Blog HTML Writer
Overview
Write one complete blog HTML post from one news topic using a fixed section flow and reusable style rules.
When To Use
- User wants a final HTML blog article, not plain text.
- User wants consistent SEO structure and readability.
- User wants beginner-friendly Korean wording without childish tone.
Required Output Bundle
Always return these two outputs together:
- Final HTML document
- One separate meta description sentence (plain text line)
Fixed HTML Flow
Use this exact section order unless user explicitly overrides:
- Hero title block
- Question
- Short answer
- Explanation
- Term table
- Flow section (diagram allowed)
- Image explanation section
- Example
- "Ireon sanghwangeseo sseuyeoyo" section
- Policy terms section
- Practical reading tips
- FAQ (exactly 2 items)
- One-line summary box
- Sources footer
Never add a "comic summary" section by default.
Style Rules (must follow)
- Title: strong SEO style, include primary keyword early.
- First paragraph: include one-line definition of the main term.
- Reading level: understandable for elementary students.
- Tone: simple and clear, but not childish.
- Keep sentence length short to medium.
- Prefer concrete everyday examples.
SEO Rules
- Include one H1.
- Include logical H2/H3 hierarchy.
- Add title and meta description in head.
- Add one standalone meta description sentence outside HTML output.
- Include 1-2 source links at footer.
Internal Link Placeholders
Add at least 2 internal link placeholders in body text:
- [[INTERNAL_LINK:related-post-1]]
- [[INTERNAL_LINK:related-post-2]]
FAQ Rules
- Exactly 2 FAQ questions.
- Each answer must be 2-4 short sentences.
- Questions should match likely beginner confusion.
Validation Checklist
Before finalizing:
- Comic summary section absent.
- "Ireon sanghwangeseo sseuyeoyo" section exists.
- FAQ count is exactly 2.
- One-line summary box exists at end.
- Meta description sentence is provided separately.
- Internal link placeholders exist (2+).
Reference
Read references/style-rules.md for detailed writing constraints. Use assets/template-skeleton.html as the base structure.