This project is a collection of templates for Plone integrators to use through Cookieplone.
Set up your system with Plone's Prerequisites for installation.
Select a template with the following command:
uvx cookieplone
[1/1] Select a template
1 - A Plone Project
2 - Backend Add-on for Plone
3 - Frontend Add-on
Template | Description | |
---|---|---|
A Plone Project |
Create a new Plone project with backend and frontend components. | Read More |
Backend Add-on for Plone |
Create a new Python package to be used with Plone. | Read More |
Frontend Add-on for Plone |
Create a new Node.js package to be used with Volto. | Read More |
We welcome contributions to cookieplone-templates
.
You can create an issue in the issue tracker, or contact a maintainer.
See Installation.
For source control through Git and continuous integration and delivery (CI/CD), you'll also need a Git repository either under your personal or organization's account. Both GitHub and GitLab are currently supported Git repository and CI/CD service providers. However, only GitHub is currently supported for documentation hosting.
Create a local Python virtual environment with the following command.
make install
COOKIEPLONE_REPOSITORY=~/YOUR_PATH_TO/cookieplone-templates uvx cookieplone project --no-input
make format
make format_templates
pytest
is this package's test runner.
Run all tests with the following command.
make test
Run all tests, but stop on the first error and open a pdb
session with the following command.
uv run pytest -x --pdb
Run only tests that match test_template_has_required_keys
with the following command.
uv run pytest -k test_template_has_required_keys
Run only tests that match test_template_has_required_keys
, but stop on the first error and open a pdb
session with the following command.
uv run pytest -k test_template_has_required_keys -x --pdb
To publish your project to your Git service provider, first create an empty remote repository with your Git service provider. Then navigate to the root of your generated project folder. Finally, issue the following commands.
If your remote repository is private, you'll need to manage authorization when you push commits upstream.
git status
git commit -m "first commit"
git remote add origin https://<git_service_provider>/<organization_or_username>/<project_slug>.git
git branch -M main
git push
Your remote repository should now be populated with your generated project.
The Cookieplone template documentation_starter
supports publishing documentation and pull request preview builds on Read the Docs.
First, create an account on Read the Docs, then follow their documentation to add a documentation project and configure pull request previews.
Next, update your documentation files.
Search for the string MY_READTHEDOCS_PROJECT_SLUG
throughout your project, and replace it your project's slug that Read the Docs assigned to your project.
Finally, commit and push your changes to your remote repository.
Read the Docs will build documentation and with the next pull request, will build a pull request preview and insert a link to the preview in your pull request.
It's currently not supported to check for a unique slug on Read the Docs before generating your project, especially if you set up a private repository.
This project is licensed under the MIT License.
Happy coding!