Success messages patterns
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 79
- Forks
- 52
- Avg merge
- 18h 58m
- Merged PRs (30d)
- 4
Description
## Summary
Improvements to success messages patterns.
## 💬 Description
Additional examples and improvements to the success messages patterns detailed on the design system website.
## 💰 Use value
Describe why this is important and how it will help users (either developers, designers or the end-users). Think about how it makes people's lives easier, more accessible or quicker to build stuff.
## Additional info
Additional and/or improved examples of success messages will allow developers to gain a better understanding of what their own implementations should achieve.
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 on the design system website by locating the existing success message patterns guidance and reviewing its current examples. Done means the guidance includes additional or improved examples that help developers understand the intended success-message implementations; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100