as an Integrator I can read how to make a frontend that is editable on a demo site and test it against content on that demo site

[djay]

Problem

We want a way to allow others to try out making their own frontend and discovering how easy it is to make it real time editable. And to track the progress of the project as new apis are added to make more parts editable. We want to allow many frontends to be editable for the same backend content.

Proposed solution

• [ ] hydra package will have a plone.distribution which puts up documentation for integrators and testers
  • can write integrator docs in readme and have demo site content just link to it on github
• [x] Initial docs to explain how to make a frontend for plone hydra.
  • plone client etc.
  • can use any framework.
  • how you might deploy that frontend. e.g. netlify
  • then how to login and enter the frontend url to access the editor.
  • And how most of the editor functions will be broken for now until until more of the roadmap is completed
  • how in the future you will include an additional iframe bridge api to enable live edit functionality
• [x] Initial dummy content to test with
• [ ] Stetch goal: write the docs in markdown in the readme and turn that into html and turn that into frontpage content in the distribution

for @djay to do

• [x] deploy repo that can build frontend and backend images and push to EKS and then do heml upgrade
• [x] deploy repo will look for merges in hydra and use github action to redeploy changes automatically
  • not sure we can put secrets in hydra for it to use a repo dispatch. if not we will have to use zapier or similar to kick off the deploy . or just do it manually for the time being.
• [ ] cron to reset the content nightly in case anyone tests and changes the content