Firms take different approaches to template files. Some, (I’m looking at you @twiceroadsfool) like to load ’em up with most everything a project needs, and let the teams weed out what they find they don’t need. Others take a more streamlined approach, and provide the universal basics, with teams adding more in from ‘resource files’.
I generally take the streamlined approach. I want the consistent data to be in the template, and anything that requires intermediate/advanced use to be already in place awaiting minor editing per the project specifics. Which means, some of what I include is static, and some requires editing. How to communicate which is which? I’d rather not have a team spend time deciding, so I add a suffix:
And now they know: Which ones to edit, and which ones to not.