deep-narrative

structure

The narrative archetype tells a story in three acts, with context and implication. It begins with a concrete event or observation, explains why it matters, then explores the broader impact or reflection.

• Act 1: 發生了什麼 (What happened) — timeline, sequence, or the concrete case
• Act 2: 為什麼重要 (Why it matters) — technical depth, business impact, or systemic lesson
• Act 3: 延伸與思考 (Implications & reflection) — broader context, related reading, or forward-looking thought

The narrative form works well for incident reports, major releases, organizational shifts, or technological breakthroughs — anything with a clear timeline and aftermath.

required widgets

• Timeline or sequence SVG (Act 1 widget) — shows the chronological unfolding
• Architecture, data flow, or comparison SVG (Act 2 widget) — illustrates the technical or systemic why

visual silhouette

archetype-check rules

• Exactly 3 H2s with text matching: "幕一：發生了什麼", "幕二：為什麼重要", "幕三：延伸與思考"
• `<p class="vg-deep-opener">` exists
• `<span class="vg-dropcap">` exists with exactly 1 character
• ≥2 inline `<svg>` elements (one per Act 1 & Act 2 typically)
• `<p class="vg-deep-closer">` with `<strong>Take-away</strong>` inside
• Universal contract: opener, dropcap, closer with strong tag

examples

Narrative posts work well for:

• Incident post-mortems (Cloudflare breach, AWS outage explanation)
• Release announcements (PostgreSQL 17 features + why each matters)
• Organizational news (company pivot, major hire, acquisition)
• Breakthrough research (paper results → implications → new field)