## Summary - Updated frontmatter `title:` in all 63 doc cards from slug-case to human-readable (e.g. `borgmatic` → `Borgmatic`, `ai-assistance-guide` → `AI Assistance Guide`) - Titles now closely match file stems so `[[wiki-links]]` render naturally without alternate anchor text - Corrected titles that diverged from stems (e.g. `host-inventory` → `Hosts`, `grafana-alloy` → `Alloy`, `argocd-applications` → `Apps`) - Deleted `title-test-alpha.md` and `title-test-beta.md` test cards and removed their reference index entry ## Deployment and Testing - [x] `docs-check-links` passes — all wiki-links valid - [x] `docs-check-index` passes - [x] `docs-check-filenames` passes - [ ] Verify titles render correctly on docs site after deploy Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/117
1.3 KiB
1.3 KiB
| title | tags | ||
|---|---|---|---|
| Docs |
|
Docs (Quartz)
Documentation site built with Quartz and served via nginx.
Quick Reference
| Property | Value |
|---|---|
| URL | https://docs.ops.eblu.me |
| Namespace | docs |
| Container | registry.ops.eblu.me/blumeops/quartz:v1.0.0 |
| Source | docs/ directory in blumeops repo |
| Build | Forgejo workflow build-blumeops.yaml |
Architecture
- Source: Markdown files in
docs/with Obsidian-compatible wiki-links - Build: Forgejo workflow builds Quartz static site on push to main
- Release: Built assets published as Forgejo release attachments
- Deploy: Container downloads release bundle on startup, serves via nginx
Release Process
Documentation is automatically built and released when changes are pushed to main:
- Workflow detects changes in
docs/directory - Quartz builds static HTML/CSS/JS
- Assets uploaded as release attachment
- ArgoCD deployment updated with new
DOCS_RELEASE_URL - Pod restarts and downloads new bundle
Configuration
- Quartz config:
quartz.config.ts - Layout:
quartz.layout.ts - ArgoCD app:
argocd/apps/docs.yaml - Manifests:
argocd/manifests/docs/