Mohio Documentation
Mohio is a local-first knowledge workspace for small teams. It keeps documents in plain Markdown, runs as a desktop app, and is designed to support bring-your-own AI workflows without hiding the underlying files.
Overview
- Problem: small teams need shared documentation without heavy wiki tooling or opaque storage.
- User: small teams that want a document-first workspace and local ownership of their files.
- Stack:
Electron, React, TypeScript, Vite, CodeMirror, Markdown files in a Git-backed workspace.
Documentation Architecture
1. Project Overview
- This page is the landing page for the Jekyll docs.
- Audience: user-facing
- Purpose: explain what Mohio is, why it exists, who it serves, and how the documentation is organized.
2. Technical & Architecture
- Architecture
- Audience: developer-facing
- Purpose: document system boundaries, runtime flow, integrations, and infrastructure-level decisions.
3. Design System
- Design System
- Audience: developer-facing
- Purpose: document the visual rules, layout model, and shared interaction language.
4. Changelog
- Changelog Index
- Audience: developer-facing
- Purpose: keep a chronological record of shipped changes and the reasoning behind them.
5. Feature & Module Details
6. User Manual
- User Manual Index
- Audience: end-user-facing
- Purpose: document user-facing workflows without implementation detail.
Additional Docs
- Roadmap
- Audience: user-facing
- Purpose: show the current product direction and planned phases.