[GUI] Make the header brand link to the project
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- css, html
- Domain
- frontend
Research direction
Start in serve/web/index.html and locate the header brand span shown in the issue. Check the existing styles in components.css, including the global focus-visible rule. Update the brand link and its styles as proposed, then verify the link opens the repository in a new tab and preserves the header’s appearance and keyboard focus ring.
Written by the indexing model from the issue text.
Description
[GUI] Make the header brand link to the project
Area: GUI (web chat) — serve/web/index.html
Versions: app 0.2.12 / control 0.1.58
Problem
The top-left brand is plain text:
<span class="st-header__brand">Strata</span>
Clicking it does nothing, although it looks like a logo/home link.
Proposal
<a class="st-header__brand" href="https://github.com/Niko1221/Strata/tree/main"
target="_blank" rel="noopener noreferrer" title="Strata on GitHub">Strata</a>
plus a small style so it keeps the current look:
a.st-header__brand { color: inherit; text-decoration: none; }
a.st-header__brand:hover { color: var(--st-accent-text); }
The focus ring is already the project's own: components.css declares
:focus-visible { outline: 2px solid var(--st-focus); outline-offset: 2px } globally, so the brand needs
no rule of its own.
One line in the template, two rules in CSS; no behaviour elsewhere changes.
Test plan
- click the brand -> the repository opens in a new tab, the page itself stays;
- hover does not underline and does not change the header height; keyboard focus draws the usual
ring; - the rest of the header (tabs, buttons) is untouched.
- Dominant language
- C++
- Stars
- 11.6k
- Forks
- 1k
- PR merge metrics
- No merged PRs in 30d
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
- 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 Niko1221/Strata
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Niko1221/Strata#5560 · 2 comments ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Niko1221/Strata#5553 · 2 comments ·
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 4 days
-
[GUI] Monitor: on a Mac "GPU load" is time busy, not compute in use; VRAM HIT RATE is always a dashOpen
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 4 days
Similar issues
-
NVIDIA windows
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
kind/bug priority/medium qa_automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yugabyte/yugabyte-db#37324 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
CharlotteCross1998/awesome-game-decompilations#61 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
godotengine/godot#125240 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day