aws-amplify / aws-amplify/amplify-ui
Provide clear (best practice) examples. Not antipatterns.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 347
- Avg merge
- 18h 29m
- Merged PRs (30d)
- 9
Description
### On which framework/platform would you like to see this feature implemented?
React
### Which UI component is this feature-request for?
Other
### Please describe your feature-request in detail.
Theming documentation is a total mess.
Please provide simple and pure examples first, before starting mixing styled components and custom attributes.
Many developers just copy as is, without thinking.
No need to overcomplicate examples at the very beginning.
### Please describe a solution you'd like.
_No response_
### We love contributors! Is this something you'd be interested in working on?
- [x] 👋 I may be able to implement this feature request.
- [ ] ⚠️ This feature might incur a breaking change.
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 React theming documentation referenced in the issue and identify where examples currently introduce styled components or custom attributes. Done means the documentation leads with simple, pure best-practice examples before presenting those more advanced patterns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100