feat(pwa): add a theme-color meta tag to analytics.flisk.si so mobile browser chrome matches the page
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- html, javascript
- Domain
- frontend
Research direction
Reproduce with curl -s https://analytics.flisk.si/ | grep -c theme-color (prints 0), then find the template that renders the home page head — it already sets viewport, title and description next to where the tag belongs. Add <meta name="theme-color"> with the page background hex plus a second tag carrying media="(prefers-color-scheme: dark)", and add the two response-body tests from the plan. Done when both new tests pass and the existing suite is still green.
Written by the indexing model from the issue text.
Description
Problem
https://analytics.flisk.si/ has no <meta name="theme-color"> tag. chat, inference, tools and readme set one. On Android Chrome and iOS Safari the address bar and tab strip stay the default grey or white and clash with the page, and an installed home-screen shortcut gets no brand colour.
Reproduce: curl -s https://analytics.flisk.si/ | grep -c theme-color prints 0.
Root Cause Analysis
The page template sets viewport, title and description but not the theme colour, so browsers fall back to their defaults. It is one line of head markup.
TDD Fix Plan
- RED: Add a test that GET / contains
<meta name="theme-color"with a valid hex colour.
GREEN: Add the tag to the page head with the page background colour. - RED: Add a test that a dark scheme variant exists via
media="(prefers-color-scheme: dark)".
GREEN: Add a second tag for dark mode.
REFACTOR: Share the head fragment with the other flisk.si pages.
Acceptance Criteria
- The home page has a theme-color meta tag
- The colour matches the page background in light and dark
- All new tests pass
- Existing tests still pass
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No 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 flisk-sh/analytics
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
All issues in flisk-sh/analytics
Similar issues
-
chore cloudflare-workers consistency d1 difficulty: easy documentation dx enhancement good first issue help wanted hygiene javascript maintenance priority: P3 seo
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MattiaPARRINELLO/backstage#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·