Stories for cookieplone usage
Open
Nobody has claimed this yet.
33 needs: docs
- Dominant language
- Python
- Stars
- 12
- Forks
- 4
- Avg merge
- 4m
- Merged PRs (30d)
- 1
Description
Potential stories for using cookieplone, whether or not they currently exist. This is a wish list. Please edit this description as needed.
- Develop Plone frontend Volto and contribute to its core
- Create a project with a backend only
- Create a project with a frontend only
- Create a project with both a backend and frontend
- Develop a Plone add-on
- Develop a Volto add-on
Stories for NOT using cookieplone.
- I want to demo Plone now and throw away its data periodically. Visit one of Plone's hosted demos.
- I want to demo Plone and retain its data on my own system. This is a disposable Plone setup, not intended for development. Use Docker Compose to run your own Plone site locally.
- Develop Plone backend and contribute to its core. Instead use
buildout.coredev.
@jensens @ericof @sneridagh @mauritsvanrees
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named. Review the linked hosted-demo documentation and current cookieplone usage guidance, then establish which unchecked story is in scope. Done should be an agreed, concrete change rather than an open-ended wishlist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100