These rules keep the wiki easy to navigate, safe to sync into Wiki.js or static hosts, and consistent for managers and staff.
{.dense} tables, {.tabset} tabs, task lists, etc.). See the official guide: Markdown — Wiki.js.| Audience / topic | Folder | Example |
|---|---|---|
| Manager setup, Solution options, operational configuration | Managers/ |
Managers/Solution-options/README.md |
| Rostering: shifts, templates, pricing (manager) | Managers/Shifts/ |
Managers/Shifts/shift-templates.md |
| Operational lists (event locations, future ops topics) | Managers/Operations/ |
Managers/Operations/event-locations.md |
| End-user “how do I…” for all roles | User-manual/ |
Numbered chapters + README.md |
| Screenshots and binary uploads | assets/ |
assets/legacy-root/… or assets/topics/… |
| Older topic-specific articles (keep URLs stable) | Asset/, Clinical/, Personnel/, System/, Vehicles/ |
Prefer linking from legacy/README.md when you add a replacement elsewhere |
| Repo maintenance for contributors | docs/ |
This file, plus CONTRIBUTING.md at repo root |
Do not introduce new narrative pages as loose files at the repository root unless they are top-level navigation (home.md, how-to-use-this-wiki.md, documentation-index.md, navigation-by-site-menu.md, governance-documents.md, KPI.md, etc.).
When you add a guide that maps to a sidebar area (for example a new Management → Tools screen), add a row to navigation-by-site-menu.md so users can still find help by the same path they use in the portal.
shift-pricing-and-invoicing.md).Asset/Containers.md). Do not bulk-rename without updating every inbound link and Wiki.js path.Each browsable page should start with YAML like:
---
title: Short human title
description: One line for search / SEO (optional but recommended).
published: true
tags: managers, shifts
editor: markdown
---
title: Shown in the wiki UI; keep concise.description: Plain summary; no internal codenames unless necessary.published: Use true when the page is ready; false only if you use drafts in your workflow.tags: Use a single comma-separated string (e.g. tags: managers, shifts). Do not use a YAML list under tags: (- item) — Wiki.js Git import calls .split(', ') on tags and skips the page if it is an array. If you have no tags, use tags: [] or omit tags.tags: help immediately followed by a second line - managers (or any - …). That is not valid for Wiki.js import — use one line: tags: help, managers.[Solution options hub](../Managers/Solution-options/README.md) from docs/..md targets in GitHub; Wiki.js often resolves them to the correct page path when configured for Git storage.System/Solution-options-complete-guide.md).assets/ only (e.g. assets/topics/shifts/my-screenshot.png)./assets/topics/shifts/my-screenshot.png (match how assets/legacy-root/ is referenced today).navigation-by-site-menu.md when it maps to a portal menu area, and from documentation-index.md and/or the relevant hub (Managers/README.md, Managers/Shifts/README.md, home.md) as appropriate.assets/; no new root-level *.png / *.jpg.tags is a list or [].