Archive PloneConf 2025, prepare for PloneConf 2026
Open
@polyester is already working on this.
Since Jul 30, 2026.
- Dominant language
- Makefile
- Stars
- 65
- Forks
- 100
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 5
Description
The following tasks need to be performed to archive a snapshot of the trainings from PloneConf 2025 and prepare for PloneConf 2026. @stevepiercy, @polyester, and others will perform these tasks.
- #1004
- Cut branch
2025frommain - Add
2025to the Ruleset "Branch protection" in https://github.com/plone/training/settings/rules/20865105. - Create environment
2025at https://github.com/plone/training/settings/environments.- In the environment
2025, create environment variableDEPLOY_PATH_TRAININGto use the path on the server/var/www/2025.training.plone.org. The other variables and the secret are inherited at the repository level. The secretDEPLOY_KEY_TRAININGis stored in our REDACTED_SECRET_STORAGE_TOOL, and its name is "dplone_training_rsa kupu training user deploys github DEPLOY_KEY_TRAINING". - In the environment
2025, add deployment branch rule2025with the pattern of2025.
- In the environment
- Add a new key for 2025 in https://github.com/plone/ai-team-private/blob/master/ansible/host_vars/kupu.yml#L109-L115. (@fredvd plans to migrate this old Ansible deployment configuration to a modern one.)
- Configure DNS for
2025.training.plone.org - Configure web server for
2025.training.plone.org - Sync
2025branch withmainexcept for 2025 configuration, just before archival. - Update branch
2025,docs/conf.pyfor:-
project -
version -
release -
html_theme_options[announcement] -
ogp_site_url -
ogp_image -
ogp_site_name -
html_baseurl -
logo[text]
-
- Update
2025branch.github/workflows/build_deploy.ymlusing2024branch as an example. - Ensure
2025branch deploys to2025.training.plone.org - Update
mainbranch,docs/_templates/404.htmlwith archive link. #1008 - Update
mainbranch,docs/index.mdto list the 2025 archive. #1008 - Remove trainings from the
mainbranch to archive them. - Update branch
main,docs/conf.pyfor: #1008-
intersphinx_mapping -
exclude_patterns -
source_replacements
-
- Run
make linkcheckbrokenonmain - Run
make linkcheckbrokeninplone/documentation - Update Matomo to track new hostname. See https://github.com/plone/training/pull/944
List of trainings to keep
These trainings shall remain hosted at https://training.plone.org/ for 2026.
- Customizing Volto Light Theme
- Mastering Plone 6 development (to be renamed to "Mastering Plone Development")
- Content editing for Plone (to be renamed to "Training for Content Editing")
- Installing and Deploying Plone
- Plone Migrations: Theory and Practice
Trainings under update
None.
List of trainings to remove
The latest snapshot version of these trainings shall remain hosted at https://2025.training.plone.org/ and maintained on the branch 2025.
Training herders
- @stevepiercy
- @polyester
- other?
Previous years' related issues
- 2025's checklist https://github.com/plone/training/issues/907
- 2024's checklist https://github.com/plone/training/issues/844
- First annual plan https://github.com/plone/training/issues/672
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.
Assessment
This issue has not been assessed yet.