9 lines
480 B
Markdown
9 lines
480 B
Markdown
Documentation Style Guide
|
|
|
|
- When referencing another Markdown file in this repo, use a relative link so it is clickable in Gitea. Example: [docs/git-workflow.md](git-workflow.md).
|
|
- Keep titles concise and descriptive; use sentence case unless a proper noun.
|
|
- Prefer short bullets (one point per line). Merge related points.
|
|
- Use backticks for commands, file paths, env vars, and code identifiers.
|
|
- Make documents actionable: lead with outcomes, then steps, then background.
|
|
|