wiki-writing

To write an enduring wiki page, start with a concise lead sentence defining the subject, use neutral third-person present-tense prose, structure the body with clear noun-phrase headings, and apply disciplined interpage linking to avoid fragmentation.

The best way to structure internal documentation is to select a specific page type—such as entity, concept, decision, project, or reference—and organize the content with clear section headings that capture persistent, encyclopedic knowledge for your team.

To document a technical decision record, create an encyclopedic page that outlines the alternatives considered, provides the rationale, and states the final choice, finishing with a concise one-line edit summary to track the revision.

You should expand an existing knowledge base page instead of creating a new one when the new content naturally fits the current subject, preventing duplication and maintaining disciplined link-first mention conventions across the wiki.

Reference documentation should use a neutral, third-person, present-tense tone while actively avoiding filler, puffery, and vague qualifiers to ensure the knowledge resource remains precise and maintainable for future readers.

Yes, your wiki writing requires informative one-line edit summaries for page revisions, as this discipline helps maintain a reliable knowledge resource by clearly tracking changes and rationale for future teams.