Publisher Queue Architecture

Architecture Ideas:
We can create a dynamically updating publishing queuing app with all the information we want. I'd estimate a sprint and change to do any of the first 3 options.
- [ ] [Writing to json file in an S3 Bucket](https://aws.amazon.com/blogs/startups/building-dynamic-dashboards-using-lambda-and-dynamodb-streams-part-1/)
- [ ] Writing to google sheets (Bob)
- [ ] [Dynamically recreating an app](https://rockset.com/blog/live-dashboards-dynamodb-streams-lambda-elasticache/)
- [ ] Something with websockets instead of polling (a mystery)

Some Questions:
Adding security is an extra 1/2 sprint to a sprint.
- [ ] Does it need to be secure? (non-public, only Joplin editors can view it)
- [ ] Do publish requests made be different users need to be secure? (impossible for other Joplin editors to see)