Enforce unique doc filenames and simple wiki-links (#109)
## Summary - Rename section index files to match their titles (tutorials.md, reference.md, how-to.md, explanation.md) so all filenames are unique - Convert all ~47 path-based wiki-links to simple filename format across 15 files - Update doc-filenames task to no longer skip index.md files - Update doc-links task to reject path-based links containing '/' This ensures all wiki-links work correctly in obsidian.nvim by making links resolvable by filename alone. ## Testing - `mise run doc-filenames` - all unique - `mise run doc-links` - no broken or path-based links - `mise run doc-titles` - no duplicates Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/109
This commit is contained in:
parent
a03a9faaad
commit
3da455e49c
45 changed files with 176 additions and 125 deletions
|
|
@ -17,18 +17,18 @@ The docs follow the [Diataxis](https://diataxis.fr/) framework:
|
|||
|
||||
| Section | Purpose | When to Use |
|
||||
|---------|---------|-------------|
|
||||
| **[[tutorials/index | Tutorials]]** | Learning-oriented | "I'm new and want to understand" |
|
||||
| **[[reference/index | Reference]]** | Information-oriented | "I need specific technical details" |
|
||||
| **[[how-to/index | How-to]]** | Task-oriented | "I need to do X" |
|
||||
| **[[explanation/index | Explanation]]** | Understanding-oriented | "I want to understand why" |
|
||||
| **[[tutorials|Tutorials]]** | Learning-oriented | "I'm new and want to understand" |
|
||||
| **[[reference|Reference]]** | Information-oriented | "I need specific technical details" |
|
||||
| **[[how-to|How-to]]** | Task-oriented | "I need to do X" |
|
||||
| **[[explanation|Explanation]]** | Understanding-oriented | "I want to understand why" |
|
||||
|
||||
## Quick Paths by Audience
|
||||
|
||||
### For Erich (Owner)
|
||||
|
||||
You probably want quick access to operational details:
|
||||
- [[how-to/index|How-to guides]] for common operations (deploy, troubleshoot, update ACLs)
|
||||
- [[reference/index|Reference]] has service URLs, commands, and config locations
|
||||
- [[how-to|How-to guides]] for common operations (deploy, troubleshoot, update ACLs)
|
||||
- [[reference|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
|
||||
|
||||
|
|
@ -36,29 +36,29 @@ You probably want quick access to operational details:
|
|||
|
||||
Context for effective assistance:
|
||||
- Read [[ai-assistance-guide]] for operational conventions
|
||||
- [[reference/index|Reference]] has the technical specifics you'll need
|
||||
- [[reference|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/index|Explanation]] covers the "why" behind design decisions
|
||||
- [[reference/index|Reference]] shows what's actually running
|
||||
- [[explanation|Explanation]] covers the "why" behind design decisions
|
||||
- [[reference|Reference]] shows what's actually running
|
||||
- Browse service pages to see specific implementations
|
||||
|
||||
### For Contributors
|
||||
|
||||
Getting started with changes:
|
||||
- [[contributing]] walks through the workflow
|
||||
- [[how-to/index|How-to guides]] for specific tasks (deploy services, add roles)
|
||||
- [[reference/index|Reference]] tells you where things live
|
||||
- [[how-to|How-to guides]] for specific tasks (deploy services, add roles)
|
||||
- [[reference|Reference]] tells you where things live
|
||||
|
||||
### 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/index|Explanation]] covers architecture and design rationale
|
||||
- [[explanation|Explanation]] covers architecture and design rationale
|
||||
- The `replication/` tutorials go deep on components
|
||||
- Reference pages show specific configuration choices
|
||||
|
||||
|
|
@ -66,8 +66,7 @@ Replicators are people who want to build their own similar homelab GitOps setup,
|
|||
|
||||
Documentation uses `[[wiki-links]]` for cross-references:
|
||||
- `[[service-name]]` links to a reference page
|
||||
- `[[folder/page]]` links to nested pages
|
||||
- `[[page | Display Text]]` customizes the link text
|
||||
- `[[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.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue