Hi @Kristin McLerran! I hope you get some good tips and suggestions from the community! I wanted to send along this presentation from Activate 19, Iterable's growth marketing conference. Ted Goas from Stack Overflow does a great presentation on Design Systems for Email. Hope it helps!

https://activate.iterable.com/sessions/design-systems-for-email-bring-order-to-the-chaos/

---

Amazing, thank you @Sarah Lubecki! I'll take a look today 😀

---

@"kristin.mclerran" I've not had a chance to develop a modular email design system using Iterable—I'm still in the integration stage—but I have done this with a few other popular ESPs. One of my favorite methods is to use the same principles you would in developing a material design system or brand identity but specifically with emails and the corresponding email code. Create the look and feel--the ideal master template with switchable/adaptable components. You'll need to define your naming conventions and make sure you're allowing room for future changes/adaptions. Documentation here is vital for referencing as your team grows and making it easier to reference the different components quickly.

From what I've learned about Iterable, I would think you'd be able to do this by leveraging snippets and positional parameters (at least that's what I'm looking into for developing the EDS in my current role). For example, say you have a loyalty rewards snippet that changes color based on how long the users has been an active reward member. You'd use the positional parameters to change that snippets color based on the guidelines you've established.

Beyond that, a lot of it will be managing expectations within your company's current workflow. Happy to chat more if you'd like. Love this stuff and please share what you find!

---

Hi @Melissa McCollum - thank you so much for sharing! I think we are going to move toward using positional parameters. I'd love to chat with you more about this! I'll DM you 😀

---