Blog Content Plan — 6 Months (April–September 2026)¶
Platform: docs.cronova.dev (MkDocs Material blog plugin) Cross-post: dev.to, Hashnode (canonical URLs to cronova.dev) Frequency: 2 posts/month (realistic for a full-time professional) Language: English (primary), Spanish summaries for LATAM reach Goal: Build credibility for DevOps/infrastructure consulting
Content Strategy¶
Principles¶
- Write what AI can't fake — real incidents, real data, real gotchas
- Show the work — include configs, logs, commands, not just concepts
- One post = one actionable takeaway — readers should leave with something to apply
- Cross-reference the repo — every post links to the public homelab repo for credibility
- No fluff — skip "What is Docker?" intros. Assume technical readers.
Content pillars¶
| Pillar | Why it's unique | Posts/6mo |
|---|---|---|
| Operational excellence | Backup drills, incident response, monitoring — stuff people skip | 4 |
| Security hardening | Container caps, DNS privacy, auth — practical not theoretical | 3 |
| Architecture decisions | Trade-offs, what worked, what didn't — experience-based | 3 |
| Cultural/personal | Paraguay perspective, Guarani naming, career crossover | 2 |
Month-by-Month Plan¶
Month 1 — April 2026 (Launch)¶
Post 1: "I Tested Every Backup in My 68-Service Homelab — Here's What Broke"
- The strongest opening post. Nobody publishes actual restore test results.
- Content: backup-verify.sh architecture, the 8 test suites, what failed (Pi-hole DAC_OVERRIDE, gravity DB corruption), what passed, schedule.
- Include: real script snippets, cron schedules, restic verify output
- Cross-post: r/selfhosted (high engagement for backup content), dev.to, HN
- Estimated engagement: high — this fills a genuine content gap
Post 2: "Container Hardening at Scale: What 68 Services Taught Me About cap_drop"
- Practical guide: cap_drop ALL, per-image-type cap_add patterns (LinuxServer.io, PostgreSQL, BusyBox)
- Include: the DAC_OVERRIDE gotcha, FOWNER for gravity DB, healthcheck patterns per base image
- Real examples from the repo, not generic Docker docs
- Cross-post: dev.to, r/docker
Month 2 — May 2026¶
Post 3: "My ISP Went Down and Took My Entire Homelab With It — Twice"
- The March 18 WAN + NAT incident, written as a narrative
- Cascade diagram: ISP → WAN → NAT → DNS → Tailscale → everything
- What the watchdog caught vs missed, the pfctl NAT injection hack
- Lessons: Tailscale DNS bootstrap, OPNsense automatic NAT bug, dual-network troubleshooting
- Real timeline from the incident report
- Cross-post: r/homelab, r/opnsense, HN
Post 4: "Running a Production Homelab from Paraguay"
- The LATAM perspective nobody writes about
- ISP realities (Tigo outages), hardware sourcing ($30 shipping on $12 parts), prepaid SIM economics
- Guarani naming convention — why and how
- cronova.dev branding story
- Cross-post: r/selfhosted, dev.to, LATAM tech communities
Month 3 — June 2026¶
Post 5: "Recursive DNS in My Homelab — Why I Don't Trust Cloudflare With My Queries"
- AdGuard → Unbound → root servers on VPS
- Pi-hole → Unbound on OPNsense at home
- Split DNS removed (recursive loop incident)
- Why most "privacy-focused" homelabs still leak DNS
- Cross-post: r/selfhosted, r/privacy, HN
Post 6: "4 Rounds of Codebase Audits: 100+ Fixes in My Homelab Repo"
- The systematic approach: 3-agent parallel review, severity tiers, batch execution
- Before/after: markdownlint (1,437→0), shellcheck, yamllint
- The audit as a methodology anyone can apply to their repo
- Cross-post: dev.to, r/selfhosted
Month 4 — July 2026¶
Post 7: "OPNsense as My Home Gateway — 6 Months In"
- February cutover from ISP router, what improved, what broke
- VLANs (IOT, Guest) — design and enforcement
- WAN watchdog script for auto-recovery
- CrowdSec integration (if deployed by then)
- Cross-post: r/opnsense, r/homelab
Post 8: "My AI Assistant Runs on a $10 Raspberry Pi Zero"
- PicoClaw deployment story (if deployed by then)
- Free LLM provider stack (Groq, Gemini, OpenRouter, Mistral)
- Real usage: Telegram bot for research, translation, homelab queries
- $0/month operating cost breakdown
- Cross-post: r/selfhosted, r/raspberry_pi, HN
Month 5 — August 2026¶
Post 9: "Monitoring 68 Services With VictoriaMetrics — My Grafana Dashboard Tour"
- Papa stack: vmagent → VictoriaMetrics → Grafana
- 11 alert rules, ntfy integration, alerting tiers
- Home Assistant metrics via Prometheus endpoint
- What dashboards actually matter vs what looks cool
- Cross-post: dev.to, r/selfhosted
Post 10: "From Supply Chain to DevOps: What Inventory Management Taught Me About Infrastructure"
- Career crossover narrative
- Parallels: SKU management ↔ container management, stockout rate ↔ uptime, dead stock ↔ unused services
- How supply chain thinking improves homelab operations
- The consulting angle — positioned as a thought leadership piece
- Cross-post: dev.to, LinkedIn, HN
Month 6 — September 2026¶
Post 11: "1 Year of Self-Hosted Everything: The Real Costs"
- Full cost breakdown: hardware, electricity, VPS, domains, time invested
- What's worth self-hosting vs using SaaS
- Total cost of ownership vs Google Workspace / cloud alternatives
- Honest assessment — where self-hosting doesn't make sense
- Cross-post: r/selfhosted, HN (this type of post consistently hits front page)
Post 12: "My Family Uses AI via WhatsApp — Here's How I Set It Up"
- OpenClaw on RPi 5 deployment story (if deployed)
- Family WhatsApp group with AI assistant
- Privacy architecture, free provider stack
- Paraguay family tech adoption perspective
- Cross-post: r/selfhosted, r/OpenClaw
Cross-Posting Strategy¶
| Platform | When | Why |
|---|---|---|
| docs.cronova.dev | Day 1 (publish) | Canonical URL, SEO authority |
| dev.to | Day 1 (cross-post) | Large dev audience, good SEO, free |
| r/selfhosted | Day 1 (share link) | Highest engagement for homelab content |
| r/homelab | Day 1 (share link) | Second-highest reach |
| Hacker News | Day 2 (submit) | Lottery ticket — HN front page = 10K+ views in a day |
| Hashnode | Day 3 (cross-post) | Additional SEO, developer audience |
| Day 3 (summary post) | Professional network, consulting leads | |
| Twitter/X | Day 1 (thread) | Quick visibility, tag relevant accounts |
Cross-post rules¶
- Always set
canonical_urlto the cronova.dev post - dev.to and Hashnode both support canonical URLs natively
- Reddit: share as link post, not self-post (drives traffic to your site)
- LinkedIn: write a 3-paragraph summary with "Read more at..." link
- Never publish full content on Medium (they own SEO juice)
Newsletter Strategy¶
Platform: Buttondown (free up to 100 subscribers, Markdown-native)
- Add signup form to docs.cronova.dev footer
- Each blog post generates a newsletter edition
- Include 1-2 bonus tips not in the blog post (incentive to subscribe)
- Monthly "homelab changelog" email with what changed in the repo
Success Metrics (6-month targets)¶
| Metric | Month 1 | Month 3 | Month 6 |
|---|---|---|---|
| Blog posts | 2 | 6 | 12 |
| Monthly visitors | 500 | 2,000 | 5,000 |
| Newsletter subs | 20 | 75 | 200 |
| GitHub stars | 5 | 25 | 100 |
| dev.to followers | 50 | 200 | 500 |
| Consulting inquiries | 0 | 1-2 | 3-5 |
| Revenue | $0 | $0 | $0-200 |
These are conservative estimates. One HN front page hit could 10x any of these overnight.
Posts Requiring Deployment First¶
| Post | Requires | Target Month |
|---|---|---|
| #8 (PicoClaw) | RPi Zero W + microSD | July |
| #12 (OpenClaw WhatsApp) | RPi 5 + Personal SIM | September |
| #7 (OPNsense 6 months) | VLAN enforcement + CrowdSec | July |
| #9 (Monitoring tour) | HA Prometheus working | August |
Posts 1-6 can be written entirely from existing content and experience.
Engagement Stack¶
See blog-engagement-research-2026-03-20.md for full analysis.
| Channel | Purpose | Setup | Time/week |
|---|---|---|---|
| Giscus comments | Blog discussions → GitHub Discussions | 30 min once | 0 (auto) |
| Buttondown newsletter | 1:1 relationships, consulting leads | 15 min once | 15 min |
| Consulting funnel (2-3 posts/week) | Existing account | 45 min | |
| Community + traffic (r/selfhosted, r/homelab) | Existing account | 40 min | |
| GitHub Discussions | Repo Q&A, Giscus backend | Enable on repo | 15 min |
| BlueSky | Developer audience (secondary) | Create account | 15 min |
Do NOT: start a Discord, use Disqus, use Twitter/X, use Mastodon.
Total time budget: ~4 hours/week (realistic with full-time job + family).
First Actions¶
- Enable MkDocs Material blog plugin on docs.cronova.dev
- Set up Giscus comments (GitHub Discussions backend)
- Enable GitHub Discussions on homelab repo
- Create Buttondown account, add signup to site footer
- Create dev.to account, connect to blog RSS
- Create BlueSky account
- Write Post 1 draft (backup-verify deep dive)
- Schedule: 1 post on the 1st, 1 post on the 15th of each month
Budget¶
| Item | Cost |
|---|---|
| MkDocs blog plugin | $0 (already included in mkdocs-material) |
| Giscus comments | $0 (GitHub Discussions) |
| Buttondown newsletter | $0 (free tier, 100 subs) |
| dev.to + Hashnode + BlueSky | $0 |
| Custom domain email (optional) | $0 (already have cronova.dev email via Cloudflare) |
| Total | $0 |