DocumentationEveryday use

Rust · 0.1.0

Write with Markdown

Format notes while keeping their source portable and readable.

The everyday toolkit

Use headings for structure, lists for steps, emphasis for a small amount of contrast, and fenced code blocks for examples. Preview the rendered memo after editing, especially when mixing links, images and code. Markdown formatting and tag recognition are separate rules.

## Reading note

One **important** point and a [source](https://example.com).

- A detail to revisit
- [ ] Try the idea

```text
A code block keeps literal text.
```

Literal text and links

Use inline code or a fenced block when text should be treated as code rather than ordinary note text. A #tag written inside code is not a normal tag occurrence. Check links before opening them and avoid placing access tokens or private URLs in a memo you plan to publish. Attachment access still follows the memo and file policies; Markdown does not bypass them.