Blog

Ops bulk import — operator checklist

  1. Pre-flight (optional): From the repo root (this folder’s default path is built into the script):

    pnpm --filter @invizipoll/api docs:validate-export
    

    For a different folder, pass a path relative to apps/api, e.g. ../../docs/Private/your-export, or use an absolute path. This runs the same collectPublishedDocsContentViolations rules as publish.

  2. Import: InviziPoll Ops → ContentBulk import — select the .md files (this folder or your Downloads copy). See apps/admin/src/lib/blog-markdown-import.ts for supported YAML (gray-matter ---).

  3. Status: All docs in this package default to draft. Review in the editor, then publish in Ops (published docs need a non-empty section).

  4. Blog rows (5) remain published in front matter; adjust in Ops if you need drafts first.

  5. Web deploy: The docs hub “Start here” first card expects slug docs-what-is-invizipoll. Deploy the web app after publishing that doc (or adjust DOCS_QUICK_START_JOURNEYS if you intentionally use a different slug).

  6. Smoke test after publish: GET /api/public/docs and spot-check GET /api/public/docs/<slug>.