Content Structure

Every piece of content follows this skeleton:

1. Hook: One sentence that makes the reader care. State the problem or the payoff.
2. Context: 2-3 sentences of background. Only what the reader needs to follow the argument.
3. Body: The actual content. One idea per paragraph. Short paragraphs (3-5 sentences max).
4. Takeaway: What should the reader do or remember? Be specific.

Never bury the lead. The most important information goes first.

Blog Posts

Opening paragraph: State what the reader will learn and why it matters. No throat-clearing ("In today's fast-paced world...").

Use subheadings every 200-300 words. Readers scan before they read.

Code examples: Show the simplest version that works. Annotate with comments only where the logic is non-obvious.

Closing: Summarize the key insight in one sentence. Optionally suggest a next step.

Word count targets:

• Tutorial: 1000-1500 words
• Opinion/analysis: 800-1200 words
• Announcement: 300-500 words

Documentation

Write for the reader who is trying to accomplish something, not the developer who built it.

Structure every doc page as:

• What this is (one sentence)
• When to use it
• How to use it (with a complete example)
• Reference (parameters, options, edge cases)

Use second person ("you") not third person ("the user"). Use active voice ("Run the command") not passive ("The command should be run").

Editing Passes

Apply these passes in order:

1. Structure pass: Is the argument logical? Does each paragraph follow from the previous? Cut anything that doesn't support the main point.
2. Clarity pass: Replace jargon with plain language. Break long sentences. One idea per sentence.
3. Concision pass: Cut filler words (very, really, just, actually, basically, in order to). Cut redundant phrases. If you can say it in fewer words, do it.
4. Tone pass: Match the target tone. Read it aloud. Does it sound like a person talking?
5. Proofread: Grammar, spelling, punctuation. Check proper nouns and technical terms.

Tone Adjustment

When adapting tone, adjust these dimensions:

• Formal vs casual: vocabulary complexity, contractions, sentence length
• Technical vs accessible: assumed knowledge, jargon level, explanation depth
• Authoritative vs conversational: first person usage, rhetorical questions, humor
• Urgent vs measured: sentence length, exclamation points, imperative verbs

Always preserve the core message when adjusting tone. Change how you say it, not what you say.

SEO Basics

• Title: Include the primary keyword naturally. Under 60 characters.
• Meta description: Summarize the value proposition in 150-160 characters.
• Headings: Use H2 for main sections, H3 for subsections. Include keywords where natural.
• Internal links: Link to related content where it genuinely helps the reader.
• Alt text: Describe images for accessibility. Include keywords only if accurate.

Do not keyword-stuff. Write for humans first. Search engines reward content that readers actually find useful.