microsoft / microsoft/react-native-windows-samples
Migrate to Docusaurus v2
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 544
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
@chrisglein we don't control the order of inclusion as that's done by docusaurus.
If/we move to docusaurus v2, a lot of this can go away since we can just embed react components instead of dealing with css styling
Originally posted by @asklar in https://github.com/microsoft/react-native-windows-samples/pull/251#discussion_r492475514
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 Docusaurus v2 migration discussion in PR #251, especially the notes about inclusion order, CSS styling, and embedding React components. Define the documentation migration scope and confirm what the completed Docusaurus v2 setup should replace before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100