Blog Engagement Strategy Research¶

Date: 2026-03-20 Context: docs.cronova.dev (MkDocs Material on Cloudflare Pages), public GitHub repo, consulting pipeline goal Constraint: Full-time supply chain job + family = max ~5 hours/week on content + engagement

1. Comments on Static Sites¶

Options Evaluated¶

System	Backend	Self-hosted?	Privacy	Effort	Notes
Giscus	GitHub Discussions	No (GitHub)	Good	Low	Best option for MkDocs Material — native support documented
Utterances	GitHub Issues	No (GitHub)	Good	Low	Predecessor to Giscus, less features (no threading, no reactions)
Disqus	Disqus servers	No	Bad	Low	Tracks users across sites, cross-context behavioral advertising, injects ads on free tier
Isso	SQLite	Yes	Good	Medium	Python app, requires a server — overkill for a static Cloudflare Pages site
No comments	N/A	N/A	N/A	Zero	Valid strategy — see analysis below

Giscus: The Clear Winner¶

MkDocs Material has first-class Giscus support with documented setup:

Install Giscus GitHub App on ajhermosilla/homelab repo
Enable GitHub Discussions on the repo
Generate config at giscus.app
Create overrides/partials/comments.html with Giscus script
Add comments: true to page front matter (or use meta plugin for folders)
Built-in dark/light theme sync with Material palette

Time to implement: ~30 minutes.

The "No Comments" Strategy¶

Many successful tech bloggers operate without on-site comments, letting discussions happen where they naturally occur (Reddit, HN, Twitter). This works when:

You actively engage in those external discussions
You include a "discuss on X" link at the bottom of posts
Your goal is reach, not on-site community

Verdict: Start with Giscus (low effort, ties into GitHub Discussions), but do NOT obsess over on-site comment engagement. Most real discussion will happen on Reddit/HN. Giscus is there for the occasional reader who wants to ask a specific question.

Disqus: Avoid¶

Disqus collects and shares personal data for behavioral advertising, tracks users across sites even when not logged in, and injects ads on the free tier. The tech-savvy homelab audience actively dislikes Disqus. Do not use it.

2. Reddit Engagement¶

Best Subreddits for Homelab Content¶

Subreddit	Members	Best for
r/selfhosted	~500K+	Self-hosting deep dives, tool comparisons
r/homelab	~1M+	Hardware, architecture, "homelab tour" posts
r/docker	~200K+	Docker Compose walkthroughs, container tips
r/opnsense	~30K+	OPNsense-specific guides
r/proxmox	~50K+	Proxmox/VM content
r/pihole	~100K+	DNS/ad-blocking content
r/homeassistant	~300K+	Home automation content

Self-Promotion Rules (2026)¶

The 90/10 rule still applies: 90% of your activity should be genuine community participation (answering questions, helping others), 10% can reference your own content.

Key principles:

Redditors reward specificity: Real numbers, screenshots, lessons learned, tradeoffs — not hype
Never post just a link: Write a summary in the post body, include key takeaways, link to your blog as "detailed writeup here"
Disclose affiliation: If it's your blog, say so. Transparency is respected
Shadow bans are real: Reddit silently hides posts from link-droppers without notification
Participate in comments: The discussion IS the value. Do not "post and flee"

Strategy: Engage on Reddit, Link Thoughtfully¶

Answer 2-3 questions per week in relevant subreddits (no link to your blog)
When you publish a post, share it as a text post with a summary + link
Reply to every comment on your posts
Reddit discussions > driving to your site. The visibility and trust you build on Reddit IS the funnel

3. Discord Community¶

Should a Solo Blogger Start a Discord?¶

No. Not at this stage. Reasons:

Time sink: Community management is a part-time job. Even a small Discord needs daily moderation, conversation-starting, and rule enforcement
Empty server problem: A Discord with 5 people feels dead and hurts your brand more than having no Discord at all
Threshold: Most successful creator Discord servers launched after reaching ~5,000+ newsletter subscribers or consistent monthly readership in the tens of thousands
Burnout risk: The #1 reason solo creators burn out is community management overhead

Existing Communities to Join Instead¶

Community	Members	Platform
Homelab Discord	~37,000	discord.com/invite/homelab
Self-Hosted Podcast	~8,000	discord.com/invite/n49fgkp
r/selfhosted Discord	Active	Linked from subreddit

