paper
Markdown editor
Star 0
Fork 0
Watch
paper plan.md
2.4 kB · 35 lines
Markdown
at main

Paper roadmap #

Paper's goal is a focused, keyboard-friendly WYSIWYG Markdown editor that remains comfortable with large documents and unrestricted local file navigation.

This roadmap describes capability goals, not an implementation sequence or a record of completed work. See the README for current usage and limitations, and architecture for design boundaries.

Reliable editing #

Make everyday editing predictable across keyboard input, clipboard operations, Unicode, composition, and undo/redo. Validate behavior with assistive technology and across supported operating systems.

Success means users can edit and navigate without losing content, selection, or their place in the document.

  • TODO: Complete the inline boundary policy in the core guide: add explicit formatting toggles and pending formatting, handle adjacent or nested delimiters consistently after partial replacements, and validate native navigation, IME, clipboard operations, and undo/redo across supported platforms.

Safe file lifecycle #

Support saving, saving under another name, recovery, and external-change handling. Protect unsaved work and make conflicts and failures actionable.

Keep folder browsing lightweight: the current folder helps navigation but never confines which documents can be opened.

Markdown fidelity #

Expand block and inline formatting while preserving source meaning. Define supported syntax and make unsupported constructs explicit rather than silently rewriting or discarding them.

Success requires reliable import/edit/export round trips, not just a visually convincing document.

  • TODO: Revisit the flat block model before supporting nested containers with multiple child blocks. Define behavior for lists containing paragraphs, quotes, or code blocks, and for selections and replacements across container boundaries, before choosing a tree representation.

Large-document editing #

Establish document-size, responsiveness, and memory budgets using representative Markdown and Unicode content. Keep full WYSIWYG editing available while maintaining stable scrolling, selection, undo, and accessible navigation.

Cross-platform confidence #

Verify the complete reading, editing, and file lifecycle on macOS, Windows, and Linux. Preserve a consistent application experience while respecting platform input and window behavior.