Document publishing process
Open
@benoit74 is already working on this.
Since Feb 2, 2026.
documentation
- Dominant language
- Python
- Stars
- 7
- Forks
- 1
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 18
Description
To secure the quality of the publishing process, things have to be done following a clear and rigourous process. So far this is not documented properly, We should document it to:
- As a reminder/howto for content responsible
- As an input for the CMS developers
I would put the documentation in the wiki (in this repo).
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.