Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Extract hardcoded UI strings in the landing page sections into lib/copy

Closed Beginner friendly
#950 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start in components/landing/sections.tsx and list every user-visible string: labels, aria-labels, toasts and placeholders. Copy the structure of lib/copy/dashboard.ts and lib/copy/streams.ts into a new lib/copy/landing.ts, then import from it in the component. Done when no string literals remain in the component, the wording is unchanged, and the existing tests pass with any needed import updates.

Written by the indexing model from the issue text.

Description

frontend good first issue

Description

Most pages now keep user-facing text in lib/copy/* modules, but the landing page sections still hardcodes its labels, aria-labels, toasts and placeholders inline.

Location

components/landing/sections.tsx. Existing examples: lib/copy/dashboard.ts, lib/copy/streams.ts.

Task

Move every user-visible string into a new lib/copy/landing.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
10h 11m
Merged PRs (30d)
60

Getting set up

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 FlowwStar/FlowStar

All issues in FlowwStar/FlowStar

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.