stride3d / stride3d/stride-docs
Consider moving Stride Docs to Stride repo
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 39
- Forks
- 74
- Avg merge
- 3h 36m
- Merged PRs (30d)
- 2
Description
I had a discussion on this subject with xen2
btw, just a random idea, but do you think it's good to keep stride and stride-docs repo separate?
just wondering since doc is built using code, and sometimes doc examples would be better to fit in main solution (to make sure they get refactored)
I think we should investigate benefits, if it is going to make our life easier in any way.
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 investigating how the separate stride and stride-docs repositories are built and how documentation examples relate to the main solution. Compare the maintenance and refactoring benefits of moving the documentation into the Stride repository; done means recording a clear recommendation and migration scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100