Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Spokój: calm, consistent polish of Prostota (founder direction 2026-10-15)

Open
  • Is something wrong?
#500 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 15, 2026.

  • #529 by @PelikanFix16 — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
design, frontend

Research direction

This is an umbrella tracker, not a task to start on. Read the rules and per-screen layouts in docs/design/spokoj/README.md at the linked commit, then pick one specific child issue such as #501 or #502 and work from that. Done means that child's criteria pass at 390×844 and 1440×900 in light and dark, with no control moving between states.

Written by the indexing model from the issue text.

Description

enhancement

Founder direction (Hubert, 2026-10-15). I reviewed the running application on phone, tablet, computer and large screens and approved the design board “Spokój”. Flux must not overwhelm people: everything consistent and understandable, buttons never larger than their text, at most two content columns, and a control never changes place when a view or state changes. This refines F-026 Prostota (#336); it does not redesign it. Where Spokój and an older Prostota drawing differ, Spokój wins.

  • Rules, the --own token, layout per screen and renders of every board: docs/design/spokoj — PR #499 records it in docs/design/final and F-026.
  • Interactive board with Polish notes: Spokój canvas.
  • Evidence: measured on main 86c43c75 (demo data, dark, Chromium in Docker) at 390, 820, 1440, 1920 and 2560 px; control positions recorded per accessible name in 24 states per viewport.
Main

Rules

  1. Text matters more than buttons (32 px buttons, 44 px on touch, 13–14 px labels; one primary action per surface).
  2. At most two content columns; a further object replaces the panel's content.
  3. One header row, with or without a panel.
  4. Empty sections disappear.
  5. One pattern for one thing: one bubble, one panel shell, one composer.
  6. Selection is a soft fill; no white rings or bars.
  7. A control never changes place.

Work

New issues:

  • #501 Phone: message with a task card collapses (high)
  • #502 Hand-off: same dialog from the task panel, empty state without agents
  • #503 One message bubble (--own)
  • #504 One composer
  • #505 Layout: one-row header, two columns, widths per screen
  • #506 Controls keep their place (sidebar, header, Tasks toolbar, labels)
  • #507 Phone project header
  • #508 Home and Sketchbook
  • #509 Map: infinite canvas
  • #510 Map list as a tree
  • #511 Wiki history, outline, page toolbar
  • #512 Project details
  • #513 Settings
  • #514 Search results

Existing issues amended by founder-direction comments with drawings:

  • #488 — calm task panel (P10 layout, phone status menu, no single-page pagination) and the thread replacing the panel's content
  • #345 — C opens the Create window; ⌘K empty state with recents and actions
  • #437 — empty Inbox without zero counters

Already covered and still open: #436 (times, thread numbers), #437 (desktop Inbox alignment, mono meta), #438-6 (search chips on the phone), #347, #354.

Order

  1. #501, #502, #505 (header), #508 (Home bar)
  2. #506, #507, #503, #504, #488 thread-in-panel
  3. #488 task panel, #512, #345
  4. #509, #510
  5. #511, #513, #514

Done when

Every child and amended issue meets its criteria in the integrated application at 390 × 844, 820 × 1180, 1440 × 900 and 2560 × 1440 in light and dark, Chromium and WebKit, and a fresh measurement shows no control moving between the states listed in the audit board.

Dominant language
TypeScript
Stars
3
Forks
0
Avg merge
19h 9m
Merged PRs (30d)
334

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 ColdPhase/flux

All issues in ColdPhase/flux

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.