blumeops/docs/tutorials/exploring-the-docs.md
Erich Blume ed24ffdd64 Enforce unique doc filenames and simple wiki-links
Rename section index files to match their titles (tutorials.md,
reference.md, how-to.md, explanation.md) so all filenames are unique.
Convert all path-based wiki-links to simple filename format for better
obsidian.nvim compatibility.

Update doc-filenames task to no longer skip index.md files.
Update doc-links task to reject path-based links containing '/'.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-04 17:13:35 -08:00

2.9 KiB

title tags
exploring-the-docs
tutorials
getting-started

Exploring the Documentation

Audiences: All (Owner, AI, Reader, Contributor, Replicator)

This guide explains how the BlumeOps documentation is organized and how to find what you need.

Documentation Structure

The docs follow the Diataxis framework:

Section Purpose When to Use
**[[tutorials Tutorials]]** Learning-oriented
**[[reference Reference]]** Information-oriented
**[[how-to How-to]]** Task-oriented
**[[explanation Explanation]]** Understanding-oriented

Quick Paths by Audience

For Erich (Owner)

You probably want quick access to operational details:

  • how-to for common operations (deploy, troubleshoot, update ACLs)
  • reference has service URLs, commands, and config locations
  • ai-assistance-guide explains how to work effectively with Claude
  • Run mise run zk-docs to prime AI context with key documentation

For Claude/AI Agents

Context for effective assistance:

  • Read ai-assistance-guide for operational conventions
  • reference has the technical specifics you'll need
  • The repo's CLAUDE.md has critical rules (especially the kubectl context requirement)

For External Readers

Understanding what this is:

  • explanation covers the "why" behind design decisions
  • reference shows what's actually running
  • Browse service pages to see specific implementations

For Contributors

Getting started with changes:

For Replicators

Replicators are people who want to build their own similar homelab GitOps setup, using BlumeOps as inspiration.

  • replicating-blumeops provides the overview
  • explanation covers architecture and design rationale
  • The replication/ tutorials go deep on components
  • Reference pages show specific configuration choices

Documentation uses [[wiki-links]] for cross-references:

  • [[service-name]] links to a reference page
  • [[page|Display Text]] customizes the link text

When reading on the web (docs.ops.eblu.me), these render as clickable links. The backlinks panel shows what references each page.

Pre-commit hooks automatically validate that all wiki-links point to existing files and that link targets are unambiguous.

AI Context Priming

The zk-docs mise task concatenates key documentation files for AI context:

mise run zk-docs

This outputs the AI assistance guide, reference index, how-to index, architecture overview, and tutorials index - providing Claude with essential context for BlumeOps operations.