Blog
Visual flair (graphical) annotations
All docs use the shipped renderer: GFM, :::info / :::tip / :::warning / :::note callouts, tables, horizontal rules, and fenced code (see BlogMarkdownBody in @invizipoll/ui).
| Slug | Additions (this pass) |
|---|---|
| docs-enterprise-sso-saml-oidc | :::info intro; :::warning plan; :::tip IdP vs vault; section → Admin & Enterprise; SEO fields |
| docs-scim-directory-sync | :::info + :::warning entitlement; section Admin & Enterprise; SEO |
| docs-domain-verification-dns | :::tip DNS workflow; :::warning entitlement; section Admin & Enterprise; SEO |
| docs-encryption-model-overview | :::info intro; audience + SEO; --- before “Cryptographic building blocks” |
| docs-billing-trial-and-tier-limits | :::tip source of truth; table row “Trial (14-day)”; audience + SEO |
| docs-ai-poll-building | :::info privacy; tags + audience + SEO; --- before Privacy; reworded consent (no POST jargon) |
| docs-inviting-team-members | :::tip entry point to Admin → Users |
| docs-zero-knowledge-cryptography-requirements | :::note terminology; removed duplicate footnote; audience + SEO |
| docs-post-quantum-cryptography-architecture | :::info harvest-now; audience + SEO |
| docs-signup-workspace-and-handoff | :::tip slug choice; audience + SEO |
No new image URLs were added (static assets not deployed in this pass). To add hero screenshots later, place files on the marketing origin and use  in these bodies after deploy.
Optional product follow-up (not done here): Mermaid or video embeds would require BlogMarkdownBody + sanitizer work before using that syntax in CMS markdown.