Do you have your own admin panel for the authors, or do they submit using markdown files/docs in e-mails? If you have an admin panel, how do you handle previews and edits... meaning do you store a copy of the content in database and then generate the static files using database as source of truth?
Or do you just generate the static files directly once the user has submitted the content.
Do you have your own admin panel for the authors, or do they submit using markdown files/docs in e-mails? If you have an admin panel, how do you handle previews and edits... meaning do you store a copy of the content in database and then generate the static files using database as source of truth?
Or do you just generate the static files directly once the user has submitted the content.
We built a CMS which using a WYSIWYG editor, marketing and design teams could also create pages and update banners.
SEO teams could improve and update meta-data for pages.
Changes from this system go into an event bus SQS (AWS) and that is then pushed into a build pipeline in jenkins.