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

Wiki as drawn: page list, page with who edited, references and an outline; phone reading at 16px

Open
  • Is something wrong?
#354 3 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 8, 2026.

  • #374 by @PelikanFix16 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
react, typescript
Domain
accessibility, documentation, frontend

Research direction

Start with docs/Wiki.tsx, docs/WikiParts.tsx, docs/DocViews.tsx, and docs/docs.css under app/apps/web/src; review the linked design guide and confirm the starting paths with the owner. Read the existing UI tests test_wiki_panes.py, test_docs.py, and test_doc_references.py, then run ./scripts/check_ui.sh. Done means the acceptance criteria and desktop/mobile light/dark renders are met, with keyboard and touch checks; #338 and #339 are dependencies.

Written by the indexing model from the issue text.

Description

agent:ready enhancement

Part of #336 (F-026, founder direction 2026-10-07). Design guide: docs/design/final (§7 screens · §6 files references and photos; until #337 merges, read the pinned copy). Interactive boards (light/dark toggle, notes): design canvas, page "Prostota".

Outcome

A project's Wiki reads like the drawn page on the computer and the phone, with its existing versions, sharing and drafts.

Final design

desktop-wiki phone-wiki

Acceptance criteria

  • AC-1. On the computer the Wiki is two panes as drawn: the page list ("Pages") beside the page. The page shows its title, an "Edited by · " line with the editors' faces (agents as Kreska with "for ", #339), the text at a readable measure, and an "On this page" outline on wide panes. Edit is the one primary action.
  • AC-2. References inside a page follow the final design (#348): an accepted decision is a card ("Decision accepted", its title, date and who), and tasks appear as #number with their state glyph and word (#338) or pill.
  • AC-3. On the phone the title reads "Wiki · N pages", the pages are a horizontal row of chips, the reading text is 16px (S17) and Edit stays reachable at the bottom. There are no other toolbars.
  • AC-4. Existing behaviour stays: versions and history, share, download, focus mode, drafts and conflicts, and access per audience.
  • AC-5. 1440 × 900 and 390 × 844 match the renders in light and dark; the page list and outline are keyboard reachable.

What changes in the code today

From a read of main at 3c553b79; the owner confirms before starting. Paths are under app/apps/web/src, public/ is app/apps/web/public, root scripts/ and tests/ are the repository's, and UI tests are in app/tests/ui.

Change

  • docs/Wiki.tsx and docs/WikiParts.tsx (page index with search, the wiki bar with focus, history, share and download as icon buttons) → the drawn page list and the page header with the editors line; docs/DocViews.tsx reading view.
  • docs/docs.css (212px index, 820px column, .wiki-bar) → Soft volume layout; prose measure as in #338.
  • Phone: the stacked index and page strip (@container wiki (max-width: 499px)) → the drawn chip row and 16px reading text.

New

  • The "On this page" outline from the page's headings on wide panes.
  • Decision cards and task references in the page (shared with #348).

Tests to rewrite

  • test_wiki_panes.py, test_docs.py and test_doc_references.py where they assert the old layout.

Depends on

#338, #339 (tokens and shared components first; independent parts can start earlier).

How to test

./scripts/check_ui.sh            # browser suite; add the new or changed tests
./scripts/check_application.sh   # when API or data paths change
python3 scripts/check_agent_setup.py && git diff --check

Compare with the renders above at 1440 × 900 and 390 × 844 CSS px, in light and dark, on ./flux demo data, then get an independent visual review with a neutral brief (guide §9). Screenshots do not prove interaction or accessibility, so also test keyboard, touch (Chromium and WebKit emulation), reduced motion and contrast in the running app.

Owner: whoever claims it (assign yourself and comment once). Evaluator: the other agent. The design is a founder direction: implement it as drawn; raise a conflict with a functional contract on #336 instead of changing the design.

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

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.