Feature mjml support #54
Open
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.
This pull request modernizes and standardizes the application's email system for app instance lifecycle events by migrating from traditional Markdown-based emails to MJML-based Blade templates. It introduces reusable MJML Blade components for consistent, responsive email layouts and updates the mail classes to use Laravel's new
envelopeandcontentmethods, passing configuration and theming data to the views.Key changes include:
Email System Refactor and MJML Adoption
Mail Class Modernization
AppInstanceReadyMail,AppInstanceMidtrialMail,AppInstanceOneDayLeftMail,AppInstanceTrialCompleteMail) to use Laravel's newenvelope()andcontent()methods instead of the deprecatedbuild(). These methods now inject theme and configuration data into the views for dynamic rendering. [1] [2] [3] [4] [5] [6] [7] [8]Reusable MJML Components
Backward Compatibility
These changes will ensure all user-facing emails are visually consistent, mobile-friendly, and easier to maintain going forward.