content-adaptation.md

# Beehiiv Adaptation Rules

- Treat Beehiiv as `email + web + publication growth`, not as a plain CMS.
- Separate these surfaces on purpose: `title`, `subtitle`, `email subject`, and `preview text`.
- If the publication uses recurring layouts, inspect templates first instead of freehanding HTML.
- Decide whether the post is for `web`, `email`, or `both`, and whether tiers are `free`, `premium`, or segmented.
- Use one clear title field as the H1; do not repeat it inside the body.
- Open fast: explain why this edition exists now within the first screen.
- Prefer short paragraphs, recap bullets, and clean subheads that scan in both inbox and browser.
- Strip heavy iframe/widget/browser-only assumptions unless the user explicitly needs them.
- Keep CTA singular and publication-aware: reply, share, upgrade, read, register.
- Default operational posture: `draft first`, explicit send/visibility settings, warn about Send API / Enterprise caveats when relevant.