Page frontmatter
Every page starts with a YAML frontmatter block at the top of the file, enclosed in triple dashes. At minimum, include atitle so the page appears correctly in the browser tab and sidebar. Adding a description improves SEO and provides users with a quick summary before they start reading.
Markdown basics
通用文档站点 supports standard Markdown for all common formatting needs. The following elements cover the majority of what you will use when writing documentation:| Element | Syntax | Result |
|---|---|---|
| Heading 1 | # Heading | Large section title |
| Heading 2 | ## Heading | Subsection title |
| Heading 3 | ### Heading | Minor subsection |
| Bold | **text** | text |
| Italic | *text* | text |
| Link | [text](url) | Clickable link |
| Inline code | `code` | code |
| Code block | ```lang | Syntax-highlighted block |
Callout components
Callouts let you draw your users’ attention to information that deserves special emphasis. 通用文档站点 provides four callout types, each with its own visual treatment:Use
<Note> for supplementary information that is helpful but not critical — context, background, or extra detail your users can safely skip.Use
<Info> for factual context such as prerequisites, permissions, or version requirements that users should be aware of before proceeding.Code blocks
Wrap code examples in triple backticks and always include a language tag immediately after the opening backticks. The language tag enables syntax highlighting, which makes code easier to read and scan.typescript, python, bash, json, yaml, and many more. You can also add an optional filename after the language tag — for example, ```typescript app.ts — to display the filename above the code block.
Steps
Use the<Steps> component when you need to guide users through a sequence of actions where order matters. Wrap each individual action in a <Step> with a descriptive title.
Once you have written your pages, head to Organizing docs with navigation and groups to learn how to structure them into a navigable sidebar for your users.