Managing the blog with AI

Everything the Blog panel does, you can also do by chat — and a few things are faster that way. The blog has its own family of AI commands that execute directly, without a long build turn.

Writing

• Write a post from scratch — “write a blog post about sustainable packaging”. You can steer it: length (short / long), tone (casual / professional / technical), author, categories, whether to publish right away, and even the cover (“with a cover image of a forest”).
• Continue the post you’re viewing — open a post in the preview and say “continue the body” or “add a section about pricing”. Genesis knows which post you’re on and extends its body.

Managing

All of these resolve the post from how you refer to it — by title fragment or slug (“the Tesla post”, “my latest post”):

• Publish / unpublish — “publish the launch post”, “make that post a draft again”.
• Edit metadata — “rename the Tesla post to Launch Day”, “set the author to Sarah”, “move it to the News category”, “change the cover”.
• Delete — “delete the post about X” (removes it everywhere: page, listing, feed).
• Add authors and categories — “add author John Doe with a short bio”, “new category Tutorials, blue”.

Note

One thing chat can’t do either: renaming a slug (the URL part). It’s locked to protect shared links — delete and recreate the post if the URL must change.

Fixing

Three repair commands for when something looks wrong:

• “No header on my blog” — installs your site’s header and footer on all blog pages. Needed if the blog was enabled before your header existed, or navigation got lost along the way.
• “Fix the blog layouts” — resets the four blog page templates to their canonical state. Use when the blog’s structure itself is broken. (It’s a reset — custom styling of those templates is replaced.)
• “Repair broken blog posts” — rebuilds post files and the blog’s internal index when posts are missing from the list or won’t render.

A safety note

The blog’s content pipeline is protected: the AI can’t quietly invent or overwrite post files during unrelated edits — posts are only created and changed through the blog commands and the Blog panel. Your content stays where you put it.