Action: Join these communities as a participant, not a promoter. Help people, share knowledge, mention your blog only when directly relevant.

Discord vs Matrix¶

Given you already run Matrix-capable infrastructure:

Matrix is great for privacy purists and self-hosting enthusiasts
But your audience is on Discord, not Matrix
Discord had a February 2026 controversy (age verification via facial recognition), pushing some users to alternatives
Matrix/Element is still clunky UX compared to Discord
Verdict: Do not self-host a community platform. Join where your audience already is (Discord + Reddit)

4. GitHub Discussions¶

Enable on `ajhermosilla/homelab`?¶

Yes, for two reasons:

Giscus integration: Blog comments automatically become GitHub Discussions, creating a searchable Q&A archive
Repo-specific Q&A: Readers can ask about your Ansible playbooks, Docker Compose configs, or network topology without needing to find you on Reddit

Setup¶

Enable Discussions on the repo (Settings > Features > Discussions)
Create categories: "Blog Comments" (for Giscus), "Q&A" (for repo questions), "Show and Tell"
Giscus maps blog posts to discussions via pathname mapping

What It Is NOT¶

GitHub Discussions is not a community platform. Do not expect high engagement. It is a low-maintenance knowledge base that occasionally catches a question you can answer in 5 minutes. That is its value.

Email is the highest-converting engagement channel for a consulting pipeline:

Reply-to-email creates 1:1 conversations — the first step toward a consulting relationship
Newsletter subscribers are warmer leads than blog visitors — they opted in
Email is private, which means people share real problems (which become consulting opportunities)
You own the list — no algorithm changes, no platform risk

Buttondown¶

Buttondown is the recommended platform (from the blog platform research):

Free tier: up to 100 subscribers
Allows subscriber replies (replies go to your email)
No tracking pixels by default (privacy-friendly, matches your audience values)
Markdown-native (write once, send)
Paid tier ($9/mo) at scale: analytics, automation, custom domains

