docs: add starter mdx posts

content/posts/designing-with-nextjs.mdx

@@ -0,0 +1,33 @@
+---
+title: "Designing With Next.js"
+date: "2026-05-22"
+excerpt: "A short sample note about pairing interface design decisions with static Next.js content."
+tags:
+  - Design
+  - Next.js
+  - Web Dev
+author: "Starter Content"
+coverImage: "/starter-diagram.svg"
+---
+
+This sample note gives tag pages another realistic post to list. It is intentionally brief and ready to replace.
+
+![Simple local diagram for a starter design post](/starter-diagram.svg)
+
+## A tiny design checklist
+
+- Keep headings scannable.
+- Pair every visual with helpful alt text.
+- Use consistent tags so archive pages feel populated.
+
+The same content can support readers and tooling: humans get structure, while static route generation gets predictable params.
+
+```ts title="content-tags.ts" {3}
+export const starterTags = [
+  'Design',
+  'Next.js',
+  'Web Dev',
+]
+```
+
+> Replace this with a real design journal, launch note, or tutorial when you are ready.

content/posts/math-notes-for-builders.mdx

@@ -0,0 +1,33 @@
+---
+title: "Math Notes for Builders"
+date: "2026-05-08"
+excerpt: "A compact starter post that keeps Math and Code tags populated while checking equation rendering."
+tags:
+  - Math
+  - Code
+  - Web Dev
+author: "Starter Content"
+---
+
+This replaceable note exists to keep the **Math**, **Code**, and **Web Dev** tag pages meaningful during early validation.
+
+## Tiny model
+
+Inline math can express a quick estimate like $n \log n$, while display math can show the full relationship:
+
+$$
+T(n) = O(n \log n) + O(k)
+$$
+
+## Practical reminder
+
+- Prefer simple explanations before formulas.
+- Add runnable code when it clarifies an idea.
+- Link back to related posts, such as the [starter showcase](/posts/starter-mdx-showcase/).
+
+```js title="estimate.js" {1,4}
+export function estimate(items, constant = 1) {
+  const n = Math.max(items.length, 1)
+  return n * Math.log2(n) + constant
+}
+```

content/posts/starter-mdx-showcase.mdx

@@ -0,0 +1,73 @@
+---
+title: "Starter MDX Showcase"
+date: "2026-06-03"
+excerpt: "Sample starter content demonstrating math, local images, links, tables, tasks, and code blocks for validating blog routes."
+tags:
+  - Design
+  - Next.js
+  - Math
+  - Code
+  - Web Dev
+author: "Starter Content"
+coverImage: "/starter-showcase.svg"
+---
+
+This is deliberately sample content for a fresh blog. Replace it with your own writing once the routes, tags, and search experience are validated.
+
+![Abstract gradient card used as a local starter cover](/starter-showcase.svg)
+
+## What this post covers
+
+- A local image from `public/` referenced with an absolute path.
+- Links to [Next.js](https://nextjs.org/) and an internal [tag page](/tags/web-dev/).
+- GFM tables, task lists, blockquotes, code fences, and math.
+
+> Starter posts should be easy to delete, but rich enough to prove the publishing pipeline works end to end.
+
+## Markdown and GFM examples
+
+| Feature | Purpose | Status |
+| --- | --- | --- |
+| Tags | Builds static tag pages | Ready |
+| Math | Checks KaTeX rendering | Ready |
+| Code | Checks syntax highlighting | Ready |
+
+- [x] Confirm route generation has at least one post.
+- [x] Confirm spaced tags such as **Web Dev** create usable params.
+- [ ] Replace this demo with a real article.
+
+Inline code like `generateStaticParams` should be readable inside a sentence, and inline math such as $E = mc^2$ should render without extra setup.
+
+Display math is useful for longer equations:
+
+$$
+\operatorname{score}(post) = \frac{links + images + code}{reading\ time}
+$$
+
+## Code with title and highlighted lines
+
+```tsx title="components/example-card.tsx" {2,6-8}
+type ExampleCardProps = {
+  title: string
+  href: string
+}
+
+export function ExampleCard({ title, href }: ExampleCardProps) {
+  return <a href={href}>{title}</a>
+}
+```
+
+## Lists, links, and details
+
+1. Draft the article in MDX.
+2. Add concrete examples and screenshots.
+3. Link to useful references, such as the [MDX docs](https://mdxjs.com/).
+
+<details>
+  <summary>Why keep demo content obvious?</summary>
+  <p>Because starter posts are fixtures for validation, not permanent editorial content.</p>
+</details>
+
+## Closing note
+
+This post intentionally exercises common authoring features so the owner can validate static post routes, tag pages, and future search indexing with realistic but replaceable content.