A lightweight static site generator for markdown-based knowledge bases and documentation.

Transform your markdown files into a searchable, professional documentation website with minimal resource overhead.

Features | Use Cases | Quick Start | Documentation | Deployment | License

MarkStack is built on a simple premise: Documentation should be accessible, robust, and permanent. It is designed to serve all walks of life, from the student building a second brain, to the Dungeon Master organizing a campaign, to the Enterprise Architect enforcing ISO compliance.

Built for the "Potato" & the Cloud I intentionally developed MarkStack on a single-core, 1GB RAM virtual machine. Why? Because if it runs there, it runs anywhere.

• For the Hobbyist: Run it on a Raspberry Pi Zero 2 W, an old laptop, or a free cloud tier. It respects your hardware.
• For the Enterprise: It scales effortlessly in high-availability clusters with zero resource bloat.

Radical Simplicity: Vanilla by Design Modern web development has become over-complicated. MarkStack rejects this. MarkStack is built with Vanilla JavaScript and a single file build process. There is no complex architecture to learn, no "magic" black-box frameworks, and no fragility.

• Hackable: Because the code is simple and transparent, you can read it, understand it, and modify it to fit your exact needs.
• Future-Proof: With no heavy dependencies, your documentation site won't break just because an npm package updated 5 years from now.

Enterprise Grade: Compliance & Audit In professional environments, documentation is a legal record. MarkStack solves "documentation rot" by treating your docs as code.

• The Audit Trail: You get an immutable Git history for every comma changed. Strict Pull Request workflows mean nothing goes live without approval. This is perfect for ISO record-keeping.
• Accountability: No more "mystery edits." You know exactly who wrote that API guide, who approved it, and when it went live.

The "Headless" Brain: From D&D to Ph.D. You don't need to be a systems engineer to have a powerful, globally accessible knowledge base. MarkStack turns GitHub (or any private Git repo) into your personal Content Management System.

• The Workflow: Creating a study guide for a new subject? Managing lore for your D&D campaign? Just edit your files in the browser on GitHub (even on mobile!) and your site updates automatically if you setup the workflow, or if you have a site you use Cloudflare Pages or GitHub Pages with, it updated with each update to the repo!
• The Freedom: You get the ease of a note-taking app with the power of a static site. Your data remains yours. It is private, portable, and secure, stored in simple Markdown files that you will always own.

OFF LINE MODE!

• Take it with you: You can just clone the repo, build your first few pages and copy it to a USB, take it with you and use any text editor on any computer to edit the .md files! I REALLY recommend Caddy, it has a portable version for every OS, be it MacOS or Linux or Windows so basically all you have to do is just copy the the executable / binary to the dist folder and run it after you ran the script to build your files. You can find it here: Caddy Offical Repo

MarkStack adapts to a wide range of documentation needs. The table below outlines common scenarios where teams and individuals have successfully deployed MarkStack-powered sites.

MarkStack uses standard GitHub-flavored Markdown for all content. This design decision enables a streamlined documentation workflow that integrates directly with your existing development process.

How it works:

1. Documentation lives alongside your code in the same repository
2. Edit any .md file directly in the GitHub web interface or your local editor
3. Commit and push changes through your normal Git workflow
4. Rebuild the site with a single command
5. All changes are tracked in Git history with full attribution

This approach eliminates the need for separate documentation platforms or content management systems. Your documentation benefits from the same review process, branching strategy, and collaboration tools you already use for code. Pull requests enable documentation reviews, and merge conflicts are resolved using familiar Git workflows.

# Update documentation from the latest changes
git pull origin main
npm run build
# Documentation is now current

• Standard Markdown with YAML frontmatter, compatible with GitHub rendering
• GitHub-style alerts for NOTE, TIP, IMPORTANT, WARNING, and CAUTION callouts
• Task lists and footnotes for checklists and academic-style references
• Syntax highlighting for 190+ programming languages via highlight.js
• Mermaid diagrams for flowcharts, sequence diagrams, and other visualizations
• Visual editor with live preview, scroll sync, and file management

• Dark and light themes with automatic preference persistence
• IBM Plex typography for professional, readable text
• Responsive layout that adapts to desktop, tablet, and mobile screens
• Collapsible sidebar with hierarchical navigation

• Fast builds averaging 1.0 to 1.4 seconds for sites with 50+ content-heavy pages
• Single-file architecture with no build toolchain complexity
• Zero client-side frameworks using only vanilla JavaScript
• Static HTML output requiring no application server

