Hey! I'm that marketing bod you're referring to. I wasn't trying to oversimplify the challenge of coding email templates. I was only trying to say that learnin

Hey! I'm that marketing bod you're referring to. I wasn't trying to oversimplify the challenge of coding email templates. I was only trying to say that learning markdown is a great stepping stone for our team to get more technical skills under our belt. We have to crawl before we can walk. If everyone understands how to do things like create hyperlinks or knows how bold and italicize words without the help of a WYSIWYG panel, that's a good thing in my book. Maybe we can't code the most beautiful, responsive, complex emails in the world, but hey, everyone starts somewhere. I'm really lucky that I work at a company where we're encouraged to learn and where marketing is actually included in decisions like moving a blog from Wordpress to Jekyll. We had engineers who asked us to consider the extra work of learning Git and markdown. We welcomed the challenge and saw this as a unique opportunity to collaborate. I don't look at this decision as some hasty bait and switch move made by the engineering team. We were consulted as partners in the decision and I'm happy with where we landed. One of the writers on our team helped scrub the blog before we published it. At one point she even had more commits on the repo than any of the devs! I loved seeing that. I'm excited about the possibilities and would encourage you to be a bit more optimistic about our capacity to learn new skills.