Customisation Guide

Verdocs is designed to be highly flexible through a single configuration file: config.yml. This file, located at the root of your project, controls everything from website metadata to granular theme colors.

The config.yml Structure

The configuration is divided into four main sections: General Metadata, Hosting, Branding, and Theming.

1. General Metadata

These fields define the identity of your documentation site.

FieldTypeDescription
titleStringThe name of your website. Appears in the browser tab and navbar.
descriptionStringA brief description used for SEO and meta tags.

Example:

title: "Project Phoenix Docs"
description: "The official technical documentation for Project Phoenix."

2. Subfolder Hosting

If you are not hosting your documentation at the root of a domain, you must configure the base_path.

FieldTypeDescription
base_pathStringThe URL prefix for your site (e.g., /verdocs/ for GitHub Pages). Defaults to "".

Example:

base_path: "/verdocs/"

GitHub Pages
base_path is specifically needed when you're deploying your site to GitHub Pages. Always set it to your repository name. For more details on how to setup a github pages website, click here.


3. Branding (Assets)

Customise the visual identity of your site by referencing files in your assets/ directory.

FieldTypeDescription
navbar_logoStringThe filename of the logo shown in the top-left of the navbar.
faviconStringThe filename of the icon shown in the browser tab.

Example:

navbar_logo: "logo.png"
favicon: "favicon.ico"

4. Theming (Dual-Theme Support)

Verdocs features full support for Light and Dark modes. You can customise both independently via the theme and dark_theme sections.

Standard Theme Fields

FieldDescription
primary_colorThe accent color used for links, active sidebar items, and progress bars.
background_colorThe main background color of the documentation pages.
text_colorThe primary font color for body text.
colorsA map of semantic tags (admonitions) to their respective hex colors.

Semantic Colors (Admonitions)

The colors section (aliased as admonitions) allows you to define the brand colors for callouts like Tips, Notes, and Warnings.

Example Configuration:

theme:
  primary_color: "#007bff"
  background_color: "#ffffff"
  text_color: "#333333"
  colors:
    tip: "#28a745"
    note: "#17a2b8"
    warn: "#ffc107"
    important: "#fd7e14"
    danger: "#dc3545"
    error: "#bd2130"
    custom_tag: "#722ed1" # You can add as many as you want!

dark_theme:
  primary_color: "#007bff"
  background_color: "#0d1117"
  text_color: "#c9d1d9"
  colors:
    tip: "#2ea043"
    # ... define other dark mode variants here

How to Apply Changes

  1. Modify config.yml: Open the file in your preferred editor and update the values.
  2. Preview: If the preview server is running (verdocs preview), it will detect the changes and reload the site automatically.
  3. Generate: For production, run verdocs generate to bake these settings into your static HTML files.

Hex Only
Verdocs currently supports standard 6-digit hex codes (e.g., #FFFFFF) for all color fields.

On this page
The config.yml Structure 1. General Metadata 2. Subfolder Hosting 3. Branding (Assets) 4. Theming (Dual-Theme Support) Standard Theme Fields Semantic Colors (Admonitions) How to Apply Changes