Core workflow surface

What already works well today:

• Headings, drawers, properties, planning lines, TODO keywords, links, blocks, tables, and timestamps

• Agenda views across many files

• TODO / planning edits from CLI and VS Code

• Capture, archive, and refile workflows

• Canonical formatting

• HTML export and multi-file publishing

• Roam-style IDs, backlinks, dailies, and node creation

• Org-crypt subtree encryption/decryption workflows

• LSP-backed editor features

Planning + agenda

Org2's planning workflow is already pretty serious.

Highlights:

• Scheduled + deadline items across many files

• Rich date-window controls

• Filter dimensions for status, kind, date/time, tags, IDs, properties, priority, effort, file, headline text, and more

• Sort and group controls for daily planning views

• Practical handling of real-world TODO vocabularies (for example WAIT/HOLD/PAUSED normalize into in-progress-style buckets)

This is not just “show me tasks due today.” It is shaping into a real backend for agenda tooling.

Knowledge management / roam workflows

Org2 has first-class support for linked-note workflows:

• Stable IDs

• Backlinks

• Wiki links and id: links

• Node creation

• Dailies navigation

• Link insertion helpers

• Workspace graph operations via Roam DB sync

This matters because Org-style notes get dramatically better once links, references, and dailies stop feeling bolted on.

VS Code experience

VS Code is currently the most complete Org2 editor story.

That includes:

• Syntax highlighting and folding

• Agenda UI

• TODO / planning commands

• Capture / archive / refile commands

• Formatter commands with preview/apply flows

• HTML export commands

• Roam commands for IDs/backlinks/dailies

• Power-keymap shortcuts for fast workflows

If you want to use Org2 today instead of just admire the idea, this is the path.

LSP capabilities

Org2's LSP surface is already broader than the docs site previously implied.

Current highlights include:

• Definitions / declarations / references for file and ID links

• Hover, completion, signature help, and highlights

• Rename + linked editing for IDs and file-link targets

• Workspace file-rename support for updating Org file links

• Formatting, range formatting, and on-type table-aware formatting

• Semantic tokens, inlay hints, code lens, document colors

• Call hierarchy for Org ID/file links

That's real editor infrastructure, not a toy server.

Publishing

Publishing is already a first-class workflow, not an afterthought.

• Single-file HTML export

• Recursive workspace export

• Project-level publish definitions via org2.json

• TOC / heading-numbering / stylesheet / file-link-rewrite support

• This docs site is generated by Org2 itself

Positioning

Org2 is trying to preserve what is powerful about Org while dropping the assumption that the only serious home for it is Emacs.

That is the whole bet:

• keep the plain-text power,

• make the backend portable,

• meet users where they already work.