Journal CMS

[danielBingham]

We need to build a basic CMS system to allow journal editorial teams to create their own front end using the data in the system.

They need to be able to:

• Show and style their about information
• Display and style their published papers
• Style headers and footers
• Style a paper view page
• Display the styled pages under their own domain name
• Safe draft changes and choose when to publish them
• Preview draft changes

We can use Handlebars as a templating language and provide their information.

Question: Do we statically generate it? Or generate a frontend that uses our APIs as a backend? Does it make more sense to regenerate it each time a new submission is published or journal information is changed? (Potentially, most journals publish less than 1 paper a day.)