We’re super excited about the reception that Foundation for Emails and Inky have gotten, and want to talk a little bit about where they are going. We see a future where Inky becomes the standard for how emails get written, anywhere and everywhere. One of the biggest pieces of this is making it easy to extend Inky so that everyone can build their own custom open source and proprietary email components. While the current Inky language supports all of the core building blocks you need to create beautiful, responsive HTML emails, we have also heard many requests for additional components and the ability to extend Inky.
Where are we headed?
We believe that Email development should be just as simple as web development, where you can easily integrate open source components, extend those components with your own custom styles, and create your own custom pluggable elements. Just like a company builds up a library of custom, pluggable modules of code and components, they should be able to create a set of custom, pluggable inky tags that make generating brand-coherent, beautiful emails as easy as can be.
What Should Custom Inky Tags Look Like?
The question at hand is what those pluggable inky tags should look like. We’d like them to be programming language agnostic, so that there can be native Inky implementations in languages like Ruby, Python, etc. We’d also like them to be flexible, capable of handling the multitudes of email components out in the world. Clearly there needs to be a template component, a SCSS styling component, but what else?
What are your thoughts? What are they key components you would need? To what extent do you think they can be isolated and standalone vs needing knowledge of the rest of the structure of the email? Do you have example components you’d like to implement that we can play around with and see if this would work?