Extract hardcoded UI strings in Navbar into lib/copy
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- nextjs, typescript
- Domain
- frontend
Research direction
Start with components/layout/navbar.tsx and list every visible string: labels, aria-labels, toasts and placeholders. Read lib/copy/dashboard.ts and lib/copy/streams.ts to see the export shape, then create lib/copy/navigation.ts with the same wording and import it in the component. Done when the component has no string literals left, the UI renders unchanged, and the existing tests pass, updating their imports if they reference these strings.
Written by the indexing model from the issue text.
Description
Description
Most pages now keep user-facing text in lib/copy/* modules, but Navbar still hardcodes its labels, aria-labels, toasts and placeholders inline.
Location
components/layout/navbar.tsx. Existing examples: lib/copy/dashboard.ts, lib/copy/streams.ts.
Task
Move every user-visible string into a new lib/copy/navigation.ts and import it in the component. Keep wording identical.
Acceptance criteria
- No user-visible string literals remain in the component
- Existing tests still pass (update string imports in tests if needed)
- UI is unchanged
Good for contributors because
Mechanical refactor following an established pattern.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 144
- Avg merge
- 7h 11m
- Merged PRs (30d)
- 37
Getting set up
- No 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 FlowwStar/FlowStar
-
Remove unused formatFee() from fee-utils.tsPossibly taken @jdjioe5-cpu claimed this 12 days ago. Openfrontend good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
FlowwStar/FlowStar#1039 · 4 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Name the 15% fee buffer constant in fee-utils.tsPossibly taken @jdjioe5-cpu claimed this 12 days ago. Openfrontend good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Add a timeout to the XLM price fetch in use-token-pricePossibly taken @jdjioe5-cpu claimed this 12 days ago. Openfrontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
FlowwStar/FlowStar#1037 · 1 comment ·
Maintainers usually reply within 1 day
-
Add a timeout to the Friendbot request in TestnetFaucetBannerPossibly taken @jdjioe5-cpu claimed this 12 days ago. Openfrontend good first issue ux
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FlowwStar/FlowStar#1036 · 1 comment ·
Maintainers usually reply within 1 day
-
Add a request timeout to Horizon fetches in lib/stellar.tsPossibly taken @jdjioe5-cpu claimed this 12 days ago. Openfrontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FlowwStar/FlowStar#1035 · 1 comment ·
Maintainers usually reply within 1 day
All issues in FlowwStar/FlowStar
Similar issues
-
Chip source filter and denial markers miss Storage rows when a Storage activity source is pickedOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
omdsh-dev/DSH-better-sidebar#1141 ·
Maintainers usually reply within 2 days
-
desktop linux photos
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Cleanup SetupPossibly taken @AlexanderKaran claimed this today. Opendocumentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
e18e/framework-tracker#769 ·
Maintainers usually reply within 1 day
-
bug v2
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modelcontextprotocol/servers#5483 ·
Maintainers usually reply within 1 day