communicationbusiness
Content Calendar
Plan and manage content production with editorial calendars — defining themes, channels, cadence, ownership, and measurement for consistent, strategic content delivery.
contenteditorialcalendarplanningpublishing
Works well with agents
Works well with skills
content-calendar/
SKILL.md
Markdown| 1 | |
| 2 | # Content Calendar |
| 3 | |
| 4 | ## Before you start |
| 5 | |
| 6 | Gather the following from the user: |
| 7 | |
| 8 | 1. **What are the business goals for content?** (Lead generation, brand awareness, developer adoption, SEO, customer education) |
| 9 | 2. **Who is the target audience?** (Personas, job titles, experience levels) |
| 10 | 3. **What channels will you publish on?** (Blog, newsletter, social media, YouTube, docs, podcast) |
| 11 | 4. **What is the publishing cadence?** (Weekly, biweekly, monthly — per channel) |
| 12 | 5. **Who creates and approves content?** (Writers, reviewers, editors, subject matter experts) |
| 13 | 6. **What planning horizon?** (Monthly, quarterly) |
| 14 | |
| 15 | If the user says "we need to post more content," push back: "More content without a theme or audience in mind creates noise, not value. What specific outcome should content drive in the next quarter?" |
| 16 | |
| 17 | ## Content calendar template |
| 18 | |
| 19 | ### 1. Content Strategy Summary |
| 20 | |
| 21 | Anchor the calendar to strategy before filling in dates. |
| 22 | |
| 23 | ``` |
| 24 | Planning period: Q2 2025 (April - June) |
| 25 | Primary goal: Increase developer signups by 25% |
| 26 | Target audience: Backend engineers evaluating API platforms |
| 27 | Channels: Blog (2x/month), Newsletter (weekly), Twitter (daily) |
| 28 | Content pillars: 1. Technical tutorials 2. Case studies 3. Engineering culture |
| 29 | Success metrics: Blog traffic, newsletter open rate, signup conversions |
| 30 | ``` |
| 31 | |
| 32 | ### 2. Content Pillars and Themes |
| 33 | |
| 34 | Define 3-5 pillars that all content maps to. Each pillar supports the business goal. |
| 35 | |
| 36 | ``` |
| 37 | | Pillar | Description | % of Content | Goal Alignment | |
| 38 | |----------------------|------------------------------------------|-------------|--------------------------| |
| 39 | | Technical tutorials | Step-by-step guides solving real problems | 40% | Developer trust + SEO | |
| 40 | | Case studies | Customer stories with measurable results | 25% | Social proof + leads | |
| 41 | | Engineering culture | How we build — process, values, lessons | 20% | Employer brand + trust | |
| 42 | | Product updates | Feature launches, changelog highlights | 15% | Retention + adoption | |
| 43 | ``` |
| 44 | |
| 45 | ### 3. Monthly Calendar View |
| 46 | |
| 47 | For each month, plan content at the title level with key metadata. |
| 48 | |
| 49 | ``` |
| 50 | ## April 2025 |
| 51 | |
| 52 | | Week | Date | Channel | Title | Pillar | Owner | Status | |
| 53 | |------|------------|------------|-------------------------------------------|------------|-------------|----------| |
| 54 | | 1 | Apr 1 | Blog | "Building a Rate Limiter in Go" | Tutorial | @alice | Draft | |
| 55 | | 1 | Apr 3 | Newsletter | Weekly digest: rate limiting + API news | Mixed | @bob | Planned | |
| 56 | | 2 | Apr 8 | Blog | "How Acme Cut API Latency by 60%" | Case study | @carol | Outline | |
| 57 | | 2 | Apr 10 | Newsletter | Weekly digest: performance case study | Mixed | @bob | Planned | |
| 58 | | 3 | Apr 15 | Blog | "Our Approach to On-Call Rotations" | Culture | @dave | Idea | |
| 59 | | 3 | Apr 17 | Newsletter | Weekly digest: on-call + community recap | Mixed | @bob | Planned | |
| 60 | | 4 | Apr 22 | Blog | "v2.3 Release: Batch Endpoints" | Product | @eve | Planned | |
| 61 | | 4 | Apr 24 | Newsletter | Weekly digest: new features roundup | Mixed | @bob | Planned | |
| 62 | ``` |
| 63 | |
| 64 | ### 4. Content Production Workflow |
| 65 | |
| 66 | Define the stages every piece of content moves through, with owners and SLAs. |
| 67 | |
| 68 | ``` |
| 69 | Stage 1: Idea → Proposed in content backlog with pillar tag and audience |
| 70 | Stage 2: Outline → Structured outline approved by editor (2 business days) |
| 71 | Stage 3: Draft → Full draft written by author (5 business days) |
| 72 | Stage 4: Review → Technical review by SME + editorial review (3 business days) |
| 73 | Stage 5: Final edits → Author incorporates feedback (2 business days) |
| 74 | Stage 6: Publish → Scheduled and published on target date |
| 75 | Stage 7: Promote → Shared on social channels, newsletter, community |
| 76 | Stage 8: Measure → Performance reviewed 14 days after publish |
| 77 | ``` |
| 78 | |
| 79 | Total lead time: **14 business days** from outline approval to publish. Work backwards from the publish date to set deadlines. |
| 80 | |
| 81 | ### 5. Measurement Framework |
| 82 | |
| 83 | Define how you'll evaluate content performance. Review metrics monthly. |
| 84 | |
| 85 | ``` |
| 86 | | Metric | Target | Measured At | |
| 87 | |---------------------------|---------------|------------------| |
| 88 | | Blog pageviews | 10K/month | Google Analytics | |
| 89 | | Newsletter open rate | >40% | Email platform | |
| 90 | | Newsletter click rate | >8% | Email platform | |
| 91 | | Content → signup rate | >2% | Attribution tool | |
| 92 | | Social engagement rate | >3% | Social analytics | |
| 93 | | Publish consistency | 100% on-time | Calendar audit | |
| 94 | ``` |
| 95 | |
| 96 | ## Quality checklist |
| 97 | |
| 98 | Before finalizing the calendar, verify: |
| 99 | |
| 100 | - [ ] Every piece of content maps to a content pillar |
| 101 | - [ ] Each pillar is connected to a business goal, not just "it'd be nice to write about" |
| 102 | - [ ] Every item has an owner and a status |
| 103 | - [ ] The production workflow has realistic SLAs that work backwards from publish dates |
| 104 | - [ ] Publish cadence is sustainable given the team's capacity |
| 105 | - [ ] Measurement metrics are defined and attributed to specific tools |
| 106 | - [ ] The backlog is prioritized, not just a dumping ground of ideas |
| 107 | - [ ] At least one month is planned at the title level, not just themes |
| 108 | |
| 109 | ## Common mistakes to avoid |
| 110 | |
| 111 | - **Planning content without a strategy.** A calendar full of titles with no content pillars or audience definition is just a to-do list. Start with goals and pillars, then fill in titles. |
| 112 | - **Overcommitting on cadence.** Publishing daily when you have one writer guarantees burnout and declining quality. Set a cadence the team can sustain for 6+ months, then increase. |
| 113 | - **No owner per piece.** "The marketing team" is not an owner. Every content item needs one person responsible for moving it from idea to published. |
| 114 | - **Skipping the measurement step.** If you never review what performed well, you'll keep producing content that doesn't work. Build a monthly review into the calendar itself. |
| 115 | - **Treating all channels the same.** A blog post is not a tweet is not a newsletter. Adapt format, tone, and length to each channel — don't just cross-post the same text everywhere. |
| 116 |