Build

Content your editors will actually use, in the same repo.

Posts, pages, categories, tags, comments, and media are models like any other, which means they get the dashboard, the generated API, and the migrations without a second system to host, patch, and keep in sync with the site.

What you get.

All of it in the same install, with nothing to wire together first.

Posts and pages

Markdown body, excerpt, author, publish state, and stable slugs. Both are editable in the dashboard and readable over the API.

Taxonomy

Categories and tags through the categorizable and taggable traits, with the pivot tables migrated for you.

Comments

The commentable trait adds threads, moderation state, and the relations to any model, not just posts.

Media

Images, attachments, and assets go through the same storage drivers the rest of the app uses.

Feeds

RSS and a sitemap are generated from the content that exists, so they cannot drift from it.

Docs and blog

BunPress docs at /docs and a Markdown blog at /blog build and deploy with the site, from one command.

From the command line.

Buddy scaffolds, runs, and ships this the same way it does the rest of the app.

buddy make:model Article buddy migrate --diff buddy dev docs

These share the same models, config, and types, so using them together costs nothing extra.