Official technical documentation for the VergeOS hyperconverged infrastructure (HCI) platform.
Live Site: https://docs.verge.io
This repository contains the source files for VergeOS product documentation, including installation guides, feature documentation, knowledge base articles, and reference architectures.
- Framework: MkDocs with Material for MkDocs
- Language: Markdown
- Plugins: mkdocs-glightbox (image lightbox), blog plugin
- Deployment: GitHub Pages via GitHub Actions
- Python 3.8+
- pip
-
Clone the repository
git clone https://github.com/verge-io/docs.git cd docs -
Create and activate a virtual environment
macOS / Linux:
python -m venv venv source venv/bin/activateWindows (CMD):
python -m venv venv .\venv\Scripts\activate.bat
Windows (PowerShell):
python -m venv venv .\venv\Scripts\activate.ps1
-
Install dependencies
pip install -r requirements.txt
-
Start the development server
mkdocs serve
The site will be available at http://127.0.0.1:8000
docs/
├── implementation-guide/ # Installation and setup procedures
├── product-guide/ # Feature documentation by category
│ ├── auth/ # Authentication (Azure AD, Google, MFA)
│ ├── backup-dr/ # Snapshots, syncs, disaster recovery
│ ├── nas/ # Network-attached storage
│ ├── networks/ # Networking configuration
│ ├── private-ai/ # AI features
│ ├── storage/ # vSAN, tiers, Fibre Channel
│ ├── system/ # System config, nodes, clusters
│ ├── tenants/ # Multi-tenancy
│ ├── virtual-machines/ # VM management
│ └── vpn/ # IPSec, WireGuard
├── knowledge-base/ # Blog-style articles and how-tos
│ └── posts/ # Individual KB articles
├── reference-architecture/ # Deployment patterns
├── release-notes/ # Version history
├── assets/ # Images, logos, SVGs
├── stylesheets/ # Custom CSS
├── javascripts/ # Custom JS
└── overrides/ # MkDocs theme overrides
mkdocs.yml # Site configuration and navigation
| Command | Description |
|---|---|
mkdocs serve |
Start local development server with hot-reload |
mkdocs build |
Build the static site |
mkdocs build --site-dir ./_site |
Build to custom output directory |
- Use friendly, collaborative tone ("we" not "I")
- Keep guides focused on single topics
- Each step should show tangible progress
- Separate commands from their output in code blocks
MkDocs Material admonitions are available:
!!! note "Title"
Content here
!!! tip "Pro Tip"
Helpful advice
!!! warning "Caution"
Important warnings
??? note "Collapsible"
Hidden by defaultSupported types: note, abstract, info, tip, success, question, warning, failure, danger, example, bug, quote
- Store images in
docs/assets/ - Use relative paths:
 - Glightbox plugin enables click-to-zoom
KB articles require YAML frontmatter:
---
title: Article Title
slug: url-friendly-title
description: Brief description
author: Author Name
published: true
date: YYYY-MM-DD
tags: [tag1, tag2]
categories:
- Category
---Copyright © 2026 Verge.io. All rights reserved.