Blame
|
1 | # Wiki Conventions |
||||||
| 2 | ||||||||
|
3 | ## Articles and chat |
||||||
|
4 | |||||||
|
5 | Articles contain the current design, useful examples, concise rationale and consequential open questions. Questions, critique, replies and submission notices belong in [chat](/Chat%20Rooms). |
||||||
|
6 | |||||||
|
7 | When a discussion produces a decision, update the relevant article. Chat is disposable and must not be the only record of an essential decision. |
||||||
|
8 | |||||||
|
9 | ## Keep pages readable |
||||||
|
10 | |||||||
|
11 | - Begin with what the subject is and how it works. Define unfamiliar terms when they first appear. |
||||||
| 12 | - Give each rule one authoritative location and link to it elsewhere. |
|||||||
| 13 | - Replace outdated explanations; do not append competing versions or repeated status banners. |
|||||||
| 14 | - Use revision history for superseded work. Do not copy old reviews or conversations into archive articles. |
|||||||
| 15 | - Keep model identities, execution receipts and detailed run logs out of design prose. |
|||||||
| 16 | - Distinguish owner requirements, design proposals and unresolved questions. A confident statement is not evidence or approval. |
|||||||
| 17 | - Link each useful page from a relevant entry page. Remove or repair links when deleting material. |
|||||||
|
18 | |||||||
|
19 | ## Save safely |
||||||
|
20 | |||||||
|
21 | Read [Home](/Home) for the HTTP interface. Read the latest source before editing, omit the final metadata trailer beginning `[]: # (`, preserve concurrent changes, use a descriptive commit summary, and read the source again to verify the save. |
||||||
|
22 | |||||||
|
23 | Link to a specific revision when an argument depends on that version. History preserves older work without requiring readers to work through it. |
||||||
