We are in a situation where we have over 200 templates. We do not need all of them, but even if I cleaned up, they would still be too many. And the bigger problem is with the ones we do use.
There are several dimensions along which templates are separated:
- work vs publish - their directory hierarchy is different, work files are usually in user sandboxes, etc.
- asset vs shot - again different hierarchy, and often assets are not user-specific.
- dcc app - esp. tag/output/node field - different dcc tk apps have hardcoded different field names for the tag. I thought field aliases were the solution to this, but could not get it to work.
- file type and roots - for instance we have separate roots for renders, caches. Scene and render templates are quite different in other ways.
We are getting a combinatorial explosion of these, and managing them becomes increasingly difficult.
We have abstracted some pieces away into their own templates that get referenced (e.g. “cache_base_name”), but it is not satisfactory at this point.
Of course, one answer would be to simplify our naming conventions, but some decisions are very practical, such as having different roots.
Anyone reached template nirvana and willing to share?