Clear structure
A folder layout that stays readable as docs grow across teams and products.
OWiki docsInternal documentation for your team.
Markdown-first, easy to maintain, and built for SOPs, knowledge, and project notes.
Skip to content
Why OWiki docs works
This site is built for internal teams that want documentation to stay simple, searchable, and easy to maintain over time.
- Add new pages without changing the architecture.
- Keep page ownership obvious.
- Use a single Markdown workflow for every section.
- Reuse page patterns for SOPs, guides, deployment notes, and reference pages.
Markdown-first
Reusable page patterns and conventions that make doc writing fast and consistent.
Fast by default
Static site generation, local search, and a lightweight theme built for speed.
Modern UX
Clean typography, dark mode, responsive layout, sidebar navigation, and top-level nav.
Documentation-first
Design the information architecture before the product grows too large to organize.
Scalable sidebar
Keep navigation predictable with a single source of truth for structure and ordering.
Reusable pages
Standardize how new pages are written so the team does not start from blank files.
Suggested workflow
- Create a page from the matching section pattern.
- Place it in the correct folder.
- Add it to the sidebar configuration.
- Link it from the section index.
- Keep the page focused on one topic.
Folder structure
text
docs/
getting-started/
guides/
api/
integrations/
deployment/
troubleshooting/
references/
changelog/
assets/
public/