How Fact entry, Commons proposals, LoreLines, and Home content are authored. AI-assisted by default, with structured-data entry that doesn't feel like a tax form.
Why this matters
Fandom’s largest unforced UX error was wikitext as the contribution surface. OLN explicitly rejects wikitext (see Entry 009). OLN needs an explicit design stance on how Fact entry, Commons proposals, LoreLines, and Home content are authored.
In 2026 the right answer is AI-assisted by default, with structured-data entry that doesn’t feel like a tax form.
Decided (Entry 037)
The editor architecture is settled: a TipTap / ProseMirror block editor you edit in place (not a WYSIWYG box, never wikitext), with ProseMirror JSON as the source of truth and a safe MDX subset used only for export and diffing. Pages render through a component allowlist so user content cannot execute; launch is presence + a soft single-writer lock, not real-time co-editing; and plugins/themes are marketplaces over a no-user-code substrate (a plugin configures a reviewed component; a theme is validated tokens). What remains below is the build and the authoring affordances.
Open
- AI-assisted Fact extraction from prose drafts (with confidence scoring)
- Form-vs-prose split for Commons proposals — when each
- LoreLines authoring affordances (the low-friction surface needs to feel low-friction)
- Home authoring tooling — does OLN ship its own editor or integrate Substack-style external?
- Mobile-first authoring for LoreLines specifically
- Offline drafts and revision history during authoring