• Full-text client-side search that works offline
• Fuzzy matching to find results even with partial or misspelled queries
• Keyboard navigation with Ctrl+K shortcut to open search
• Context highlighting showing matches within search results

# Clone the repository
git clone https://github.com/KineticEnforcer/MarkStack.git
cd MarkStack
# Install dependencies
npm ci
# Build the site
npm run build
# Preview locally
npm run serve

Open https://localhost:3000 in your browser. Your documentation site is ready for content.

MarkStack includes comprehensive documentation covering all aspects of the system:

markstack/
├── build.js              # Build script (single-file static site generator)
├── editor-server.js      # Visual editor server
├── editor.html           # Visual editor interface
├── siteconfig.json       # Site configuration
├── content/              # Markdown content directory
│   ├── _index.md         # Homepage content (optional)
│   └── category/         # Category folders
│       ├── _index.md     # Category landing page
│       └── article.md    # Individual articles
├── templates/
│   └── base.html         # HTML template with placeholders
├── static/               # Static assets copied to output
│   ├── css/              # Stylesheets
│   ├── js/               # Client-side JavaScript
│   └── svg/              # Logo and icons
└── dist/                 # Generated output (excluded from version control)

Edit siteconfig.json to customize your site:

{
  "siteTitle": "My Knowledge Base",
  "headerTitle": "MyKB",
  "siteSubtitle": "Documentation for everything",
  "siteUrl": "https://docs.example.com",
  "baseUrl": "",
  "defaultDescription": "Knowledge base and documentation",
  "showHero": true,
  "copyrightText": "© 2026 Your Name"
}

The baseUrl setting controls the path prefix for all internal links. Set it according to where your site is hosted:

For most deployments, leave baseUrl empty. Only set it when hosting in a subdirectory or on a GitHub Pages project site.

# Create a new article
echo "# My Article" > content/my-article.md
npm run build

# Create a category with a landing page
mkdir content/tutorials
cat > content/tutorials/_index.md << 'EOF'
---
title: Tutorials
description: Step-by-step guides for common tasks.
---
EOF
# Add an article to the category
echo "# Getting Started" > content/tutorials/getting-started.md
npm run build

Every page can include YAML frontmatter for metadata:

---
title: Page Title
description: Description for search engines and social sharing.
---
Content begins here...

Use GitHub-style alert syntax for callouts:

> [!NOTE]
> Supplementary information the reader should know.

> [!TIP]
> Helpful advice for better results.

> [!IMPORTANT]
> Critical information for successful outcomes.

> [!WARNING]
> Potential issues the reader should be aware of.

> [!CAUTION]
> Risk of negative consequences from specific actions.

Create diagrams using Mermaid syntax:

```mermaid
flowchart LR
    A[Input] --> B[Process]
    B --> C[Output]
```

Development workflow:

# Terminal 1: Watch for changes and rebuild
npm run watch
# Terminal 2: Serve the site locally
npm run serve
# Or use the visual editor for focused writing
npm run editor

MarkStack generates static HTML files that can be hosted on any web server or static hosting platform.

For automated deployments, see the CI/CD Integration documentation.

• Node.js 18.0.0 or higher
• npm (included with Node.js)

No additional build tools, compilers, or system dependencies are required.

This release introduces the Visual Editor and significantly improves code quality across the codebase.

• Visual Editor (npm run editor)
  • Browser-based markdown editor with live preview
  • File tree panel for navigating and managing content
  • Real-time preview styled exactly like the built site
  • Scroll synchronization between editor and preview panels
  • File management: create, rename, delete files and folders
  • Keyboard shortcuts: Ctrl+S (save), Ctrl+B (build)
  • Confirmation modals for unsaved changes and destructive actions

• Code Quality Refactoring

  • Added comprehensive JSDoc documentation to all source files
  • Organized code with clear section separators and comments
  • Improved function naming and code structure
  • Professional-grade documentation following senior developer standards

• Editor Server (editor-server.js)

  • RESTful API for file operations (read, write, create, delete, rename)
  • File tree endpoint for content navigation
  • Build trigger endpoint for site regeneration
  • Secure local-only access on port 3001

• Editor Interface (editor.html)

  • Split-panel layout with resizable sections
  • Syntax highlighting for markdown editing
  • GitHub-style alert rendering in preview
  • Mermaid diagram support in preview
  • Unsaved changes detection with visual indicator

• New Visual Editor documentation page
• Updated Commands Reference with editor command
• Updated Project Structure with editor files
• Updated Quickstart with editor workflow

This project is licensed under the GPL-3.0 license. See LICENSE for the full license text.

_{Built for developers who value simplicity and performance.}