← Blog

The Distraction-Free Editor — Why a Quiet Page Helps You Write More

The Distraction-Free Editor — Why a Quiet Page Helps You Write More

The default modern editor is a toolbar. Bold, italic, headings, lists, code, link, image, table, formula, callout, embed, mention, slash-menu, AI-assist, comment. It's all visible all the time. It's all available the second you start typing.

That maximalism makes sense for a collaborative doc tool. It's the wrong default for a journal.

Jottii's editor is built around the opposite intuition: hide everything you don't need, until you need it. Here's how it works in practice and why it changes the texture of the writing.

What's there

The journal page is mostly white space. A title field at the top. A body underneath. The cursor blinking. That's the visual baseline.

When you select text, formatting options appear next to the selection — not in a fixed bar at the top. Bold, italic, strikethrough, headings (H1 / H2), bullet and numbered lists, quote, inline code, code block, link. Markdown shortcuts also work — **bold**, # heading, - list. If you know them, you never need the toolbar at all.

When you don't have text selected, the page is silent. There's nothing to look at, click, or be distracted by.

What's not there

Deliberately omitted, as of today:

These aren't features waiting in a backlog. They're choices.

Why a separate title field

A small but consequential decision: every entry has a dedicated title field, separate from the body.

In a single-blob editor, the first line is the title by convention. That convention has costs:

A separate title field decouples the two. The title is the label; the body is the writing. The title can be empty. It can also be a date, a one-word emotion, or "untitled" — and the entry still looks correct in the sidebar.

Functionally, it also lets us do clean things: titles render in the calendar and sidebar, bodies don't. The visual hierarchy stays intact whether you title or not.

The editor's stack

For the curious: Jottii's web editor is built on CodeMirror 6 with a Markdown grammar. The mobile app uses TipTap. The two converge on a small, shared subset: headings, bold/italic, lists, blockquote, inline code, code block, links. Underneath, every entry is plain Markdown — the canonical form, exportable to any other tool.

We considered going further into rich-text territory (tables, columns, embeds) and consciously didn't. Markdown is the lingua franca of private writing tools. It's portable, future-proof, and won't be deprecated by an editor framework rev.

The distraction-free principle, applied beyond the editor

The editor is the visible expression of a broader rule we apply across the app:

The last one is the most important. Streak counters and gamification are great for some habits and corrosive for journaling. A page that nags you to write produces a page you write for the page. A page that quietly waits produces a page you write for yourself.

What this changes about the practice

Reports we get from users (and our own experience):

Where the editor will go

A few directions we're working on, all of which keep the silent-page principle:

We will not be adding: AI features that read your text, color highlights, embedded media uploads. The page stays quiet.

The deeper reason

Writing for yourself works best when the surface respects you. Most editors are built to demonstrate features to a buyer. Journals don't have buyers. They have writers, who needed to start ten seconds ago, who need the friction to be lower than the resistance to writing.

A distraction-free editor isn't an aesthetic. It's a permission: this is your page, nothing here is asking for your attention, you can write or not. Most days, you do.

Open Jottii and write the first thing you notice today. The page is quiet enough.