Every blog post becomes a newsletter issue (repurpose, don't rewrite)
End each issue with a soft CTA: "If you're dealing with [problem this post solves] at your organization, reply and tell me about it"
Reply-to-email IS the engagement mechanism — no comment system needed in the newsletter
Treat every reply as a potential consulting lead

Platform Assessment¶

Platform	Tech community?	Consulting leads?	Time ROI	Verdict
LinkedIn	Strong B2B	Best for consulting	High	Must-have
BlueSky	Growing (devs, journalists)	Low	Medium	Worth trying
Mastodon	Niche (FOSS/homelab crowd)	Very low	Low	Optional
Twitter/X	Declining for tech	Moderate	Low	Skip
Threads	Consumer-focused	Very low	Low	Skip

LinkedIn: Priority Platform for Consulting¶

LinkedIn data for 2026:

Inbound outreach (prospect contacts you after reading your content) converts at 14.6% vs 1.7% for outbound
Niche, industry-specific content generates 15-22% ICP engagement vs <1% for generic content
Comments are 15x more valuable than likes for algorithm reach
PDF/carousel posts outperform video (LinkedIn deprioritized video in 2025)
Critical engagement window: first 60-120 minutes after posting

LinkedIn strategy:

Post 2-3x/week: technical case studies, "what I learned" posts, infrastructure decisions explained
Content pillars: homelab-to-enterprise patterns, self-hosting cost analysis, infrastructure automation
Position as: "I build enterprise-grade infrastructure at home — imagine what I can do for your organization"
Engage in comments on other people's posts (same 90/10 principle as Reddit)

BlueSky¶

40M+ users, but daily actives dropped 40% YoY
Developer/journalist audience with 2.8x higher engagement rates than Twitter/X
Open ATProtocol means tech community is interested
Worth crossposting to, but do not make it primary
$100M Series B in March 2026 — platform is not going away

Mastodon/Fediverse¶

Active homelab community (tech-related relay connects 100+ instances)
Mastodon 5.0 (2026) improving discoverability
Your audience is partially here — FOSS/self-hosting enthusiasts
Low effort to crosspost if you set up an account on fosstodon.org or similar
Do not self-host a Mastodon instance for this purpose (resource overhead not justified)

Twitter/X: Skip¶

The tech community has fragmented away from X
Algorithm changes in 2025-2026 deprioritize links to external sites
Engagement quality has declined
Not worth the time investment for a consulting pipeline

7. Cross-Posting Strategy¶

dev.to¶

Set canonical URL to your blog post on docs.cronova.dev
This tells search engines your site is the original source
dev.to has built-in import-from-RSS with automatic canonical URL setting
dev.to audience: developers who might become consulting leads
Cross-post selectively (your best 1-2 posts/month)

Hacker News¶

Do NOT use "Show HN" for blog posts — Show HN is for things people can try/use, not reading material
Submit as regular stories with your blog post title
HN loves: strong opinions backed by data, real numbers, architecture decisions, postmortems
HN hates: listicles, "top 10" posts, anything that smells like marketing
Raspberry Pi, self-hosting, and computer hardware are among HN's favorite topics
Engage in HN comments when your post gets traction — HN readers respect the author participating

Reddit (covered in section 2)¶

Text post with summary + link, not just a link drop
Different subreddits for different posts (don't spam the same post everywhere)

8. What Actually Drives Engagement (Consensus)¶

High-ROI Activities¶

Newsletter with reply-to-email — builds 1:1 relationships, highest consulting conversion
LinkedIn content — direct path to consulting leads, B2B audience
Reddit participation — community trust, organic reach, real discussions
Giscus on blog — low-effort, catches occasional engaged reader
GitHub Discussions — searchable Q&A archive for repo visitors

Low-ROI Activities (Avoid)¶

Running your own Discord/Matrix — time sink, empty server problem
Twitter/X — fragmented audience, algorithm hostile to links
Disqus — privacy nightmare, audience actively dislikes it
Self-hosted Isso — overengineered for the use case
Posting everywhere daily — leads to burnout, not engagement

Time Investment Warning¶

Successful solo bloggers consistently report:

Quality over quantity — 1 great post/month beats 4 mediocre ones
Batch content creation — write 2-3 posts in a session, schedule releases
Do not attempt daily social media posting with a full-time job and family
Community management burnout is the #1 reason solo creators quit

9. Recommended Strategy¶

Phase 1: Foundation (Week 1, ~3 hours)¶

[x] Blog is live on docs.cronova.dev (done)
[ ] Enable GitHub Discussions on ajhermosilla/homelab
[ ] Add Giscus to MkDocs Material (30 min, documented setup)
[ ] Create LinkedIn profile optimized for consulting (headline, about section, featured posts)
[ ] Create BlueSky account (optional, 10 min)
[ ] Set up Buttondown newsletter with custom domain

Phase 2: Engagement Rhythm (Ongoing, ~4 hours/week)¶

Activity	Frequency	Time	Purpose
Write blog post	2x/month	2-3 hrs each	Core content
Send newsletter	2x/month	15 min (repurpose blog post)	Build subscriber list
LinkedIn post	2-3x/week	15 min each	Consulting pipeline
Reddit participation	3-4 comments/week	10 min each	Community trust
Cross-post to dev.to	1-2x/month	10 min	Wider reach
Submit to HN	When you have a banger post	2 min	Spike traffic

Phase 3: Scale If Warranted (6+ months out)¶

Only if you see traction:

Consider Discord/community if newsletter hits 1,000+ subscribers
Consider Mastodon if FOSS audience grows
Consider paid newsletter tier if consulting leads come through email
Consider sponsoring a homelab podcast if ROI justifies it

The Consulting Funnel¶

Blog post (docs.cronova.dev)
  ├── Reddit/HN discussion → trust + visibility
  ├── dev.to crosspost → developer reach
  ├── LinkedIn post → B2B visibility
  └── Newsletter → subscriber
        └── Reply-to-email → 1:1 conversation
              └── Consulting engagement

What NOT to Do¶

Do not start a Discord server
Do not post on Twitter/X
Do not use Disqus
Do not try to be on every platform
Do not sacrifice writing quality for posting frequency
Do not engage in community management that takes more than 1 hour/week
Do not measure success by pageviews — measure by newsletter subscribers and replies

10. Bilingual (English/Spanish) Angle¶

Unique Positioning¶

Being bilingual in Paraguay gives you a unique angle:

Latin American tech community is underserved in homelab/self-hosting content
Spanish-language homelab content is scarce compared to English
Potential strategy: English-first for global reach, occasional Spanish posts for regional differentiation
LinkedIn in particular has a growing Latin American tech community

Practical Approach¶

Write primary content in English (larger audience, consulting leads likely English-speaking)
Consider a "en espanol" section or tag for selected posts
The bilingual angle itself is a differentiator worth mentioning in your bio/about page