Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.3k
Remove Inky Email Templating Language documentation#21585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
The Inky framework has not been actively developed for about three years (last release in March 2022). In addition to Sass deprecations and other bugs, the project is generally no longer up to date when it comes to implementing email templates.In my opinion, it no longer makes sense to list the project as the only solution for designed emails.
javiereguiluz commentedNov 29, 2025
I don't think you are wrong, but Inky is still the Symfony recommendation and the only solution that has an integrated Twig solution. So, we cannot remove it just yet, so we're closing this PR without merging. For now, I created#21604 to mention MJML as an alternative. I hope you understand this. Ideally, we should open an issue in the Symfony code repo (https://github.com/symfony/symfony) to discuss if we should deprecate Inky integration by MJML. Thanks! |
…guiluz)This PR was merged into the 6.4 branch.Discussion----------[Mailer] Mention MJML as an alternative to InkyThis is an alternative to#21585. Inky is still the Symfony recommendation, so we cannot remove it yet. But, let's mention MJML as a valid alternative.Commits-------897a3f3 [Mailer] Mention MJML as an alternative to Inky
FlorianBoe commentedDec 1, 2025
Hello! |
Hi 👋
The Inky framework has not been actively developed for about three years (last release inMarch 2022). In addition to Sass deprecations and other open bugs (see issues), the project is generally no longer up to date when it comes to implementing email templates.
MJML is another framework for this use case, although many people probably use an external service provider for this.
In my opinion, it no longer makes sense to list the project as the only solution for styled emails. I would suggest removing the reference to Inky, since otherwise it could be perceived as a best practice within the ecosystem.