Public Repository Templates

Use this page when creating or refreshing documentation in a public translated document-template repository.

The copy-ready templates live in:

examples/translation-repository/

They are intentionally generic. Copy them into the public repository, then edit repository names, branch names, and publication policy there. The tool repo is the template source; the public repository is the source of truth for its actual operations.

What to Copy

Recommended starting set:

• examples/translation-repository/README.md

• examples/translation-repository/docs/README.md

• examples/translation-repository/docs/branch-policy.md

• examples/translation-repository/docs/maintenance-runbook.md

• examples/translation-repository/docs/security-and-permissions.md

• examples/translation-repository/docs/translation-style.md

Copy workflow templates separately from examples/github-actions/. The docs templates explain the expected branch model; the workflow templates implement the version-branch validation and packaging flow.

Policy Source

Keep the branch layout and visibility rules in one place: Public Template Repository Integration. The templates listed above are starting files for the public repository; they should not become a second copy of the policy in this tool repo.

Update Rule

When these templates change:

1. Update examples/translation-repository/ in this tool repo.

2. Run make check and make docs.

3. Copy the reviewed template changes into public translated-template repositories that want the new wording.

4. Do not assume updating this tool repo rewrites public repository docs automatically.

This mirrors the KM translation tool pattern: reusable docs live with the tool, while production public repositories copy and own their active copies.