A modern, accessible documentation viewer for Markdown files with live search, navigation, and mobile support.
- π Live search with keyboard shortcuts (Alt+S)
- π± Mobile-friendly responsive design
- π― Keyboard navigation support
- π Auto-generated document outline
- π Wiki-style internal linking
- π¨οΈ Print-friendly styling
- βΏ ARIA-compliant accessibility
- π Dark theme
- Install dependencies:
npm install
- Copy the example configuration:
cp example.index.json index.json
Then modify index.json
with your site's metadata, author info, and social links.
- Create your documentation structure:
docs/
βββ images/ # Place images here
βββ index.md # Main landing page
βββ ... other .md files
- Build the documentation index:
npm run build
This will scan your docs folder and update index.json
with the document structure.
- Start the development server:
npm start
- Place all documentation files in the
docs/
directory - Store images and video in
docs/images/
- Use
.md
extension for Markdown files
Each Markdown file can include YAML frontmatter:
---
title: Page Title
description: Page description
sort: 1 # Optional: controls sidebar order
thumbnail: images/thumb.png # Optional: for OG images
---
# Content starts here
To create sections, make a folder and add a matching Markdown file:
docs/
βββ getting-started/
β βββ getting-started.md # Folder index
β βββ installation.md
β βββ configuration.md
βββ index.md
Use double brackets for internal links:
[[Page Title]]
[[Page Title|Custom Text]]
Store images in docs/images/
and reference them:

# or
![[picture.png]]
Headers are automatically added to the right sidebar outline and are collapsible.
We recommend using Obsidian.md as your editor for the documentation files. The docs/.obsidian
directory includes a custom plugin that provides enhanced editing features:
- Displays page titles in the file explorer instead of filenames
- Shows frontmatter-defined sort order in the file list
- Automatically updates file ordering based on the
sort
property - Makes folder and document organization more intuitive
To use the plugin:
- Open the
docs
folder as an Obsidian vault - The plugin will be automatically loaded
- The file explorer will now show your document titles and sorting order
.
βββ docs/ # Documentation files
βββ build-docs.js # Documentation builder
βββ index.html # Main viewer
βββ index.js # Application logic
βββ styles.css # Styling
The build process:
- Scans the
docs/
directory - Edits
index.json
with document metadata
A GitHub Actions workflow is included that automatically:
- Runs on every push to the master branch
- Executes the build process
- Commits and pushes any changes to
index.json
- Ensures your documentation index stays in sync with your content
This means you can edit your documentation directly on GitHub, and the index will be automatically updated.
If you don't want to use Github actions, you can use npm run build
- Create a new repository on GitHub.
- Push your code to the repository.
- Go to Cloudflare Pages and connect your GitHub repository.
- Configure the build settings:
- Production branch:
main
(or your main branch name) - Build command: Leave empty
- Build output directory:
/
(root)
- Production branch:
- Save and deploy.
For improved SEO and social sharing, you can use a Cloudflare Worker to dynamically generate OG/Twitter tags.
- Create a new Cloudflare Worker using the code in
cloudflare-worker.js
. - Set the
SITE_URL
environment variable to where your site will be located, e.g.,https://example.com/docs/
- Set the
DOCS_URL
environment variable to the URL where your documentation files are hosted (usually your Cloudflare Pages URL). - Configure a route in your Cloudflare account to route all requests to your Cloudflare Pages site through the worker.
{
"defaultPage": "home",
"metadata": {
"title": "Site Title",
"description": "Site description",
"site_name": "Documentation"
},
"author": {
"name": "Author Name",
"role": "Role",
"socials": [
{
"icon": "fab fa-github",
"url": "https://github.com/username",
"title": "GitHub"
}
]
}
}
The build process generates the documents part for index.json
- Fork the repository
- Create a feature branch
- Submit a pull request
MIT License - see LICENSE file for details.