Ops bulk import — operator checklist
-
Pre-flight (optional): From the repo root (this folder’s default path is built into the script):
pnpm --filter @invizipoll/api docs:validate-exportFor a different folder, pass a path relative to
apps/api, e.g.../../docs/Private/your-export, or use an absolute path. This runs the samecollectPublishedDocsContentViolationsrules as publish. -
Import: InviziPoll Ops → Content → Bulk import — select the
.mdfiles (this folder or your Downloads copy). Seeapps/admin/src/lib/blog-markdown-import.tsfor supported YAML (gray-matter---). -
Status: All docs in this package default to
draft. Review in the editor, then publish in Ops (published docs need a non-emptysection). -
Blog rows (5) remain
publishedin front matter; adjust in Ops if you need drafts first. -
Web deploy: The docs hub “Start here” first card expects slug
docs-what-is-invizipoll. Deploy the web app after publishing that doc (or adjustDOCS_QUICK_START_JOURNEYSif you intentionally use a different slug). -
Smoke test after publish:
GET /api/public/docsand spot-checkGET /api/public/docs/<slug>.
