Gap Register
G-015Public

Content authoring / editor interface

Tier 1 — Existential, blocks launch
Status
Open — not started
Owner
Creator
Why now
Fandom's largest unforced UX error was wikitext. OLN explicitly rejects wikitext. The replacement needs design.
Depends on
G-005
Blocks
Launch, Meaningful contributor onboarding, Memory Alpha migration

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.

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

Related

  • Entry 009 — Memory Alpha Migration
  • Entry 010 — LoreLines as Third Contribution Surface
  • G-005 — AI policy
  • G-030 — Memory Alpha migration architecture

Your read on this

Anonymous reactions are accepted; signing in lets you change yours.