DX-065: Write the documentation contribution guide and templates

[IbrahimIjai]

Context

Seventy-five content issues follow this one. Without a written contract for what
a documentation pull request must contain, seventy-five contributors will each
invent their own — and reviewers will spend their time on formatting instead of
accuracy. The rules exist in
docs/dx_1/003_content_map.md; this makes them findable.

Scope

• apps/docs/CONTRIBUTING.md covering: where content lives, the frontmatter
  contract, how to add a page to its manifest, which checks to run, the voice
  rules, and how to preview locally.
• Page templates for the three shapes in use: concept, guide, and reference.
• A .github/PULL_REQUEST_TEMPLATE/documentation.md mirroring the DX definition
  of done from the content map §4, including the requirement to name the source
  file for every mechanical claim.
• A reviewer checklist focused on accuracy and reader fit rather than style —
  style is DX-053's job.
• Link it from the root CONTRIBUTING.md and AGENTS.md.

Acceptance criteria

• Every command in the guide has been run and works as written.
• The three templates pass check:content unmodified.
• The PR template matches the content map's definition of done.
• Root CONTRIBUTING.md and AGENTS.md both link to it.

Out of scope

• Changing the repository-wide contribution rules.

---

Spec: docs/dx_1/003_content_map.md §4–§5 · Depends on: DX-064

[mkolade]

@mkolade has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi can i be assigned to this.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @mkolade to this issue.

[pchieneye]

@pchieneye has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I’ve carefully reviewed the issue and understand the expected outcome. I have the relevant experience to implement the solution and would be glad to take it on. Please assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @pchieneye to this issue.

[simisann1]

@simisann1 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Heyyy
I’ve gone through the issue carefully and the scope looks clear.
I can take this on fully and deliver a clean, well-structured PR within the Wave timeline.
I’m ready to start as soon as assigned to meee!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @simisann1 to this issue.

[nursetechie]

@nursetechie has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Interested in contributing to this issue, please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nursetechie to this issue.

[bade2brazy]

@bade2brazy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

assign this issue to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @bade2brazy to this issue.

[drips-wave]

Congratulations, @bade2brazy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @bade2brazy: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