Files
public-blog/content/posts/starter-mdx-showcase.mdx
2026-06-03 10:52:55 -05:00

74 lines
2.3 KiB
Plaintext

---
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.