Get the directory structure compatible with Three.js structure...
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- TypeScript
- Stars
- 942
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
...eventually, and make the workflow almost the same, with the same docs/examples site, so that we can render everything in a way that's familiar to the existing community?
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
No files, tests, or entry points are named. Start by comparing the current directory structure and workflow with Three.js, including the docs/examples site, and define the required compatibility boundaries. Done means the project structure and workflow are documented well enough to support a familiar rendering experience for the existing community.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- three.js, typescript, wasm
- Domain
- developer-experience, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100