Contribution & Review Process¶
Status: 🟢 Active | Owner: Architecture Team
How to Contribute¶
All content is stored in the internal/engineering-standards GitHub repository. Contributions follow standard pull request workflow.
Steps¶
- Fork or branch from
mainusing the naming conventionstandards/<short-description>. - Edit or create the relevant Markdown file under
docs/. - Follow the page template: include the status badge, owner, overview, standards section, and references.
- Run locally:
mkdocs serveto verify rendering. - Open a PR using the Standards PR template. Tag the relevant guild or team owner.
- Minimum review: 2 approvals required — at least one from the page owner's team.
- EAB approval required for any change that promotes a page from Draft → Active or Active → Deprecated.
Page Template¶
# Page Title
**Status:** 🟢 Active | **Owner:** Team Name
Brief one-paragraph description of what this page covers.
## Overview
Context and rationale.
## Standards
The actual standards — use admonitions, tables, and code blocks as appropriate.
## References
- [External link](https://...)
- Related internal page
---
*Last reviewed: YYYY-QN | Owner: Team Name*
Commit Message Convention¶
Follow Conventional Commits:
docs(security): add OWASP Top 10 remediation guidance
docs(java): update Spring Boot standard to 3.2
fix(tooling): correct broken link in vscode page
Last reviewed: 2025-Q4 | Owner: Architecture Team