[Lens] Styling pass: stronger section headings + per-product branding consistent with tokenjam.dev
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
First request the branding reference and source assets/spec mentioned in the issue. Then locate the dashboard UI entry point and review its existing headings and product treatments; keep any icons inline or vendored to preserve offline behavior. Done means the six products have branding consistent with tokenjam.dev, section headings have stronger hierarchy, and test_ui_offline.py passes.
Written by the indexing model from the issue text.
Description
The Lens UI is functional but visually utilitarian — section headings are plain all-caps monospace ("RECOVERABLE WASTE", "HEALTH AT A GLANCE", "EXPLORE"), and the analyzers/Lens have distinct product identities on the website that the dashboard doesn't reflect.
Scope
- Stronger section headings — more visual hierarchy/weight than the current flat monospace labels.
- Per-product branding — the five analyzers (Downsize / Cache / Script / Trim / Reuse) and Lens have icons/identity on tokenjam.dev; bring that consistent branding (icons, accent treatment) into the UI so the dashboard feels like the website.
Needs
A branding reference from the website — colors, icons, typography per product — so the in-UI treatment matches tokenjam.dev rather than diverging. (@anilmurty to point at the source assets/spec.)
Constraints
UI-only, offline single-file SPA — any icons must be inlined/vendored (no external fetch, per the offline rule). No new render-time external URLs. Keep test_ui_offline.py green. Larger/visual — likely a 0.5.2 item, not a 0.5.1 blocker.
- Dominant language
- Python
- Stars
- 122
- Forks
- 35
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Metabuilder-Labs/tokenjam
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#786 ·
Maintainers usually reply within 1 day
-
enhancement good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Metabuilder-Labs/tokenjam#759 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Metabuilder-Labs/tokenjam#728 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Metabuilder-Labs/tokenjam#591 ·
Maintainers usually reply within 1 day
-
bug good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Metabuilder-Labs/tokenjam#559 ·
Maintainers usually reply within 1 day
All issues in Metabuilder-Labs/tokenjam
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CLIMADA-project/climada_python#1337 ·
Maintainers usually reply within 3 days
-
tail without reverseOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
8go/matrix-commander#233 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation enhancement priority:high size:M
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Validate non-divisible effective batch sizes in the Unsloth LoRA backendPossibly taken @debesh-biswas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100