{"id":29010,"date":"2021-05-17T10:00:00","date_gmt":"2021-05-17T14:00:00","guid":{"rendered":"https:\/\/www.litmus.com\/?p=29010"},"modified":"2025-10-08T16:55:31","modified_gmt":"2025-10-08T20:55:31","slug":"how-to-organize-email-modules","status":"publish","type":"post","link":"https:\/\/www.litmus.com\/blog\/how-to-organize-email-modules","title":{"rendered":"7 ways to organize your email modules into useful categories"},"content":{"rendered":"\n\n\t
\n
\n \t
\n \t\t
\n \t\t\t
\n \t\t\t\t

So you\u2019re using email modules<\/a> or components to build your emails, which is saving you a good deal of time. But now you\u2019re running into new issues. With your growing number of code modules, how do you organize them for easy reference? How do you pass off these modules for other team members to use? And make sure they use the right ones?<\/p>\n

To keep your email production process running smoothly, there has to be some way to organize email modules\u2026<\/p>\n

Imagine I\u2019m flourishing a top hat while I introduce you to Litmus\u2019 newest feature: Categories for Design Library<\/a>.<\/p>\n

Design Library lets you seamlessly create, QA test, and store key email components in one place for quick collaboration across your team. And now, Litmus Enterprise customers can use tags to categorize and organize modules in Design Library\u2014including snippets and partials. <\/b>Modules can even be in multiple categories for flexible ease of use.<\/p>\n

\n\n\n\n
\"Litmus<\/td>\n\n

Take your email marketing to the next level with Litmus Enterprise
\n<\/strong><\/p>\n

Create emails with a quick drag and drop, automate QA testing, collect reviews and approvals, and get advanced analytics all in one spot. Plus, integrate with popular ESPs for a seamless workflow.<\/p>\n

Interested? Let\u2019s chat \u2192<\/a><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/h2>\n

Ideas for categorizing your modules<\/h2>\n

So how<\/i> should you organize your email code modules for ultimate efficiency? If you\u2019ve ever used a platform with folders, you know this isn\u2019t as simple as it sounds.<\/p>\n

Would you find this week\u2019s newsletter under Marketing > Emails > Newsletters > Week of 5\/17? Or Marketing > Email Team > Q2 2021 > Copy?<\/p>\n

While we might expect to find our email in one folder, another person on the team may be looking in a different place.<\/p>\n

The great thing about organizing your code modules in the Design Library is you can use tags.<\/i> These allow you to \u201cstore\u201d your modules in multiple places\u2014so whether you\u2019re looking in \u201cHeaders\u201d or \u201cNewsletter,\u201d you\u2019ll be able to find your newsletter header! \ud83d\ude4c<\/p>\n

I recently sat down with our email team to learn their favorite ways to organize code. Here\u2019s what they shared, including some suggestions of my own:<\/p>\n

1. By module type<\/h3>\n

In this approach, you categorize your modules by what<\/i> they are. This might look like:<\/p>\n