Naming Conventions ID: PM-BP-NC
Organization is paramount to the success of any endeavor. Packages are no different. This lesson will begin addressing some common naming conventions that you should adopt in your packages, package versions, and assets to make them more usable for both yourself and others.
- How you organize and name your packages matters
- It is often best to create packages on either dummy or demo sites under your own account - there can be complications creating packages on live client sites or under client accounts.
- There are several valid schemes for semantic versioning, but the easiest way to manage versions is using a numeric version number
- Avoid naming conflicts with your package by using a unique naming convention and consistent organization scheme
- Paths, folders, and asset names should be intuitive for users installing your package and should avoid conflicts with assets from other packages