Recommended Naming Conventions for StoreConnect Content

As you begin using StoreConnect you will rapidly realise the need for better organisation of your StoreConnect assets within the platform.

Having a structured naming convention for your assets means you can rapidly locate and edit objects you need. And it speeds the building of pages and other content by giving certainty you are adding the correct objects in the correct places.

We strongly recommend users implement naming conventions for their pages, content blocks and media objects. You will save a considerable amount of time and effort with a strong naming convention for your objects.

Listed below are recommended naming conventions. It’s important to understand each instance is different. These naming conventions are a suggestion to help you keep your content organised and should be adapted to fit your own requirements.

Store - Page Name

sc - Partners

Including the store name as a prefix to the page name simplifies the organisation of pages when there are multiple stores in one instance. This also allows flexibility for naming when more stores are added or if the site is redesigned.

There are two main uses for your Content blocks.

For our internal StoreConnect instance, we have created a naming convention for Content Blocks as follows:

Store - Parent/Child - Page/Usage - Block Name

sc - P - Home - Top Hero


sc - c - Feature - Growth Image

For a content block used on more than one page, this used as follows:

sc - P - common - Salesforce Integrated


sc - c - Homewares - Warranty

These elements work as follows:

Store: The first element allows you to allocate content blocks to one store to ensure unique content doesn’t get allocated to the wrong store page. It also allows naming for common items that can be shared between stores. Even if you don’t intend to have multiple store fronts, having the store designation in your naming convention, allows for future redesigns by incrementing the store name for the new version.

Parent/Child: Content blocks are often nested inside each other and it helps to rapidly identify the structure of the elements of your page. Parent elements are generally used to populate pages, while the child elements sit within the parent elements. You can see an example of content block nesting here. With multiple layers of content block nesting, it becomes important to rapidly identify where in the stack each content block fits. To further differentiate the heirarchy of content blocks, the first child of a content block can have an upper case C, while its children have a lowercase c.

Page/Usage: This is simply the page or portion of the site where the content block is being used. For instance “Features” or “About Us”. This can also be used to show if the Content Block is common for a particular subject or usage.

Block Name: This is your unique name for this content block describing your Content Block.

Store - Page/Product Category - Name - Variant


Back to Documentation