This is a template, not a real post. It exists so `/blog` and `/blog/hello-cleverqa` render and are testable before the first real post is written. Delete this paragraph (and the rest of this explanation) when you replace the file.
How to add a real post
1. Create a new file at `content/blog/<your-slug>.md` (or edit this one and rename it — the filename becomes the URL, so `content/blog/my-post.md` publishes at `/blog/my-post`). 2. Fill in the frontmatter block at the top of the file between the two `---` lines: - `title` — required. The page's H1 and `<title>` tag. - `date` — required. An ISO date like `2026-09-18`, used for sorting (newest first) and the `BlogPosting` structured data. - `description` — required. One or two sentences. Used as the meta description and the `/blog` index excerpt — write it for a search result, not just as a summary. - `author` — optional. Defaults to "The CleverQA Team" if omitted. 3. Write the post body below the closing `---` in plain paragraphs. Leave a blank line between paragraphs. `## Heading` and `### Subheading` work for section headings, `- item` lines (one per line) work for bullet lists, and `bold` works for emphasis. 4. Link to other pages on the site with `link text` — for example pricing, the Sentry comparison, or the review scanner tool. This is how a post distributes authority to the rest of the site, so link out where it's genuinely relevant, not for its own sake. 5. Delete `content/blog/hello-cleverqa.md` once you have at least one real post, or leave it as a second post if you'd rather keep the walkthrough around for later — either is fine, nothing else depends on this specific file.
That's it — no build step, no registry to update. The post shows up on `/blog`, gets its own page at `/blog/<your-slug>`, and is added to the sitemap automatically the next time the site builds.
What NOT to do here
Don't add a new markdown/MDX npm dependency to render post bodies — the renderer used here is intentionally small (paragraphs, `##`/`###` headings, `- ` bullet lists, `bold`, and `text` links; see `apps/web/src/lib/markdown/block-markdown-pure.ts`). If a post genuinely needs more than that (tables, images, code blocks), that's worth a conversation before reaching for a dependency, not a silent workaround.