Team branding: name and colour palette

Open
  • Is something wrong?
#25 1 comment 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
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
full-stack

Research direction

Read the proposed team-branding spec and tasks in openspec/changes/team-branding, then review the team-setup proposal in issue #24 for the required setup flow. The work spans configuration, setup views, served views, charts, static exports, and colour validation; done means those surfaces use the selected team name and palette, with invalid configuration falling back as specified.

Written by the indexing model from the issue text.

Description

roadmap

Size: S–M · Depends on: IgniteRobotics/flashpoint#24 · OpenSpec: team-branding (merged, on main)

Status

Status: merged 2026-11-01 in #42. 16/17 tasks done. Open: 5.3 [HUMAN], look at the presets on the pit laptop and a projector (tracked in #13). Changes made while applying: the warning colour must now be at least 35° of hue from the primary (was 40°; today's amber and its warning are 38.7° apart), and darker primaries get their darker shades adjusted until they read at 4.5:1. Docs: user guide "Team name and colours" and the new team setup guide.

Scope

Let each team show its own name and colours, set up with the rest of its configuration.

  • Team name: header and page title show the display name and number ("Ignite Robotics · 6829"); plain "telemetry" when unset. Replaces the hard-coded "telemetry // ignite robotics".
  • Palette: presets (amber default = today's look exactly, green, blue, red, white) or custom primary + optional background and warning colours; every shade derived in OKLCH.
  • Validation: text ≥ 4.5:1 on every surface, boundary lines ≥ 3:1, warning colour distinct from the primary. Refusals name the failing rule and suggest the nearest passing colour.
  • Everywhere: served views, charts (FP.tokens()), and static exports; a broken theme.toml falls back to default and shows up in setup checks.
  • Setup: flashpoint init --team-name --palette, and an Appearance section in the Setup view with a live preview.
  • Code: colour tokens renamed from amber to roles (--accent*, --warn); 19 hard-coded amber rgba values become tokens.
  • Non-goals: logos, fonts, layout, light mode, per-user themes.
Dominant language
Python
Stars
0
Forks
1
Avg merge
18h 37m
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 IgniteRobotics/flashpoint

All issues in IgniteRobotics/flashpoint

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.