Hermes BibleUnofficial Docs
← All docs Docs / Core Features

Extending the Dashboard

The Hermes web dashboard ( ) is built to be reskinned and extended without forking the codebase. Three layers are exposed: 1. Themes — YAML files that repaint t

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/extending-the-dashboard

The Hermes web dashboard ( ) is built to be reskinned and extended without forking the codebase. Three layers are exposed: 1. Themes — YAML files that repaint t

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Table of contents
  2. Themes
  3. Quick start — your first theme
  4. Palette, typography, layout
  5. Palette (3-layer)
  6. Typography
  7. Layout
  8. Layout variants
  9. Theme assets (images as CSS vars)
  10. Component chrome overrides
  11. Color overrides
  12. Raw customCSS
  13. Built-in themes
  14. Full theme YAML reference

Section map

Table of contents

Maps table of contents to the Core Features documentation path, with the source page reserved for exact commands and updates.

Themes

Maps themes to the Core Features documentation path, with the source page reserved for exact commands and updates.

Quick start — your first theme

Maps quick start — your first theme to the Core Features documentation path, with the source page reserved for exact commands and updates.

Palette, typography, layout

Maps palette, typography, layout to the Core Features documentation path, with the source page reserved for exact commands and updates.

Layout variants

Maps layout variants to the Core Features documentation path, with the source page reserved for exact commands and updates.

Theme assets (images as CSS vars)

Maps theme assets (images as css vars) to the Core Features documentation path, with the source page reserved for exact commands and updates.

Component chrome overrides

Maps component chrome overrides to the Core Features documentation path, with the source page reserved for exact commands and updates.

Color overrides

Maps color overrides to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Table of contents, Themes, Quick start — your first theme, Palette, typography, layout, Layout variants. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: extending, dashboard, reskinned, extended, without. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for extending the dashboard before applying exact upstream commands.

Verify firstTable of contents

Open the source anchor for Table of contents and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Table of contents; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Themes if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • The Hermes web dashboard ( ) is built to be reskinned
  • extended without forking the codebase. Three layers are exposed
  • YAML files that repaint t

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page