Update docs for Plone 6.1 release
Open
Nobody has claimed this yet.
99 tag: Plone 6.x
- Dominant language
- Makefile
- Stars
- 106
- Forks
- 190
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
- Verify that Cookieplone uses Plone 6.1 final.
- Update Cookieplone output wherever it is documented.
- With buildout- or pip-based installs, either replace all instances of
https://dist.plone.org/release/6-latest/withhttps://dist.plone.org/release/6.1-latest/or verify that the former redirects to the latter. - In
docs/install/create-project-classic-ui.md, updateguilabelsand workflow as needed. - Update
docs/admin-guide/install-buildout.mdanddocs/admin-guide/install-pip.mdto use Python versions for Plone 6.1. - Consider new replacement keys for
PLONE_BACKEND_MINOR_VERSIONandPLONE_BACKEND_PATCH_VERSION. - https://github.com/plone/volto/issues/6540
- https://github.com/plone/documentation/issues/1674
Originally posted by @davisagli in https://github.com/plone/documentation/pull/1714#discussion_r1779697046
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
Start by reviewing the Cookieplone output and the release references in docs/install/create-project-classic-ui.md, docs/admin-guide/install-buildout.md, and docs/admin-guide/install-pip.md. Verify the Plone 6.1 final version and redirect behavior, then update the documented output, labels, workflow, Python versions, and replacement-key guidance so every checklist item is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100