> ## Content Index
> Fetch the complete content index at: https://blog.tsd.digital/llms.txt
> Use this file to discover other available public pages before exploring further.

# Naming conventions for Umbraco
- URL: https://blog.tsd.digital/naming-conventions-for-umbraco/
- Published: 2007-11-26T10:30:56.000Z
- Updated: 2007-11-26T10:30:56.000Z
- Author: Tim Gaunt
- Tags: ASP.Net, Umbraco, Web Development, WebDD, .Net, #Import 2025-04-01 05:36

Having only recently started to use Umbraco I've taken a couple of days to familiarise myself with the way it works and try and get a few best practices in place, I expect these will be updated over time but you've got to start somewhere ;) As with any code, I think it's very important to follow a consistent naming convention -whether it's the same one everyone else follows or not, you need to be able to pickup code you wrote months/years/decades ago and still understand it. Your styles will no doubt change over the years but you get the idea. I've chosen to follow the following "style": **Document Types:** Lowercase the first letter of the aliases followed by capitals for the new words (similar to [Hungarian Notation](http://en.wikipedia.org/wiki/Hungarian%5Fnotation?ref=blog.tsd.digital)). Use descriptive names i.e. Home Page for the document type as it'll be client facing. Suffix with "Page" if it is a page document type (as opposed to i.e. a screen shot) **Templates:** If the template is specifically for a document type, use the same name for the template, if it relates to multiple document types name it logically i.e. "Master Template" or "Left Menu" **Macros:** Prefix the macro alias with uppercase TSD to avoid conflicts with other macros. Prefix the name with \[Source of the macro\] i.e. \[XSLT\] or \[User Control\]. This is something I picked up from the sample package created by [Warren Buckley](http://www.creativewebspecialist.co.uk/?ref=blog.tsd.digital) that I think makes it easier to understand what's going on **XSLT Files:** Prefix the name with the site's abbreviation i.e. for [www.thesitedoctor.co.uk](http://www.thesitedoctor.co.uk/?ref=blog.tsd.digital) it would be TSD or for [www.wineandhampergifts.co.uk](http://www.wineandhampergifts.co.uk/?ref=blog.tsd.digital) WAHG if it's a site specific XSLT file otherwise name conventionally i.e. [CamelCase](http://en.wikipedia.org/wiki/CamelCase?ref=blog.tsd.digital)