This is what an AI/RAG pipeline sees when it indexes this page — the same output served at https://camelmind-docs.vercel.app/api/llms/before-you-begin/markdown-in-10.Back to doc

Rendered doc

Markdown in 10 minutes

Learn the Markdown syntax you need to start writing CamelMind documentation in just a few minutes.

Markdown offers a straightforward way to write formatted documents using plain text. Instead of clicking toolbar buttons, authors use a few simple characters to create headings, lists, links, images, and other elements.

You only need a core set of Markdown features to write effective documentation.

This guide covers all essential syntax requirements to help you start authoring content in CamelMind.

Tip

Authors write CamelMind pages in MDX—Markdown with support for React components. Start by learning standard Markdown, then explore CamelMind's built-in components such as Callout, Steps, Tabs, and Details to create richer documentation.


Defining page title and headings in CamelMind

Unlike plain Markdown, CamelMind uses the page frontmatter to specify the page title.

Instead of writing a top-level heading in the document body:

md
# Document Title Example

define the page title in the frontmatter block:

yaml
---
title: Document Title Example
description: Learn how to configure titles in CamelMind.
---

CamelMind automatically renders the page title from the title field.

Begin document content with a level 2 heading (##) for the primary section:

md
---
title: Document Title Example
description: Learn how to configure titles in CamelMind.
---

## Primary Section Header  {/* toc:exclude */}

Install Node.js before creating your first CamelMind site.

## Secondary Section Header {/* toc:exclude */}

Continue to the installation guide.

Structuring content with heading levels in CamelMind

Organize document content into a logical hierarchy using heading levels.

HeadingWhen to use
##Main sections of the page.
###Subsections within a section.
####Details within a subsection. Use sparingly.

For example, structure your CamelMind document sections and subsections using the following hierarchy:

md
## Advanced CamelMind Feature Configuration {/* toc:exclude */}

In this primary section, configure high-level settings for your CamelMind documentation site.

### Primary Feature Settings in CamelMind {/* toc:exclude */}

In this subsection, adjust specific settings for individual feature options.

#### Advanced Optional Feature Options

Customize analytics, search, and authentication parameters.
Tip

Treat headings as an outline. Most CamelMind pages require only ## and ### headers. When a document requires numerous #### headings, consider splitting the content across multiple pages instead.


Creating paragraphs in Markdown

Separate individual paragraphs by inserting a blank line between text blocks.

md
This is the first paragraph.

This is the second paragraph.

Formatting text with inline styles

Apply emphasis to text using standard inline formatting characters.

MarkdownResult
**Bold**Bold
*Italic*Italic
***Bold italic***Bold italic
`code`code
~~Strikethrough~~Strikethrough

Example:

md
Use **CamelMind** to build beautiful documentation.

Run `npm run dev` to preview your site.

displays as:

Use CamelMind to build beautiful documentation.

Run npm run dev to preview your site.


Creating bulleted and numbered lists

Unordered lists

Use hyphens or asterisks to create bulleted list items:

md
- Install Node.js
- Create your site
- Start writing

displays as:

  • Install Node.js
  • Create your site
  • Start writing

Ordered lists

Use numbers followed by periods to create ordered list items:

md
1. Install Node.js
2. Run the CLI
3. Preview your site

displays as:

  1. Install Node.js
  2. Run the CLI
  3. Preview your site

Construct hyperlinks using square brackets for link text and parentheses for the target URL.

md
[Installation](/getting-started/installation)

[Writing Content](/getting-started/writing-content)

[https://camelmind.dev](https://camelmind.dev)

Embedding images in content

Embed images using exclamation marks, square brackets, and parentheses:

md
![Architecture Diagram](/images/architecture.svg)

Formatting blockquotes

Highlight key quotes or important information callouts.

md
> Documentation is part of the product.

displays as:

Documentation is part of the product.


Inserting code blocks and syntax highlighting

Enclose multi-line code examples inside triple backtick fences (```).

bash
npm install
npm run dev

Specify a language identifier after the opening backticks to enable syntax highlighting.

Common supported languages include:

  • bash
  • typescript
  • tsx
  • json
  • yaml
  • html
  • css

Example:

yaml
- label: Home
  slug: /

Formatting data with tables

Construct structured data tables using pipe characters (|).

md
| Command | Description |
| --- | --- |
| `npm install` | Install project dependencies |
| `npm run dev` | Start the development server |

displays as:

CommandDescription
npm installInstall project dependencies
npm run devStart the development server

CamelMind supports link tooltips using standard Markdown syntax.

Add a title string in double quotation marks after the target URL:

md
[Installation Guide](/getting-started/installation "Create your first CamelMind site")

[Node.js](https://nodejs.org/ "JavaScript runtime used by CamelMind")

When users hover over the link, the browser displays the title string inside a tooltip popup.

Installation Guide

Node.js

Tip

Keep tooltip text concise and descriptive. Use tooltips to supply supplemental context without disrupting reading flow.


Inserting horizontal section dividers

Separate distinct sections using three consecutive dashes.

md
---

displays as:


Escaping special Markdown characters

To render Markdown formatting syntax as literal text, precede the character with a backslash (\).

md
\# This is not a heading

displays as:

# This is not a heading


Comparing Markdown versus MDX in CamelMind

Standard Markdown satisfies requirements for most documentation pages.

When pages require complex component layouts, CamelMind allows authors to combine Markdown content with React components through MDX.

For example, instead of writing a basic blockquote:

md
> Remember to restart the server.

authors can insert a Callout component:

mdx
<Callout type="tip">
Restart the development server after changing your configuration.
</Callout>

CamelMind includes built-in MDX components that function out of the box without requiring manual import statements. See Use MDX Components for complete usage instructions.


Next step: Start authoring documentation

Congratulations! 🎉

You now have full knowledge of essential Markdown syntax for CamelMind authoring.

Most documentation pages rely on the syntax detailed in this guide. As your documentation suite grows, incorporate CamelMind built-in MDX components to construct interactive, engaging content pages. Continue to Writing Content to create your first page.

What the AI sees

1> For a complete documentation index, see /llms.txt. To read any public page as Markdown, append .md to the URL.
2 
3Markdown offers a straightforward way to write formatted documents using plain text. Instead of clicking toolbar buttons, authors use a few simple characters to create headings, lists, links, images, and other elements.
4 
5You only need a core set of Markdown features to write effective documentation.
6 
7This guide covers all essential syntax requirements to help you start authoring content in CamelMind.
8 
9<Callout type="tip">
10Authors write CamelMind pages in MDX—Markdown with support for React components. Start by learning standard Markdown, then explore CamelMind's built-in components such as [Callout](/getting-started/mdx-components#callout), [Steps](/getting-started/mdx-components#steps), [Tabs](/getting-started/mdx-components#tabs), and [Details](/getting-started/mdx-components#details-collapsible-sections) to create richer documentation.
11</Callout>
12 
13---
14 
15## Defining page title and headings in CamelMind
16 
17Unlike plain Markdown, CamelMind uses the page frontmatter to specify the page title.
18 
19Instead of writing a top-level heading in the document body:
20 
21```md
22# Document Title Example
23```
24 
25define the page title in the frontmatter block:
26 
27```yaml
28---
29title: Document Title Example
30description: Learn how to configure titles in CamelMind.
31---
32```
33 
34CamelMind automatically renders the page title from the `title` field.
35 
36Begin document content with a **level 2 heading (`##`)** for the primary section:
37 
38```md
39---
40title: Document Title Example
41description: Learn how to configure titles in CamelMind.
42---
43 
44## Primary Section Header {/* toc:exclude */}
45 
46Install Node.js before creating your first CamelMind site.
47 
48## Secondary Section Header {/* toc:exclude */}
49 
50Continue to the installation guide.
51```
52 
53### Structuring content with heading levels in CamelMind {/* toc:exclude */}
54 
55Organize document content into a logical hierarchy using heading levels.
56 
57| Heading | When to use |
58| --- | --- |
59| `##` | Main sections of the page. |
60| `###` | Subsections within a section. |
61| `####` | Details within a subsection. Use sparingly. |
62 
63For example, structure your CamelMind document sections and subsections using the following hierarchy:
64 
65```md
66## Advanced CamelMind Feature Configuration {/* toc:exclude */}
67 
68In this primary section, configure high-level settings for your CamelMind documentation site.
69 
70### Primary Feature Settings in CamelMind {/* toc:exclude */}
71 
72In this subsection, adjust specific settings for individual feature options.
73 
74#### Advanced Optional Feature Options
75 
76Customize analytics, search, and authentication parameters.
77```
78 
79<Callout type="tip">
80Treat headings as an outline. Most CamelMind pages require only `##` and `###` headers. When a document requires numerous `####` headings, consider splitting the content across multiple pages instead.
81</Callout>
82 
83---
84 
85## Creating paragraphs in Markdown
86 
87Separate individual paragraphs by inserting a blank line between text blocks.
88 
89```md
90This is the first paragraph.
91 
92This is the second paragraph.
93```
94 
95---
96 
97## Formatting text with inline styles
98 
99Apply emphasis to text using standard inline formatting characters.
100 
101| Markdown | Result |
102| --- | --- |
103| `**Bold**` | **Bold** |
104| `*Italic*` | *Italic* |
105| `***Bold italic***` | ***Bold italic*** |
106| `` `code` `` | `code` |
107| `~~Strikethrough~~` | ~~Strikethrough~~ |
108 
109Example:
110 
111```md
112Use **CamelMind** to build beautiful documentation.
113 
114Run `npm run dev` to preview your site.
115```
116 
117displays as:
118 
119Use **CamelMind** to build beautiful documentation.
120 
121Run `npm run dev` to preview your site.
122 
123---
124 
125## Creating bulleted and numbered lists
126 
127### Unordered lists {/* toc:exclude */}
128 
129Use hyphens or asterisks to create bulleted list items:
130 
131```md
132- Install Node.js
133- Create your site
134- Start writing
135```
136 
137displays as:
138 
139- Install Node.js
140- Create your site
141- Start writing
142 
143### Ordered lists {/* toc:exclude */}
144 
145Use numbers followed by periods to create ordered list items:
146 
147```md
1481. Install Node.js
1492. Run the CLI
1503. Preview your site
151```
152 
153displays as:
154 
1551. Install Node.js
1562. Run the CLI
1573. Preview your site
158 
159---
160 
161## Adding links to documents
162 
163Construct hyperlinks using square brackets for link text and parentheses for the target URL.
164 
165```md
166[Installation](/getting-started/installation)
167 
168[Writing Content](/getting-started/writing-content)
169 
170[https://camelmind.dev](https://camelmind.dev)
171```
172 
173---
174 
175## Embedding images in content
176 
177Embed images using exclamation marks, square brackets, and parentheses:
178 
179```md
180![Architecture Diagram](/images/architecture.svg)
181```
182 
183---
184 
185## Formatting blockquotes
186 
187Highlight key quotes or important information callouts.
188 
189```md
190> Documentation is part of the product.
191```
192 
193displays as:
194 
195> Documentation is part of the product.
196 
197---
198 
199## Inserting code blocks and syntax highlighting
200 
201Enclose multi-line code examples inside triple backtick fences (```).
202 
203```bash
204npm install
205npm run dev
206```
207 
208Specify a language identifier after the opening backticks to enable syntax highlighting.
209 
210Common supported languages include:
211 
212- `bash`
213- `typescript`
214- `tsx`
215- `json`
216- `yaml`
217- `html`
218- `css`
219 
220Example:
221 
222```yaml
223- label: Home
224 slug: /
225```
226 
227---
228 
229## Formatting data with tables
230 
231Construct structured data tables using pipe characters (`|`).
232 
233```md
234| Command | Description |
235| --- | --- |
236| `npm install` | Install project dependencies |
237| `npm run dev` | Start the development server |
238```
239 
240displays as:
241 
242| Command | Description |
243| --- | --- |
244| `npm install` | Install project dependencies |
245| `npm run dev` | Start the development server |
246 
247---
248 
249## Adding tooltips to Markdown links
250 
251CamelMind supports link tooltips using standard Markdown syntax.
252 
253Add a title string in double quotation marks after the target URL:
254 
255```md
256[Installation Guide](/getting-started/installation "Create your first CamelMind site")
257 
258[Node.js](https://nodejs.org/ "JavaScript runtime used by CamelMind")
259```
260 
261When users hover over the link, the browser displays the title string inside a tooltip popup.
262 
263[Installation Guide](/getting-started/installation "Create your first CamelMind site")
264 
265[Node.js](https://nodejs.org/ "JavaScript runtime used by CamelMind")
266 
267<Callout type="tip">
268Keep tooltip text concise and descriptive. Use tooltips to supply supplemental context without disrupting reading flow.
269</Callout>
270 
271---
272 
273## Inserting horizontal section dividers
274 
275Separate distinct sections using three consecutive dashes.
276 
277```md
278---
279```
280 
281displays as:
282 
283---
284 
285## Escaping special Markdown characters
286 
287To render Markdown formatting syntax as literal text, precede the character with a backslash (`\`).
288 
289```md
290\# This is not a heading
291```
292 
293displays as:
294 
295\# This is not a heading
296 
297---
298 
299## Comparing Markdown versus MDX in CamelMind
300 
301Standard Markdown satisfies requirements for most documentation pages.
302 
303When pages require complex component layouts, CamelMind allows authors to combine Markdown content with React components through **MDX**.
304 
305For example, instead of writing a basic blockquote:
306 
307```md
308> Remember to restart the server.
309```
310 
311authors can insert a Callout component:
312 
313```mdx
314<Callout type="tip">
315Restart the development server after changing your configuration.
316</Callout>
317```
318 
319CamelMind includes built-in MDX components that function out of the box without requiring manual import statements. See [Use MDX Components](/getting-started/mdx-components) for complete usage instructions.
320 
321---
322 
323## Next step: Start authoring documentation
324 
325Congratulations! 🎉
326 
327You now have full knowledge of essential Markdown syntax for CamelMind authoring.
328 
329Most documentation pages rely on the syntax detailed in this guide. As your documentation suite grows, incorporate CamelMind built-in MDX components to construct interactive, engaging content pages. Continue to [Writing Content](/getting-started/writing-content) to create your first page.

Issues (0)

No AI-friendliness issues found.