Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 36 ยท Workflows and Systems

A Company Wiki and Documentation

Build a Notion wiki that people trust: a clear structure, a docs database with owners and review dates, verified pages, templates, naming rules and search habits.

A wiki fails when people cannot find things or cannot trust what they find. Notion makes it easy to create pages and very easy to create too many. The fix is not more content but structure, ownership and review: every page has a home, an owner and a date by which someone checks it again.

Notion cannot run on this site. This lesson explains the real setup and uses JavaScript stand-ins to check the maintenance logic.

Start with the questions people ask

Before you build, list the ten questions new teammates ask most: "How do I request time off?", "Where is the brand guide?", "How do we deploy?". Your first wiki sections answer those. A wiki built around the org chart is harder to navigate than one built around tasks and topics.

A common top-level structure:

  • Start here: welcome, how the wiki works, who to ask.
  • Company: mission, values, policies, benefits.
  • Teams: one page per team with its processes.
  • How we work: meetings, tools, templates, security.
  • Projects: one page per active project (or a link to the Projects database).

Keep the top level to five to seven items. Depth should be two or three levels, not eight.

Use a database for documents

Notion has a Wiki database type, or you can build your own Docs database. Either gives you properties that plain pages lack:

Property Type Why
Name Title Clear and searchable
Owner Person Who keeps it correct
Category Select Policy, Process, Guide, Reference
Team Multi-select or relation Who it applies to
Last reviewed Date When it was last checked
Review every Select or number Days between reviews
Verification Verification property (on supported plans) or Select Verified or Expired

The verification feature in Notion lets an owner mark a page as verified for a period, after which the badge expires and signals the content needs a look. If it is not available on your plan, mimic it with a Select and a date.

Templates and style

Add database templates so every doc looks alike:

  • How-to guide: Purpose, Steps (numbered list), Troubleshooting, Related pages.
  • Policy: Summary, Who it applies to, Details, Exceptions, Contact.
  • Runbook: Trigger, Prerequisites, Steps, Rollback, Escalation.

Agree on naming: verbs for how-tos ("Request time off"), nouns for references ("Brand guide"). Use clear titles because Notion search (and the Ctrl+K / Cmd+K quick find) works on titles first.

  • A table of contents block at the top of long pages.
  • Breadcrumbs appear automatically at the top for nested pages.
  • Synced blocks hold content that must be identical in several places, such as a support contact: edit once and every copy updates.
  • Linked views of the Docs database on team pages, filtered by Team.
  • Related links at the bottom of each page.

Stand-in: which docs are overdue for review?

JavaScript, not Notion: it computes the review state the way a filtered view or formula would.

JS Stand-in: review status

Press Run (or Ctrl + Enter) to see the console output here.

No output.

In Notion the same check can be a formula property that outputs "Expired" or "Verified", and a view that shows only expired pages for each owner.

Stand-in: broken-structure check

A tidy wiki has no orphan pages (without a parent category) and no ownerless pages. This stand-in lints a list of pages.

JS Stand-in: wiki lint

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Keeping a wiki alive

  1. Name an owner for every page. A page with no owner is the one that goes stale.
  2. Review on a schedule. A monthly "docs hour" for each team prevents rot.
  3. Delete or archive pages nobody needs; fewer, better pages win.
  4. Make editing easy. Allow anyone to suggest a change with a comment, and give owners the edit.
  5. Measure. Page analytics (on paid plans) show which pages are read and which are not.

Permissions matter. Keep the wiki broadly readable but limit editing of policies to their owners. Share sensitive HR or finance pages in a closed teamspace, not the open wiki.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. What is the best starting point for a wiki's structure?

    Organize around tasks and topics people need answers for, not around who reports to whom.
  2. 2. Why add Owner and Last reviewed properties to a Docs database?

    Owners and review dates let you find and fix pages that may have gone out of date.
  3. 3. Which feature keeps one block identical in several pages?

    Edit a synced block in one place and every copy updates.

Summary

  • Build the wiki around the questions people ask, with a shallow structure.
  • Use a Docs or Wiki database with Owner, Category and review dates.
  • Templates and naming rules keep pages consistent; synced blocks avoid duplicates.
  • Review on a schedule and archive what nobody uses.

Next: Project: A Habit Tracker