Creating a clean and efficent project and experimentation environment
A common problem with many Unity Projects is bloat, by bloat we mean the inclusion of large sums of content and code that serves no purpose in your finished product. Unity's build process will make a valiant attempt to strip down unused code and content but that process is far from perfect and beyond that this bloat adversely impacts your development environment slowing your work and increasing the likelihood of logical errors.
To help you keep your project clean and efficient Heathen has defined a standard folder structure making it easy to omit unwanted content such as Sample scenes, Documentation and Prefabs. You can read more about that at the link below.
In practice we recommend that projects that make use of 3rd party assets such as Heathen's assets or any other plugin, Unity Asset Store asset or even Unity's own extensions; has 2 separate Unity Projects.
This is your core Unity Project and the one that will be used to build your finished product.
When importing assets into the project we recommend you omit (do not import) sample scenes, demos, and documentation. In most cases you will also want to omit prefabs. The content included in samples and demos is not intended by anyone to be used in a production project.
This is a second project that should be on the same Unity Version as your Production project. This project should import all of the same assets, plugins, etc. as your production project only this project should fully import the assets including
- Example Scripts
The idea is that this project is your place of learning, its your messy sandbox where you don't need to be clean or safe. Ideally you wont modify the demos and examples of the assets you import as this project also serves as a clean example of those 3rd parties. A place where you can use the original samples as intended by the author.