Blog Workflow

Optional But Valuable

4. Key Failure Story: Did something go wrong? What did you learn?
5. Specific Costs/Numbers: Any dollar amounts, time spent, metrics?
6. Gotchas: What surprised you or wasn't obvious?
7. Target Audience: Who is this for? (Rails devs, DevOps engineers, etc.)

Example Prompt to User

Let's write a blog post! I need your creative input:

1. **Topic**: What are you writing about?
   Example: "Setting up Kubernetes monitoring with Prometheus"

2. **Your Take**: What's your opinion or angle?
   Example: "Most guides overcomplicate it. Here's the minimal setup that actually works."

3. **Personal Experience**: Did you try this? What happened?
   Example: "I spent 2 days fighting Helm charts before realizing I could just use kubectl apply"

4. **Failure Story** (optional): What went wrong?
   Example: "First attempt cost me $200 in EC2 because I didn't set resource limits"

5. **Key Numbers** (optional): Any costs, time, metrics to share?
   Example: "Final setup: 30 minutes, $5/month, monitors 50 services"

6. **Gotchas** (optional): What surprised you?
   Example: "Prometheus scrape interval defaults to 1m - set it to 15s for alerts to work"

Phase 2: Generate Humanized Blog Post

Using the user's input, create a blog post following this structure:

File Creation

• Filename: _posts/{TODAY}-{slug}.md
• Slug: Lowercase, hyphenated version of title

Humanized Template

---