Welcome to the UnieAI docs

We now ship a dedicated MDX documentation surface inside the app router. Author guides in content/docs/{locale} and ship them with the same deployment pipeline as the rest of the site.

How the MDX docs work

Files live under content/docs/{locale}. Add nested folders to create nested routes.
Frontmatter controls sorting and description. order is optional and defaults to the bottom.
Pages render with custom MDX components for headings, lists, quotes, and code.
Locales follow the path prefix you already use (for example, /en/docs or /zh-TW/docs).

Frontmatter fields

---
title: Getting Started
description: The fastest way to ship with UnieAI.
order: 1
---

title renders as the page heading. description shows both in the hero and the sidebar. Use order to control navigation ordering when you add more pages.

Linking to other pages

Use regular Markdown links; internal links stay locale-aware:

[Overview](/en/docs) goes to this page for English
[Getting started](/en/docs/getting-started) jumps into the setup guide

External links open in a new tab automatically.

Rendering code and callouts

import { createClient } from "@unieai/sdk";

const client = createClient({ apiKey: process.env.UNIEAI_API_KEY! });

const response = await client.chat.completions.create({
  model: "unieai/aqua",
  messages: [{ role: "user", content: "Hello, UnieAI!" }]
});

console.log(response.choices[0].message);

MDX uses the same design tokens as the marketing pages, so your docs feel native to the product.

Add your first page

Duplicate this file or create a new one in content/docs/en.
Update the frontmatter title and description.
Run pnpm dev and visit /en/docs to see the rendered page.
Repeat for content/docs/zh-TW to localize the content.

That is all you need to start shipping product-ready documentation without leaving the codebase.