Blog posts

Markdown + YAML frontmatter, compiled to JSON at build time. One file per post; filename stem is the slug.

Frontmatter

• title (never ends in a period), slug, date ("YYYY-MM-DD"), description (one plain sentence), tags.
• tags: Changelog plus tier(s) Free / Pro / Enterprise reflecting who can actually use the feature. AI Native is for non-changelog posts only -- never combine it with Changelog.
• internal-refs: REQUIRED. A list of the commits/PRs this post announces, each "<short-sha> <commit subject> (#PR)". Non-rendering provenance so any future reader traces the copy back to the shipped work. Every post carries one; backfill posts that don't.

Voice

Hype + "here's what you get" + a little direct info -- not a tutorial. Lead with the benefit and name the thing (say "Okta", not "your IdP"). Short: 2-3 tight paragraphs. Personality welcome, but direct -- don't bury the lead in a clever title. Push mechanics to the docs and close with a CTA (hello@zenable.io, a settings link, or zenable.io/feedback).

Go easy on em-dashes (--): at most one per post, ideally zero. Prefer a comma, colon, parentheses, or a new sentence.

No AI-isms or filler buzzwords (ceremony, delve, seamless, robust, leverage). Say the plain thing.

Links to docs.zenable.io carry UTM params (?utm_source=blog&utm_medium=web).