Remove Inky Email Templating Language documentation #21585
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
carsonbot
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi 👋
The Inky framework has not been actively developed for about three years (last release in March 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.