eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions

Remove title slug check and test duplicate titles (#116)

Browse source 
## Summary
- Remove `docs-check-titles` pre-commit hook and mise task — wiki-links resolve by filename stem, not frontmatter title, so slug-format titles and uniqueness aren't needed
- Add two test cards (`title-test-alpha`, `title-test-beta`) with identical `title: Title Test Card` to verify duplicate titles don't break Quartz or obsidian.nvim
- Retitle `index.md` from `blumeops-documentation` to `BlumeOps`
- Add GitHub and Forgejo repo links to homepage intro

## Test plan
- [ ] Deploy to docs site and verify both test cards render and cross-link correctly
- [ ] Verify homepage title renders as "BlumeOps"
- [ ] Verify repo links on homepage work
- [ ] After confirming, remove test cards in a follow-up

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/116
This commit is contained in:
Erich Blume 2026-02-07 21:26:18 -08:00
commit a7d6d44d3d
8 changed files with 34 additions and 180 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/index.md
View file

@ -1,5 +1,5 @@
---
title: blumeops-documentation
title: BlumeOps
aliases: []
id: index
tags: []
@ -14,11 +14,11 @@ infrastructure.
## What is BlumeOps?
BlumeOps is my personal homelab infrastructure managed entirely through code.
Everything lives in a single git repository, from service configs to deployment
automation. Even the [[forgejo]] instance that hosts this repo is defined
within it, making BlumeOps fully self-hosting. It's a digital life raft I built
for myself as I went, and you can see it all from within your editor of choice.
(I recommend vim.)
Everything lives in a [single git repository](https://github.com/eblume/blumeops), from service configs to
deployment automation. Even the [[forgejo]] instance that [hosts this repo](https://forge.ops.eblu.me/eblume/blumeops)
is defined within it, making BlumeOps fully self-hosting. It's a digital life
raft I built for myself as I went, and you can see it all from within your
editor of choice. (I recommend vim.)
These services run on my home [[hosts|infrastructure]], primarily an m1 mac
mini named [[indri]] and a Synology NAS called [[sifaka]]. The infrastructure