Your notes are not documents.
They are structures.

Open a word processor and you are looking at a metaphor from 1980: a sheet of paper. Everything you type joins one long stream of text that flows from the top of page one to the bottom of the last page. That metaphor made sense when the goal was printing. It makes much less sense when the goal is thinking, and most notes exist to help you think.

This lesson explains the idea that quietly replaced the paper metaphor in modern note tools: the block. Once you see notes as structures built from blocks rather than streams of text, a lot of things change, including how you write, how you reorganize, and how well software (and lately, AI) can work with what you wrote.

The problem with a stream of text

A text stream has no internal shape the software can see. To a word processor, a heading is just a line someone made bold and large. A checklist is just lines that start with a square character. If you want to move a section, you select it by hand, hoping you caught the whole thing, and paste it somewhere else, hoping the formatting survives.

The deeper cost is that a stream resists rearrangement, and rearrangement is most of what thinking on paper looks like. Meeting notes want to become action items. A brainstorm wants to become an outline. A draft wants its third section moved first. In a stream, every one of those moves is manual surgery. So people avoid the surgery, and their notes stay in the order the thoughts happened to arrive, which is rarely the order that makes them useful.

What a block actually is

A block is a unit of content that the software understands as one thing: this is a paragraph, that is a heading, that is a to-do with a checked state, that is a table with rows and columns. A page is not a stream; it is a list (sometimes a tree) of blocks.

Because each block knows what it is, three operations become trivial that were painful before:

• Move. Drag a block, or a heading with everything under it, anywhere on the page or to another page. Nothing tears.
• Convert. Turn a paragraph into a heading, a list into to-dos, a set of bullets into a table. The content stays; the type changes.
• Nest. Put blocks inside blocks: sub-tasks under a task, detail under a toggle, a whole page inside another page.

A field guide to block types

Most block editors converge on a similar cast. Knowing what each type is for matters more than knowing every option in the menu.

• Headings carve a page into sections and give you a skeleton to navigate and reorganize by. If a page has more than a screen of content and no headings, it is hiding its own structure.
• Paragraphs are the default: prose, reasoning, narrative. Everything that needs sentences.
• Bulleted and numbered lists hold parallel items and ordered steps. If the order matters, number it; readers treat numbered steps as a procedure.
• To-dos are lists with state. The checkbox is a tiny database: done or not done. Meeting notes that end in to-dos are meetings that produced decisions.
• Quotes mark words that are not yours: a customer verbatim, a line from a spec, a source you are responding to.
• Code blocks preserve text exactly, with syntax highlighting. Not only for programmers: config snippets, terminal commands, and email templates all belong here, because a code block promises "copy this exactly".
• Tables compare things across the same dimensions. More on when to reach for one below.
• Callouts are blocks that refuse to be skimmed past: an icon, a background color, one important statement.
• Toggles hide detail behind a clickable heading. They are how long pages stay short.
• Dividers, images, embeds, and diagrams round out the set. In NoteX Desktop the list runs deep: multi-column layouts, video and audio embeds, LaTeX math, and nine kinds of Mermaid diagrams, including mind maps, all as ordinary blocks. The full inventory lives on the block editor page.

Two ways to summon a block

Block editors would be unbearable if every block required a trip to a toolbar. Two conventions keep your hands on the keyboard.

The slash menu. Type / anywhere and a searchable menu of every block type appears. Type a few letters to filter, press Enter, keep writing. The slash key is the whole API: you never need to memorize where anything lives, only that / will find it.

Markdown shortcuts. If you already know Markdown, the conventions carry over as live shortcuts: # and a space becomes a heading, - a bullet, 1. a numbered list, [] a to-do, > a quote, --- a divider, and three backticks open a code block. You type plain characters; the editor upgrades them to blocks as you go.

Learn five of these and note-taking speeds up noticeably, because structure stops costing keystrokes. NoteX supports both conventions on desktop and web; the complete list is on the slash command cheat sheet.

Toggles, callouts, tables: choosing well

Three block types get misused more than the rest, usually by being used too much or not at all.

Use a toggle when information is real but optional for most readers: background context, raw data behind a summary, the long version of a decision. A good test: if 8 out of 10 readers should skip it, fold it. Do not use toggles to hide things people must read; a buried action item is a missed action item.

Use a callout for the one or two statements per page that must survive skimming: the decision, the deadline, the warning. Callouts lose their power in crowds. A page with seven callouts has zero callouts.

Use a table when you are comparing several things across the same attributes: options against criteria, environments against URLs, risks against owners. If you find yourself writing parallel sentences ("Option A costs X and takes Y. Option B costs Z and takes W."), that is a table asking to exist. And when a table starts accumulating rows over weeks and needs sorting or filtering, it wants to become a database, which is its own topic: see databases.

Structure is thinking made visible

Here is the honest argument for blocks, and it is not about software features. Writing things down is how most of us find out what we actually think. The first draft of any idea is disordered because thinking is disordered. The value appears in the second pass, when you group, rank, promote, and discard.

Blocks make that second pass cheap. When moving a section costs one drag, you reorganize freely, and every reorganization is a small act of thinking: these two points are really one, this detail is actually the headline, this whole section is someone else's problem. A stream punishes revision; blocks invite it. Over months, that difference compounds into notes that are genuinely organized rather than merely accumulated.

There is a quieter benefit too. Because blocks are typed structure rather than styled text, software can do more with them: convert them to clean Markdown, index them precisely for search, and hand them to AI in a form it can parse reliably. That thread runs through this whole course, and lesson four picks it up directly.

Next, though, a more fundamental question than what your notes are made of: where they should live, and who really holds them.