Having a structured naming convention for your assets means you can quickly locate and edit objects you need. It also speed up the building of pages and other content.
Here's some recommended conventions, you may already have some in mind for your business.
Page names
[Store] - [Page name]
NY - Partner list
Including a store name, location, or other changeable identifier as part of the name makes it easy to identify, and can help future proof the page when it comes to redesign.
Content block names
Content blocks might be unique to a page, or may be reused across your site.
Unique:
[Store] - [Parent/Child] - [page/usage] - [block]
NY - P - Partner list - Top Hero
Re-usable:
[Store] - [Parent/Child] - [page/usage] - [block]
NY - P - Common - Footer
Media file names
Media files can be tricky to name using a convention as there can be many of them, and they may all end up with very long names.
Store - Page/Product Category - Name - Variant
Guiding principles of naming files
- Consistency is crucial: Use a standardized format for all files within a project to make them easily identifiable and sortable.
- Use descriptive, concise names: Include essential, unique identifiers (e.g., page name, store) that describe content without opening the file.
- Consider structure for list sorting, especially if you use dates or numerals, e.g. YYYYMMDD or YYYY−MM−DD
- Avoid special characters like ~ ! @ # $ % ^ * ( ) ; : ? , [ ] { } ' " | \ /
- Separate words for easier understanding: Use underscores or hyphens to separate metadata elements, rather than spaces.