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

New project from a template in one step, views that appear when needed, and sign-in

Open
  • Is something wrong?
#351 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@PelikanFix16 is already working on this.

Since Oct 8, 2026.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
react, typescript
Domain
authentication, frontend

Research direction

Start with the design guide’s §5 and the renders, then read app/ProjectSetup.tsx, auth/pages.tsx, and test_project_surface.py; check the sign-in coordination with #315 and the accepted requirements before changing that surface. Update project setup, progressive views, and the applicable sign-in mode, adding or revising UI tests; run ./scripts/check_ui.sh and compare both screen sizes, themes, interactions, and accessibility against the criteria.

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 (§5 behaviour; until #337 merges, read the pinned copy). Interactive boards (light/dark toggle, notes): design canvas, page "Prostota".

Outcome

Starting is light: one step to a project, and only the views a project needs.

Final design

desktop-newproject phone-newproject desktop-signin phone-signin

Acceptance criteria

  • AC-1. A new project takes one step: a name and a template. People and agents are invited later (S20).
  • AC-2. Map, Wiki and Agents appear in the view menu or header the first time they are needed, from a template or from use, and can be added from More (S21).
  • AC-3. Sign-in and account pages match the renders, with the plain Kreska logo tile and no decoration outside it.
  • AC-4. Existing projects keep every view they already use.

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

  • app/ProjectSetup.tsx (name only, then "Who can see this") → name + template in one step; invite later.
  • auth/pages.tsx → Kreska logo tile. The existing #240 baseline exposes password and configured SSO. The later accepted founder amendment, #315 and PR #361 require exclusive ordinary modes: password-only without active SSO, or the installation's sole IdP with active SSO. Provider outage/discovery failure must not enable password fallback. Existing-account migration is explicit before cutover; no recent-login challenge. F-024 S1/#310 adds the IdP path to MCP /login; coordinate the final sign-in surface with #315 rather than implementing mixed ordinary login. The render also shows an email sign-in link and a passkey, which Flux does not have today. Whether they become part of the product is a founder question, asked on #336 on 2026-10-07; until it is answered, build the applicable accepted password-only or SSO-only mode in the drawn style.

New

  • Project templates and progressive views (Map, Wiki, Agents appear when needed, addable from More).

Tests to rewrite

  • test_project_surface.py. There is no test_auth*.py, and no test asserts the sign-in brand today, so add one (the OIDC e2e tests app/tests/app/e2e/oidc*.e2e.ts also use the sign-in page).

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.

Updated 2026-10-07: sign-in methods and test paths corrected against main; cross-links to #240 and #310 added.

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.