playcanvas / playcanvas/developer-site
Migration guide for Unity users
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 146
- Forks
- 72
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 33
Description
Lots of Unity users are turning to PlayCanvas to get good WebGL support/performance. Therefore, I think it would be beneficial to add a Migration Guide to the User Guide to explain how to handle things like:
- Pre-fabs
- UI creation
- Managing what is rendered by what camera
- ...and whatever else makes sense
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
Start with the User Guide and review how it currently explains PlayCanvas concepts for users arriving from Unity. Define the migration guide's scope around prefabs, UI creation, and controlling what each camera renders, then document those mappings and any additional high-value differences. Done means the guide is added to the User Guide and covers the proposed topics clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- unity
- Domain
- documentation, game-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100