These are some best practice recommendations on how to keep your emails, themes, and modules organized! It's important to note that everyone goes about it in their own way, but at the end of the day it all comes down to setting up a strong naming convention process to ensure your team is able to efficiently organize your content.
Best Practice for Organizing Emails and Themes: Using Tags
On the email and theme side of things, using tags can help group like emails and themes together. In the below example you can see that the email was tagged with “Newsletter”, “summer”, and “monthly” in the info section when creating an email, if you would like to add multiple tags you'll need to separate the tags with a comma between them. The tags can be seen and searched for in the email center:
As mentioned above tagging is also something you can do when creating themes:
These theme tags can then be searched for when searching for a theme or applied using the advanced filter option:
Recommendations for Modules: Module Categories and Brand Restrictions
Before getting into examples of different naming conventions to use, we need to cover the brand and category system for modules. Knak is configured with three base categories: headers, body, footers. These three should get you started, but you can also create as many as you'd need. For example some other categories you could use could be: CTAs, Social, Newsletter, General, etc. The options are endless! This category will act as a storage folder for all modules you assign to it, so create as many as you need to keep things neat and tidy.
You can create new module categories by navigating to the admin side of the platform > modules > categories > create new category:
You will also be able to assign a single brand or as many brands to a module as well. This will simply help with the filtering of the modules screen as well as begin to limit the number of modules seen when filters are applied.
Now let's get to the good part, what are some of our best tips and tricks for how you should name your assets in Knak?
We recommend keeping these tips in mind:
Be Consistent (consistency is king here)
Be Detailed (include details like: brand, description, region, type, date, etc.)
Use a Separator (examples: | \ & - .)
Make if Easily Identifiable
*Optional: Use a leading unique number (harder to maintain but could be very helpful)*
Here are a few examples to get the gears turning:
Module:
Knak | 3x2 Merch Grid | APAC | Body | Jan 21 2021
Knak - Field Ops - Webinar Speaker Block - Body - Texas - 1.21.2021
BW Logo / Header / NA / 1212021
Email:
January New Year Newsletter | A | Jan 21 2021
January New Year Newsletter | B | Jan 21 2021
Poor NPS - Nurture Campaign - Email 1 of 5 - SMB Segment - Jan 21 2021
Theme:
2020 Newsletter \ Monthly \ Locked \ APAC \ 1.21.2021
2021 Newsletter \ Weekly \ Editable \ APAC \ 1.21.2021
*An optional method you could use would be to include a unique leading digit that went in numerical order for modules so that when users are searching for modules while building an email it is clear about what order modules should be inserted into an email or the number could rank the modules so the more common modules appear first like you can see in the below image: