Internal Naming Conventions
Naming Conventions help to organize your content and make your HQ easy to navigate. Content Tags are great for sorting and filtering your content, but building out a naming convention is a great way to give yourself and anyone using your HQ easy visual cues, so why not make use of both!
You are able to configure each asset in your Content Library with 2 different names: an Internal Name and a Public Title.
The forward facing title that anyone visiting your Content Track will see.
|You do have the ability to override the Public Title at the track level, but it’s still important to give each asset a Public Title that you would be comfortable with your prospects or customers seeing. More importantly, you’ll want to ensure the Public Title is something that makes sense to the world outside of your organization.|
The name of the asset which is only visible within your HQ, and will not be seen by the public.
|This is where you can apply your chosen naming conventions, and have the asset names include markers and abbreviations which are meaningful to you and your organization.|
Below are a couple ways we have found that clients have utilized the Internal Name when organizing content in the Content Library:
Language: If you are supporting multiple languages, you will need to have a forward facing name in the relevant language, but will ideally want an internal name that is in English (or whatever your default language is internally). The Public Title/Internal Name allows you to have that functionality, making the use of multiple languages easier and more practical.
Lines of Business/Verticals: If you have one asset that you have branded differently for different lines of business or verticals, you are able to clarify that in the Internal Name, which will allow you to quickly and easily find what you are looking for when you are building your Content Tracks. You could easily create a naming convention that utilizes brackets and short forms of verticals (eg. (HC) for Healthcare).
Each of your Content Tracks will have a name that you give them. That name doesn’t appear in the forward-facing URL, so you are able to create a name for it that will make sense for your organization internally.
Below are a couple ways we have found that clients have utilized internal naming conventions when creating their Content Tracks:
Language: Because the name of your Content Track will never be public facing, you can keep the name of the track in English (or whatever your default language is) and include a language code (eg. (SPA) for Spanish) so that you can quickly and easily know the language of the Content Track you are looking at.
Gated (or not): Another good thing to denote in the name of the Content Track is whether you have included a form/forms in the track. You could denote this with something simple like an asterik, or could use a similar structure to the Language example above, using a short form of the form name, or whatever makes sense to your organization internally.
Channel: Making note of the channel affiliated with your Content Track is helpful for two reasons: the first being that, as stated previously, it’s a great way to quickly and visually understand what you are looking at. The second reason is that when you are looking at all of your Content Tracks, they appear in a grid-like view with some additional analytics information appearing, which means that you will be able to quickly glean how well your Content Tracks are preforming via channel.