Feature/version i11n switching

.devcontainer/start-server.sh

@@ -1,6 +1,6 @@
 #!/bin/bash
 
-git config --global --add safe.directory /workspaces/tag-app-delivery
+git config --global --add safe.directory /workspaces/cnpe-community
 git submodule update --init --recursive
 cd website
 npm install

.github/ISSUE_TEMPLATE/localization.yml

@@ -31,9 +31,16 @@ body:
     attributes:
       value: |
         If this is a new localization, please complete the following items:
-        - [ ] Enable i18n by update website/config.toml and website/i18n/<short-language-code>.toml
+        - [ ] Add the language to `website/config.toml` under `[languages]`
+        - [ ] Create `website/i18n/<short-language-code>.toml` with UI string translations
+        - [ ] Create `website/content/<short-language-code>/_index.md` (homepage) with `outdated: true`
+        - [ ] Create section stubs (`blog/_index.md`, `contribute/_index.md`, `initiatives/_index.md`) with `outdated: true` so the top navigation works
+        - [ ] Create translation stubs for all existing pages (frontmatter only, with `outdated: true`) so the site doesn't 404 in the new language
 
         All localizations require the following items:
-        - [ ] Translate some key pages (e.g. content/_short-language-code_/_index.md)
+        - [ ] Translate page content and remove the `outdated: true` flag from translated files
+        - [ ] For versioned resources (whitepapers, glossary, maturity model), ensure both `latest/` and version folders (e.g. `v1/`) have corresponding files
         - [ ] Local testing
         - [ ] Reviews by additional native speakers
