Text Editing

Text editing is the broader field underneath note-taking apps, documentation tools, IDEs, knowledge bases, and writing software. This route is meant to be useful when you need to compare editor families, understand the tradeoffs between source visibility and interface convenience, or place a modern tool inside a longer lineage.

Obsidian is one current product context that sharpens those questions, but it is not the topic by itself. The topic is the larger history of editing surfaces, file formats, note systems, and the changing boundary between raw text and projected structure.

@current_context

Current Application Context

This route should work as a reference surface, not just a mood board: define the category, point to useful starting documents, and clarify which adjacent routes answer which questions.

obsidian

Current product example

Obsidian’s current public position is unusually clear: durable local files, privacy, customization, and independence. Their help docs also describe the app plainly as both a Markdown editor and a knowledge-base app. That combination makes it useful as one current benchmark for local-first writing tools, especially the narrower category of Markdown knowledge bases.

bridge

Questions this route should answer

What counts as an editor family? Which features belong to files versus application layers? When does an editor become a knowledge base, an IDE, or a publishing surface? Those are the comparisons this route should make easier.

scope

Boundary of the page

This page is the parent overview. The narrower cases live on the knowledge-base, note-taking-history, and editor-history routes so the distinctions stay explicit rather than collapsing into one bucket.

~"route_map"

Begin Here

^kb

Knowledge bases

Linked-note systems, vault-like structures, research archives, and the broader category where accumulated notes become a navigable memory surface.

^notes

Note-taking history

Commonplace books, slip-boxes, linked notes, and why private capture systems keep reappearing whenever writers need durable intermediate structure.

@editors

Editor history

Line editors, screen editors, visual editors, and the recurring tradeoff between raw source visibility and approachable interfaces.

>platform

Browser + TypeScript

The runtime and platform side of the same question: if text becomes structured and interactive, what contracts do the browser and editor surface need?

~"reference_points"

Reference points

ed