Quickstart

Run the installer

npx agentblog@latest init

It checks the requirements above, then asks you four questions: where your site lives in production, your brand name, the slug you want as the default author, and where posts should come from (answer mdx unless you know you want something else).

Then it copies the files in and patches the two config files a file copier cannot reach. It shows you every change first and backs up every file it edits, so npx agentblog@latest revert puts everything back.

Add one line to your stylesheet

Open your global stylesheet, usually app/globals.css, and add the second line here, after the Tailwind import.

@import 'tailwindcss';
@import '../styles/agentblog.css';

In a src/ layout the path is '../../styles/agentblog.css'.

This is the one step nothing will remind you about. That file carries the article typography. Without it your posts render as correct HTML in a single undifferentiated font size, and no error appears anywhere.

Put yourself in the author list

Open content/authors.json and replace the placeholder record with your own.

[
  {
    "slug": "editorial",
    "name": "Your Name",
    "role": "Founder",
    "bio": "One or two sentences about who you are and why you know this subject.",
    "sameAs": ["https://www.linkedin.com/in/you", "https://github.com/you"]
  }
]

Keep the editorial slug for now. The two example posts reference it, and a post that names an author who does not exist fails the build.

sameAs is worth filling in. It is how a search engine or an assistant connects "this post's author" to a real person rather than a name, which is the whole mechanism behind author credibility signals.

Look at it

npm run dev

Open http://localhost:3000/blog. You should see two example posts, styled with your own colours and fonts, and each one opening onto a full article page.

If the text looks unstyled, step 2 did not take. If the build printed a warning mentioning htmlLimitedBots, run npx agentblog@latest doctor --fix.

Check the install

npx agentblog@latest doctor

This reads your config and reports anything still missing, with the fix for each one. It exits non-zero when it finds an error, so it also works as a CI step.