mdcms-greenfield-init

MDCMS Greenfield Init

Bootstrap MDCMS in a repo that has no content yet. mdcms init scaffolds a minimal starter (one content type, one example post, a valid mdcms.config.ts) and syncs the schema. A follow-up mdcms push uploads the example.

When to use this skill

The user wants MDCMS for a new project and has no existing Markdown/MDX files to import. If the repo already has content, use mdcms-brownfield-init instead.

Prerequisites

• Server URL (self-host with mdcms-self-host-setup if needed).
• MDCMS API key with project + schema permissions.
• Project slug and environment name.
• Node.js / npm for npx mdcms.

Steps

1. Run init

npx mdcms init --non-interactive \
  --server-url "$MDCMS_SERVER_URL" \
  --project "$MDCMS_PROJECT" \
  --environment "$MDCMS_ENVIRONMENT" \
  --api-key "$MDCMS_API_KEY"

With no content on disk, init:

1. Scaffolds content/posts/ as the managed directory.
2. Generates a post type with title: z.string() and slug: z.string().optional().
3. Writes mdcms.config.ts.
4. Syncs the schema to the server.
5. Creates content/posts/example.md (a placeholder with frontmatter and a short body). Skip this last step with --no-example-post if the user does not want it.

If the user prefers a different starter directory, pass --directory <path> — the type is named after the last path segment.

2. Push the example to the server

npx mdcms push

init writes the file locally but does not import it. Running push uploads it so the user can immediately open Studio and see a real draft document.

3. Decide on the content model

At this point the repo has a minimal post type with two fields. Ask the user what their real content model looks like (blog posts with authors and tags? marketing pages? campaigns with localized variants?) and either:

• Start drafting directly in the scaffolded directory if the starter shape fits, or
• Delegate to mdcms-schema-refine to add the real types, fields, and references.