Vanilla or core volto demo site on volto.demo.plone.org

[fredvd]

No description provided.

[stevepiercy]

I started a review of the *.md files, but realized that it would take less time to push commits to this branch instead. I'll do that later today. Meanwhile, here are a couple of suggestions to keep it moving forward.

[stevepiercy]

I cleaned up the READMEs

[fredvd]

@stevepiercy Thanks. I’ve set the pr to draft as the next step is to test the GHA workflows, but these only run correctly on the main branch. So for that I need to reserve some availabe time to ‘push through’ any errors I encounter, otherwise the demo’s no longer reset/refresh. But it’s not rocket science.

The naming was the most challening: we can reuse the backend contIner image for the existing demo.plone.org but the frontend for a vanilla volto needs its own build. I want to avoid naming it ‘core’ volto. Vanilla Volto is too jummy and ice cream, so I opted for frontend-volto. We can clarify the setup in the README.

[stevepiercy]

frontend-volto

This makes sense to me, and is consistent with the hierarchical naming pattern thing-subthing.

There is also an effort to get consistent names for make targets. See plone/cookiecutter-volto#14