microsoft / microsoft/react-native-windows-samples
Some docs might be better served as "evergreen" static pages
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 544
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
We have some docs pages that don't make sense to be versioned according to RNW version. It might make sense to migrate these to static pages, so they're both easier to maintain and make sure users are given the most correct information.
Potential pages:
Contributor guide
No contributing guide indexed for this repository
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 supported-community-modules and win10-compat pages linked in the issue, then inspect how the repository currently handles versioned documentation. Determine which pages should become evergreen static pages and verify that the migrated pages present current information without RNW versioning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100