# A Quiet Writing Surface

## Opening

Long-form writing needs structure, but it also needs restraint. A document should provide landmarks without turning every line into a widget. Headings, lists, quotes, and code blocks are enough to make many real notes pleasant.

The editor still carries the original Markdown source. That matters because every cursor movement, selection, undo operation, and file save depends on the source staying stable.

## Section One

The first test is visual rhythm. A heading should make the next section easy to find. A paragraph with **important language** and *subtle emphasis* should remain readable. A phrase like `DocumentLineIndex` should stand out without interrupting the sentence.

> A good hybrid editor makes structure visible while keeping source nearby.

## Section Two

Lists should feel ordinary:

- Capture the thought.
- Add enough detail.
  - Keep nested ideas aligned.
  - Avoid visual clutter.
- Move on.

Ordered lists should also be readable:

1. State the problem.
2. Describe the tradeoff.
3. Choose the stable path.

## Section Three

Real notes often include small tables.

| Topic | Note |
| ----- | ---- |
| Rendering | Use attributed styling first |
| Editing | Keep source text canonical |
| Performance | Avoid document-wide work during typing |

And real notes often include small code fragments.

```swift
struct Note {
    var title: String
    var body: String
}
```

## Closing

The test is not whether this becomes a perfect preview. The test is whether a user can write documentation, meeting notes, research notes, and project plans without feeling like they are trapped in plain text.

