blog-init

To set up a blog project, you need to initialize a workspace by selecting a project folder and publishing repo, then generate a marker file alongside Posts/ and drafts/ directories. This process establishes your content pipeline configuration before writing begins.

Configuring a content pipeline requires selecting your local GitHub repo folder and capturing your author name. The initialization process writes a marker instructions file to wire your publishing repo without reading backend config files or starting new posts.

Yes, blog workflow initialization uses only writer-appropriate answers to create the project marker file and folders. It skips backend setup entirely, relying on folder pickers, author details, and a hero-vibe configuration to build the workspace.

Hero image vibe configuration stores one of four controlled visual palettes or style keywords during project setup. This ensures consistent release-gated hero image prompts are saved in the marker file for later publishing tasks.

Yes, blog project initialization optionally stores a slug-based live URL pattern. This helps link posts after publishing by recording the routing information in the generated instructions file without reading backend configurations.