Using MDX for Static Content in Next.js

db.fyi uses local MDX files for all tool and resource content. No CMS and no database for phase one.

Stack

• gray-matter for frontmatter parsing.
• next-mdx-remote for rendering MDX body on the server.
• fs in getStaticProps / server components to read from src/content/ai and src/content/resources.

Schema

Each tool MDX has required frontmatter: name, tagline, category, pricing, featured, url, description. Optional: stars (sort order only; never displayed), features, toolType, image, metric. Metric is only shown when label, value, and sourceUrl (http/https) are present; no metric without a source link. Content quality: no filler; explain what the tool does.

Security

We only load MDX from src/content. No runtime fetch of remote MDX. No eval or user-generated MDX.