This repo contains the Platform Maturity Model Assessment.
On answering the questions you get a spider diagram and a matrix to indicate where you are on a map right now.
You can copy the URL to share the assessment in whatever state it is in. For example:
Alongside the answers, v records which version of the question set they were given against, page records which page was open, and view=results opens straight to the results.
When giving feedback please use these shareable URLs to help folks see what you see.
Note: If you switch the language while viewing the results, the app will keep you on the results page and re-render them in the selected language. Shareable links from the results page also include this view so recipients land directly on the results.
The assessment question set carries its own version, separate from the repository's release tags, because the field_name keys and option values in shareable links are a public contract: renaming or renumbering a question silently changes what previously shared links mean.
Shareable links therefore include a v parameter recording the question set they were built against, and the footer shows the current assessment version alongside the CNCF Platform Engineering Maturity Model release it is based on.
Before changing anything under data/, read VERSIONING.md, which has the bump rules and the release process. You can check your changes locally with:
python3 scripts/validate_content.pySee CHANGELOG.md for release history.
Please join the Cloud Native Computing Foundation on Slack and use the platform-engineering channel.
The assessment content is managed through YAML files in the /data/ directory for easy updates and translations:
questions-en.yaml- English (source of truth)questions-[lang].yaml- Translations, currentlyja,ptandzhquarantine/- Translations that are incomplete or not yet reviewed, excluded from the site
To add a language, add the YAML file and add a link for it to the language nav in index.html.
questions-en.yaml, you MUST also update the corresponding translations:
-
Make changes to the English source file first: Edit
data/questions-en.yaml -
Update translation: Apply equivalent changes to
data/questions-[lang].yaml -
Bump the version: Follow the rules in VERSIONING.md
-
Verify consistency: Run
python3 scripts/validate_content.py, which checks that every file has:- Same category IDs and structure
- Same question IDs within each category
- Same option values (1-4) for scoring consistency
It compares structure only, and cannot tell whether the text was actually translated. Check that by eye.
When updating content, ensure these elements are translated in all language files:
metadatasection (titles, messages, UI text)- Category
namefields - Question
textcontent - Option
levelanddescriptiontext
After updating translations:
- Test each language using URL parameters:
?lang=en,?lang=ja,?lang=pt,?lang=zh - Verify all text displays correctly
- Ensure functionality works across all languages
- Test the complete assessment flow in each language