testing-library / testing-library/testing-library-docs
Discussion: Reduce flavored pages (React, Vue, Cypress,…) to its bare minimum?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 479
- Forks
- 740
- PR merge metrics
- No merged PRs in 30d
Description
I wanted to know your opinion on reducing each flavor section, so that we have some "big" pages about queries, common use cases, and so on, and then other React/Vue/Cypress/Svelte pages with the specifics for each framework.
All implementations are quite similar, so we could have a heading for each big difference with an example.
I'm not 100% sure this is the best approach, so feel free to suggest any other idea :)
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
Review the existing React, Vue, Cypress, and Svelte flavor sections alongside the pages covering queries and common use cases. Compare repeated material and framework-specific differences, then seek agreement on a documentation structure before making changes; done means the scope and revised page organization are decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, react
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100