Reorganize templates structure #187
Conversation
|
Testing instructions: COOKIEPLONE_REPOSITORY_TAG=create-templates-folder uvx [email protected] |
davisagli
left a comment
davisagli
left a comment
There was a problem hiding this comment.
Approving, but with some reservations about the "monorepo" project name.
| "templates": { | ||
| "project": { | ||
| "path": "./project", | ||
| "path": "./templates/projects/monorepo", |
There was a problem hiding this comment.
My preference would be to call this volto rather than monorepo. monorepo is a description of how it is organized, not what kind of project it creates.
There was a problem hiding this comment.
I'm not really clear what's the purpose of this directory. It looks like neither projects/volto nor projects/monorepo, but just project, based on its contents of a single project. Maybe I missed some earlier conversation.
There was a problem hiding this comment.
@davisagli @ericof Steve and I been chatting today about naming of all the possible type of outputs that Cookieplone can generate. We tried to stablish a unified naming for them, mainly for documentation. For now, we settled on:
1 Plone site
It has both a frontend add-on and a backend add-on, and its purpose is to build a website. This was formerly called a project.
2 Package with frontend and backend add-ons
It has both a frontend add-on and a backend add-on that integrate with each other, and its purpose is to build a feature for release as a package.
3 Package with frontend add-on only
It has a frontend add-on only, and its purpose is to build a feature for release as a package.
4 Package with backend add-on only
It has a backend add-on only, and its purpose is to build a feature for release as a package.
What do you think?
I am planning to write a document about the "addon driven development" that we have now in Plone. It will include this and all what it entails.
There was a problem hiding this comment.
Whoops, I didn't see @sneridagh's comment, before creating a separate issue to discuss and expand upon it, at #191. Would it be better to carry the discussion of this topic to the issue, and give it better visibility?
There was a problem hiding this comment.
I would prefer tackling that on an new issue
stevepiercy
left a comment
stevepiercy
left a comment
There was a problem hiding this comment.
I don't have much to add, but it looks good, with a couple of minor changes for Plone version support.
| "6.0.8", | ||
| "6.0.9", | ||
| "6.1.0a1", | ||
| "6.1.0a2", |
There was a problem hiding this comment.
Add versions recently released.
6.0.15 and 6.1.1 and their rc or a.
There was a problem hiding this comment.
@ericof the recent versions of the 6.0.x and 6.1.x lines are still missing.
Co-authored-by: Steve Piercy <[email protected]>
github-project-automation
bot
moved this from In Progress
to Done
in Bucharest Sprint 2025
Fixes #186