Publishing

Publishing to Your Blog

Your blog is the one channel you fully own, and if you're a developer it's probably a git repository — Next.js, Astro, Hugo, markdown files in a content folder, deployed on push. Most tools would ask you to move that into their CMS. GoShipFast goes the other direction: it publishes into your repo, the way you would.

How it works

When an article in the Article Studio reaches its final Publish stage (on the desktop app, with a working folder bound to your site's repo), the agent takes over and does what a careful teammate would:

1. Locates your blog content directory in the repository — where your existing posts live.
2. Studies your existing posts and writes the new article as a matching file: same frontmatter fields (title, date, description, tags, author — whatever your site uses), a clean semantic slug, your locale layout if you have one.
3. Self-checks the format against its neighbors — frontmatter parses, images resolve, structure matches.
4. Commits and pushes. If your hosting deploys on push (Vercel, Netlify, Pages), the article is live minutes later.

The article's illustrations were already rendered during the Illustrations stage, so images ship with the post. Afterward the article shows Published with a View live link, and it enters your analytics like any other channel.

Because it's the agent doing the work in chat, you can watch each step, see the diff before it's committed, and steer ("use category 'engineering'", "put it under /essays instead").

What you need

• The desktop app, with your site's repo cloned locally and bound as the brand's working folder.
• A blog that lives as files in that repo — MDX, Markdown, any static-site convention. If your existing posts have a consistent shape, the agent will match it; if the blog is empty, it will establish a sensible one and you can adjust.
• Push access from your machine (the agent uses your local git credentials, same as you).

Scheduling and alternatives

• Schedule — approved articles can be placed on the content calendar and publish at the scheduled time.
• Retry — a failed publish keeps its reason in the publish log and can be retried.
• No git blog? The multi-platform preview's Blog variant still gives you a clean, formatted rendering to paste into any CMS, and the article can always be exported from the editor.

Why git publishing is worth it

Every article in your repo is portable, versioned, and yours — the compounding asset argument in its most literal form. Platform posts drive the spike; the blog holds the value. Ship both from the same pipeline.