Doc owner: COS
Contributing
This repository is Allied’s definitive organisational handbook.
There are several ways to add or change content — from quick, non-technical edits through to full control in Git.
Pick the path that matches how big the change is and how comfortable you are with the tools.
Align drafts with Handbook standards (structure, IDs, front matter) and Writing style (tone, plain English, and vocabulary for definitive vs working materials).
Three ways to contribute
| Path | Best for | Skill level |
|---|---|---|
| Content Management System (CMS) | Day-to-day edits and new pages in existing collections | No Git required |
| Assisted edit | Bulk uploads, new structure, programme moves, or anything the CMS cannot represent cleanly | You describe the change; maintainers implement |
| Edit in Git | Full drafting, branching, local previews, and detailed revision history | Git and markdown |
-
Easy edits — CMS
Use the admin interface to edit markdown, create entries, and run drafts through review and publish. Same workflow most contributors use. -
Bulk or structural changes — Assisted edit
When you need many files at once, new folders or programme layout, or config changes, Get support (site header) with a clear brief. The docs team (or a developer when needed) applies it in the repo. -
Full-featured drafting and revisions — Git
Clone the repo, branch, commit, and open pull requests. Use this when you want local tooling, granular history, or you are changing structure yourself with review.
Reference
- Handbook standards — IDs, filenames, YAML, lists, rationale mirror
- Handbook standards — Strategy front matter — Fields and exclusions for
strategy/pages - Writing style — Plain English and tone
Questions
If you are unsure which path to use or where something belongs, ask AlliedGPT or use Get support in the site header.