+
+        See the [Contributing translations](https://github.com/Cloud-Native-Platform-Engineering/cnpe-community#contributing-translations) section of the README for more details on the translation workflow.

.github/workflows/notice-i18n-tasks.yml

@@ -49,5 +49,7 @@ jobs:
         message: |
           ### Action Required
           You are adding or updating English content so please take the following actions for other languages.
-          - If you update content, that has corresponding files in other languages, include a note suggesting that users check the English page for the most recent updates in those translated pages.
-          - If you add new content under `website/content/en` there is nothing you need to do.
+          - If you are **adding new pages**, create a translation stub for each supported language (`es`, `zh`, `ja`, `ko`, `fr`, `de`). The stub only needs frontmatter with `outdated: true` — no body content. Without stubs, the new page will 404 in other languages.
+          - If you are **updating existing content** that has translations, add `outdated: true` to the frontmatter of the corresponding translated files so the site shows a "Translation Needed" banner on those pages.
+
+          See the [README](https://github.com/Cloud-Native-Platform-Engineering/cnpe-community#adding-new-pages) for more details.

README.md

@@ -72,6 +72,72 @@ In order to effectively support and manage the diverse needs of the community, w
 
 See [Artifacts](https://cloudnativeplatforms.com/artifacts/) for a list of key artifacts produced by the community. These include whitepapers, presentations, and other resources that are useful for practitioners and organizations looking to build and operate cloud native platforms.
 
+### Tagging a new version of a whitepaper or artifact
+
+When a whitepaper, glossary, or other versioned artifact is ready for release, follow this process to tag a new version while preserving document history in git.
+
+1. **Merge all draft changes into `latest/`.**
+   Ensure the `latest/` folder contains the final content for the version you want to tag.
+
+2. **Create a folder for the new version.**
+   For example, if you are tagging `v2`, create a `v2/` folder alongside `latest/`.
+
+3. **Move the file from `latest/` to the new version folder using `git mv`.**
+   This preserves the file's commit history on the new version.
+
+   ```sh
+   git mv latest/index.md v2/index.md
+   ```
+
+4. **Restore the `latest/` file from the previous commit.**
+   This keeps `latest/` intact as the working copy for future edits.
+
+   ```sh
+   git checkout HEAD~1 -- latest/index.md
+   ```
+
+5. **Update frontmatter in both files.**
+   - In the new version file (e.g. `v2/index.md`): update the `url` to include the version (e.g. `whitepapers/platforms/v2`), set `toc_hide: true`, and mark the version as `active` in the `versions` block.
+   - In `latest/index.md`: add the new version to the `versions` block.
+
+6. **Repeat for translations.**
+   Apply the same `git mv` and restore steps to any translated versions of the artifact under the relevant `content/{lang}/` directories.
+
+7. **Commit and push.**
+
+> **Why `git mv` instead of `cp`?** Using `git mv` followed by restoring the original ensures that `git log --follow` traces the full history of the tagged version file back through all prior edits. A simple copy would start the new file's history from scratch.
+
+### Adding new pages
+
+When adding a new page to the English site, create a translation stub in each language directory so that the page is accessible in all languages. Without a stub, translated versions of the site will return a 404 for the new page.
+
+1. Create your new page under `website/content/en/` as usual.
+
+2. For each supported language (`es`, `zh`, `ja`, `ko`, `fr`, `de`), create a matching file with only frontmatter and `outdated: true`:
+
+   ```yaml
+   ---
+   title: "Same title as the English page"
+   outdated: true
+   ---
+   ```
+
+   For section pages (`_index.md`), also include `list_pages: true`.
+
+3. The `outdated: true` flag tells the site to display the English content with a "Translation Needed" banner, so you don't need to include any body content in the stub.
+
+### Contributing translations
+
+Translations are one of the most impactful ways to contribute. Here's how the translation workflow works:
+
+1. Find a page to translate. Look for files with `outdated: true` and no body content under `website/content/{lang}/` — these are stubs waiting for a translation.
+
+2. Replace the stub with your translated content. Keep the same frontmatter fields (especially `type`, `url`, and `versions` if present) but translate the `title` and `description`. Remove the `outdated: true` line.
+
+3. If the page has already been translated but the English version has been updated since, the file will have `outdated: true` with existing body content. Update the translation to match the current English version and remove `outdated: true`.
+
+4. For adding a completely new language, open a [localization issue](https://github.com/Cloud-Native-Platform-Engineering/cnpe-community/issues/new?template=localization.yml) and follow the checklist there.
+
 ## Active Initiatives
 
 The Community helps coordinate specific initiatives that are have benefits for the broader Platform Engineering community. Some of these initiatives are led by the Community, while others may exist under the CNCF Technical Advisory Groups (TAGs)

platform-as-a-product/platform-engineer-interview-script.md

@@ -52,6 +52,6 @@
 - Thank them for their time!
 - Do you have any questions for us?
 - Legal Reminder: Only the anonymized transcript will be shared with the wider research team; all references to you and your company will be removed. Only a small group of leads will have access to the video to ensure the integrity of the transcript for the duration of the project, after which the video will be deleted.
-- Join the conversation: "Join the ongoing conversation at TAG App Delivery: https://tag-app-delivery.cncf.io/wgs/platforms/"
+- Join the conversation: "Join the ongoing conversation at the Platform Engineering Technical Community Group: https://cloudnativeplatforms.com/" (link updated March 2026)
 
 

platforms-maturity-model/latest/contributions.md

@@ -0,0 +1,15 @@
+We are grateful for the many people who spent their time and energy reviewing or contributing to each version of this document.
+
+This list is meant to thank these individuals but is in no way indicative of their endorsement or complete agreement with the final contents.
+
+Many apologies if this list is inaccurate in any way. If anyone feels they have been left off or would prefer to be removed please reach out.
+
+[Version 0.0.1](https://docs.google.com/document/d/1dXx5wJm_vfq3hXRr1kPOEp3g3W0UgBkynjyK-OBuJyM/edit) reviewers: Abby Bangser, Abby Kearns, Abdur Rahman Mungul, Adrian Cockroft, Colin Humphreys, Daniel Bryant, Edward (Ted) Newman, Kief Morris, Paula Kennedy, Manuel Pais, Michael Coté, Nicki Watt, Sam Newman
+
+[Version 0.1.0](https://docs.google.com/document/d/1bP8-LQ-d41eIdQB3IC2YsncDhawpFLggql2JxwtE0XI/edit) reviewers: Abby Bangser, Abdur Rahman Mungul, Adam Gardner, Areti Panou, Asare Nkansah, Atulpriya Sharma, Colin Griffin, John Dietz, John Gardner, Josh Gavant, Kirstin Slevin, Luca Acquaviva, Marsh Gardiner, Michael Kestigian, Nadav Cohen, Nicki Watt, Niklas Beinghaus, Ram Iyengar, Rick Osowski, Rogerio Angeliski, Saim Safdar, Simon Forster, Tsahi Duek, Victor Lu, Viktor “Bika” Nagy, Vishal Biyani
+
+[Version 0.2.0](https://docs.google.com/document/d/11J_RpaUwydNNBg5aVjH5Uzn8i-b4urEtJzwR86XezFQ/edit) reviewers: Abby Bangser, Asare Nikansah, Atulpriya Sharma, Colin Griffin, John Gardner, Josh Gavant, Kirstin Slevin, Marsh Gardiner, Matt Menzenski, Puja Abbassi, Puneet Kandhari, Roberth Strand, Saim Safdar, Tsahi Duek, Victor Lu, Vijay Chintha, Vishal Biyani
+
+[Version 0.3.0](https://docs.google.com/document/d/1yhvT1dZ78JQyKs3Kb64V098XgIFG0N3IXAAX6O67Ju0/edit) reviewers: Abby Bangser, Asare Nkansah, Bob Hong, Bruno Dias, Colin Griffin, Daniel Bryant, Josh Gavant, Marsh Gardiner, Matt Menzenski, Nicki Watt, Ramanujan Iyengar, Roberth Strand, Saim Safdar, Tsahi Duek
+
+Version 1.0.0 reviewers: Abby Bangser, Antoine Bermon, Atulpriya Sharma, Blake Romano, Bruno Dias, David Sandilands, Jennifer Riggins, Josh Gavant, Karena Angell, Kirstin Slevin, Marsh Gardiner, Matt Menzenski, Puja Abbassi, Roberth Strand