What Is a Block Editor? Blocks, Pages and Databases

If you've opened Notion, Logseq or a similar app and noticed that every paragraph has its own little drag handle, you've already met the answer to "what is a block editor" — you just may not have had the name for it.

A block editor is a writing environment where the document isn't one continuous stream of text. Instead, it's a stack of independent units — blocks — where each paragraph, heading, image, list item or table is its own object that can be moved, transformed or nested.

That sounds like a small implementation detail. It changes almost everything about how the document behaves.

Blocks vs plain documents

In a traditional document — a Word file, a Google Doc, a plain text file — the content is fundamentally one long river of characters. Formatting is paint applied on top. If you want to move a section, you select it carefully, cut it, scroll, and paste, hoping the formatting survives.

In a block editor, the document is more like a stack of LEGO bricks. The paragraph you're reading would be one brick; the heading above it, another. Each block knows what type it is (paragraph, heading, bullet, image) and where it sits in the stack. Moving a section means grabbing its handle and dropping it somewhere else — the structure travels with it.

What is a block editor made of? The common block types

Most block editors share a core vocabulary:

• Text blocks — ordinary paragraphs, the default unit.
• Headings — which double as the document's outline, since each heading block knows its level.
• Lists — bulleted, numbered and to-do lists, where each item is its own nestable block.
• Toggles — collapsible blocks that hide their children until clicked, useful for FAQs, meeting agendas or anything you want tucked away.
• Tables and databases — the big one. A simple table block holds static rows; a database block holds entries with properties (status, date, owner) that you can filter, sort and view as a table, board or list.
• Embeds and media — images, videos, PDFs, code snippets, bookmarks and content pulled in from other services.

Because every one of these is "just a block," they compose freely: a toggle can contain a database, a list item can contain an image, a page can mix all of them without fighting the layout.

Why blocks matter: restructuring and mixed content

Two practical consequences fall out of the block model.

Restructuring becomes cheap. Writing is mostly rewriting, and rewriting is mostly rearranging. When every unit has a handle, reordering an essay's argument or a project doc's sections is a series of drags, not a copy-paste operation. You can also transform blocks in place — a paragraph becomes a heading, a list of bullets becomes a set of to-dos — without retyping anything.

Documents stop being just documents. Because a database is a block like any other, your project page can hold prose, a task board and a meeting-notes table on one page. That's the quiet reason block editors took over team wikis and personal knowledge bases alike: one page can be a document, a tracker and a dashboard at once. It also pairs naturally with linking between pages — backlinks turn those blocks into a connected web rather than isolated files.

Where block editors came from

The pattern has older roots — outliners have treated documents as nested nodes for decades — but Notion popularized the modern block editor when it made "everything is a block" the core of its product. The slash command (type "/" to insert any block type) and the drag handle became conventions that a wave of tools adopted, from Logseq and Anytype to WordPress's Gutenberg editor. Today "Notion-style editor" is practically shorthand for the whole category, and it's a major reason people compare tools like Notion and Obsidian in the first place — they represent the block and plain-file philosophies respectively.

Trade-offs vs plain markdown files

Honesty time: blocks are not free.

Plain markdown files have real virtues. They're readable in any text editor, trivially portable between apps, easy to sync and back up, and they'll open unchanged in thirty years. A block document, by contrast, is typically stored in an app-specific format — export usually flattens it to markdown, and things like database views don't survive the trip. If maximum longevity and portability are your top priorities, plain files are the safer bet, and tools built on them (like Obsidian) are genuinely good.

What you give up with plain files is everything above: drag-and-drop restructuring, databases, toggles, and rich mixed content. Where your notes physically live is a separate question from the editing model — a block editor can still be local-first, meaning the data stays on your device (we explain the distinction in what local-first software means). That combination is exactly what Stacy does: a Notion-style block editor with databases and backlinks, storing notes locally with optional sync.

Most people don't choose on ideology, though. They choose based on how they organize — and if you haven't settled that yet, start with how to organize notes before picking an editor model.

The recap

So, what is a block editor? It's an editor where every paragraph, heading, list, table and embed is an independent, draggable, transformable unit. Blocks make restructuring cheap and let one page mix prose with databases and media; the price is a more app-specific format than plain markdown. If your notes are things you rearrange and build on — not just write once — blocks are worth it.