Skip to content

Bake-off 2A: Reproduce the target in Floem #51

Description

@danielmrdev

Parent

Part of #49.

What to build

Reproduce the approved Editorial Paper target in a disposable Floem prototype while preserving the current application and tested Rust domain. A writer can interact with the representative Writing surface, Document selector, Settings, and integrated titlebar closely enough to judge visual fidelity, interaction quality, and development cost.

Acceptance criteria

  • The prototype matches the approved content, dimensions, tokens, Themes, and states rather than merely restyling the current screenshots.
  • Paper and Ink, normal and narrow sizes, Document selector search/results/empty states, and General/Appearance Settings states are directly demoable.
  • The integrated themed titlebar supports drag, double-click maximize/restore, minimize, maximize, close, focus, inactive, scaled, keyboard, and accessible-name states.
  • Selection, clipboard, undo/redo, IME, soft wrap, scroll, expected shortcuts, App scale, and 1/10 MiB Documents remain directly testable through the real Floem editor.
  • Simulated data is isolated from production Documents, Files, autosave, Preferences, and Typeface delivery.
  • Implementation and debugging stop at the two-day candidate budget.
  • Time, framework-specific code, dependencies, local patches, workarounds, edit-preview cycle, and known platform limitations are recorded as evidence.
  • The working application remains intact and no prototype change is presented as production-ready.

Blocked by

Workspace

  • Mode: parallel lane
  • Branch: feat/49-ui-stack-bakeoff-51
  • Worktree: /home/daniel/Projects/lettera/.worktrees/feat-49-ui-stack-bakeoff-51
  • Integrates into: feat/49-ui-stack-bakeoff
  • Remote policy: local only — never push
  • Completion: when unblocked, create the lane from the latest integration commit; validate it, merge it locally into integration with approval, validate integration, remove the lane worktree, and delete the local lane branch

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified and ready for an AFK agent

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions