blender-studio-pipeline/docs/media/naming-conventions
Demeter Dzadik f2e2a70f9d New naming convention proposal (#149)
A major overhaul of our in-blend naming conventions.

Goals:
- Every asset datablock must have a unique name to avoid Override issues.
- Separators could be more consistent and meaningful.
- Cover more cases, eg. node groups, bones, etc.
- Simply bring things up to date to align with our new preferences based on previous production experiences.
- Make sure there's some reasoning behind everything, and it's not just a legacy convention carried from old times.

These changes have now been discussed and agreed upon between myself, Andy and Simon, so as far as I'm concerned, they can be committed soon if nobody comes up with any new objections.

This can also provide some foundation for the naming aspects of an upcoming Convention Checker system.

Reviewed-on: studio/blender-studio-pipeline#149
2023-11-23 17:11:45 +01:00
..
collection_hierarchy_naming_example.png New naming convention proposal (#149) 2023-11-23 17:11:45 +01:00
hierarchy_name_example.png New naming convention proposal (#149) 2023-11-23 17:11:45 +01:00