Componetize headers and subtitles within settings pages
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Problem to solve
While the product evolves more patterns strengthen the need to componetize parts of the product.
Cross-posting from https://github.com/gitpod-io/gitpod/pull/6390#issuecomment-952131293:
FYI, we've decided to embrace utility classes for the product dashboard and have been trying to avoid using arbitrary class names when possible, preferring duplication over abstraction and extracting pieces into components when needed. 🌬️
Proposal
Following the comment from https://github.com/gitpod-io/gitpod/pull/6671#issuecomment-971587770, one of these patterns that seems to be around for a while is the headers and subtitles within settings pages.
Contributor 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.
Research direction
Start by reviewing the settings pages and the two referenced pull requests/comments to identify the repeated header and subtitle patterns. Determine the intended component boundary and which settings pages are in scope; done means the repeated patterns are consistently componentized across the agreed pages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100