[Phase 4] Community visibility: blog post, forums, and awesome lists

[HerbHall]

Summary

Execute a community visibility campaign to announce Runbooks to the Docker and DevOps communities.

Why This Matters

Even after publishing to Docker Hub, the extension needs active promotion to gain initial users. Docker extensions are not browsed as frequently as npm packages or VS Code extensions - active outreach is needed.

Channels

1. Blog Post on herbhall.net

• Write a launch announcement post covering:
  • What Runbooks does and why it exists
  • Screenshots and usage examples
  • Installation instructions
  • Link to GitHub for contributions
  • Future roadmap / planned features

2. Docker Community

• Docker Community Slack #extensions channel: Share announcement with screenshot
• Docker Community Forums: Post in the Docker Desktop category
• Docker Hub: Ensure image description and README are polished

3. Social / Developer Communities

• Reddit: Post to r/docker and r/devops
• Hacker News: Submit as a Show HN post
• Dev.to: Cross-post the blog article
• LinkedIn: Share with professional network

4. Awesome Lists

• Search for awesome-docker lists on GitHub
• Submit PRs to add Runbooks where relevant

Acceptance Criteria

• Blog post published on herbhall.net
• Posted in Docker Community Slack #extensions
• Posted in at least one additional community (Reddit, Dev.to, etc.)
• Docker Hub image description is polished

Notes

This is a manual/marketing task - not code-implementable by Claude Code. Track completion with checkboxes.