Content Ideas Quality Standards

Source: _agents/workflows/generate-seo-pages.md

Each content idea must give the reader everything they need to act immediately — not just a topic, but a specific format, hook, and opening line.

Each entry has three fields:

• idea — strategy-level description
• draft — short hook preview (ready to paste)
• full_post — complete ready-to-publish content

Pages with progressive_disclosure: true in front matter render a “See Full Draft” toggle on each card. Clicking it replaces the short hook with the full post in-place.

Generic Pattern — Do Not Use

- platform: Twitter/X
  idea: Post a thread detailing the Pause, Reflect, Document method.
  draft: Pause, Reflect, Document

Specific Pattern — Use This

- platform: Twitter/X
  idea: >-
    Start a 7-tweet thread walking through the full Pause, Reflect, Document method.
    Open with: "The exercise that made me realize I had 60 untold stories worth sharing"
    and close by asking followers to name the month they would most want to revisit.
    Each tweet covers one step with a concrete personal example.
  draft: "The exercise that made me realize I had 60 untold stories worth sharing (most people skip this):"
  full_post: |
    The exercise that made me realize I had 60 untold stories worth sharing (most people skip this):

    🧵 1/7

    Most people think they don't have enough content ideas.

    The truth? You have decades of stories you've never written down.

    Here's the Pause, Reflect, Document method that changed everything for me:

    [... all 7 tweets ...]

Requirements for Each idea Field

1. Format details — include specifics: tweet count, word count, slide count, or video length
2. Hook strategy — name the opening hook and why it works for that platform
3. Engagement mechanic — include a CTA or interaction driver (save, comment, DM, tag)
4. Platform-specific logic — match the idea to how that platform’s algorithm rewards content

Requirements for Each draft Field

• Must be a ready-to-copy opening line the user can paste directly into the platform
• Must include a strong hook (curiosity gap, bold claim, or specific number)
• Must end with a colon : or ellipsis ... to signal continuation
• Never just repeat the idea description or leave it blank
• Length limit: 1–3 sentences maximum — the collapsed preview is clamped to 4 lines; draft is the teaser, not the full post. Long draft values get cut off mid-sentence, which looks broken. Keep it tight so the whole hook is visible before “See Full Draft”.

Requirements for Each full_post Field

• Use YAML literal block scalar (|) — this preserves newlines and renders correctly
• Must be a complete, publish-ready post — not a summary or outline
• Must open with the same hook as draft for continuity
• Platform-specific structure required (see table below)
• SEO note: full post text is rendered in the HTML source (hidden by CSS, not JS-gated), so Google indexes it

Platform-Specific Format Guidance

When to Add progressive_disclosure

Add progressive_disclosure: true to a page’s front matter when all content ideas in that page have a full_post field. Do not add it to pages where only some ideas have full_post — the toggle will silently do nothing on cards without it, which is fine, but the front matter flag signals intent.

---
layout: preview
progressive_disclosure: true
tag1: Marketing
tag2: Personal Branding
...
---