Add an optional Superhuman-style layout

Open
#799 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
frontend, web-dev

Research direction

The issue links to the frontend implementation in fork PR #29, which is the best starting point for understanding the proposed layout and its tests. Review how the PR adds the optional setting, toolbar choice, keyboard navigation, and command palette while reusing existing MailFlow actions. Done means the layout is opt-in, Comfortable remains the default, mobile layout and theme choice stay separate, and the frontend checks pass; related requests #596 and #737 provide context.

Written by the indexing model from the issue text.

Description

The situation

I built a Superhuman-style layout for people who want to triage mail quickly from the keyboard. I'd like to offer it as an opt-in option in Settings → Appearance → Layout and in the toolbar's layout menu. Comfortable stays the default, the mobile layout is unchanged, and the theme is still a separate choice.

  • A narrow navigation rail opens an account and folder drawer. Split-inbox tabs sit above dense, single-line message rows.
  • Messages open full width in place of the list. j / k move through messages, Enter opens one, and Esc returns to the list.
  • ⌘K opens a contextual command palette. Archive, snooze, reply, and Undo use MailFlow's existing actions.

Compact and List first are the closest options today, but neither gives me the rail, drawer, and keyboard-first reader together.

Demo

https://github.com/user-attachments/assets/09598309-f981-4d19-97fe-d14e9eb94775

The 43-second walkthrough uses fictional mail. It shows switching layouts, navigating the inbox and reader from the keyboard, opening the command palette, and changing the theme separately.

Implementation

Frontend-only implementation in my fork (PR #29). It adds no backend changes, migrations, or dependencies. Frontend tests, lint, and the production build passed locally; the PR has the test details.

Related requests

  • #596 asked for a full-width list where a message opens on its own. List first covers that, and this layout builds on it.
  • #737 asks for a narrow account rail next to the folder tree. This layout's rail and folder drawer cover part of that request.
Dominant language
JavaScript
Stars
518
Forks
50
Avg merge
4d 45m
Merged PRs (30d)
43

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from maathimself/mailflow

All issues in maathimself/mailflow

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.