Write Markdown, diagrams and equations

Write the source in Markdown editing, inspect it in Read and use Split when you want both together. Begin with a small file before adding extensions.

Try a complete brief

# Coastal survey

We will sample every **ten minutes**.

## Before launch
- [ ] Calibrate the camera
- [ ] Confirm the launch window

| Station | Interval |
| --- | --- |
| North | 10 min |
| South | 5 min |

[Read the instrument note](instruments.md)

Headings use #, emphasis uses asterisks and links use a label followed by a destination in parentheses. Keep the referenced file beside the brief or update its path.

Add a diagram in a fence

```mermaid
flowchart LR
  A[Receive reading] --> B{Valid?}
  B -->|Yes| C[Archive]
  B -->|No| D[Calibrate]
  D --> A
```

The fence language tells the renderer what to do. A mermaid block is rendered as a diagram; a python block is displayed as code. Compare six diagram forms.

Add an equation

The average is $\bar{x}$.

$$
\bar{x} = \frac{1}{n} \sum_{i=1}^{n} x_i
$$

Use inline math for short expressions and a display block for a formula that needs its own line. Keep definitions and units in the surrounding text.

Choose one of two parsing modes

Find the setting in Settings → Advanced → Markdown Compatibility. There are two choices, not a separate third “TFM” profile. An extension may render differently elsewhere even though the file remains readable text.

Check a portable handoff

• Keep attachments with the document and prefer relative file paths.
• Explain a diagram in prose and retain its source.
• Check extension support in the receiving renderer.
• Use PDF for a stable rendered result, and Markdown when the recipient needs to edit.