In a previous post, I introduced bldr.io; an Open-Source Command Line Interface (CLI) that integrates with Salesforce Marketing Cloud (SFMC) to provide users access to their assets/files within the platform from their local environment and the ability to modify them without having to copy/paste/update them in the platform.
In this post I want to dive into how builder can be used within a team setting to manage projects within SFMC leveraging GIT.
Suppose you work on a team with Email Developers and Production Specialists.
Email Developers are usually team members who are responsible for taking the email design/creative and ensuring that it will render correctly across the various email clients.
Production Specialists are usually team members who are responsible for putting the final touches on the emails before it goes out the door.
In my previous roles, these two team members are split for various reasons. Email Developers may not have final image assets, final links, or have in-depth knowledge of an ESPs scripting language (in the case of SFMC - AMPscript). So they will typically use placeholder images and links to keep their process moving.
So how can BLDR help with this flow?
- Marketing Team receives creative brief for campaign/series of emails to be worked on
- Designer creates email designs or provides templates for build
- HTML Developers start working on coding the emails and checking render tests
- Developer passes file to Production Specialist to update image URLs, links etc.
Right about here is where the inevitable changes happen; rendering issues pop up, image URLs change, links change... any number of updates/adjustments need to happen.
Now if you're currently using some form of Version Control for your email development process, you're already ahead of the game. However, as well all know, it's easy to make quick updates directly in SFMC and forget to pass them back to GIT.
Through leveraging BLDR to manage pushing/updating your code in SFMC you now make GIT and your local version the source of truth.
In addition to it being the source of truth, your team can leverage branches to work in tandem!
Top comments (0)