Woo, that's @maizzlejs setup on @AtoBeach 🏖️
Just built @leyeConnect's beautiful welcome email design - thanks @tillythecoder for your awesome Maizzle + Laravel video 🥳
I get more excited about AtoB as each day passes, Leye has been such a phenomenal designer to work with!
Maizzle 5 is here 🥳
- 10x faster local dev
- Updated template
- Streamlined configs
- Streamlined Tailwind CSS
- New dev server with HMR*
- Content source globs
- `npx create-maizzle`
- Enhanced CSS support (vars, calc)
* Hot Markup Replacement™
It’s a breaking change but might as well do it now. Also variables in Maizzle 5 can be accessed both ways, it’d be just a duplicate for backwards compatibility reasons.
🗳️
A dependency we use in Juice, the CSS inliner, unexpectedly published some breaking changes from an RC.
If you're using Maizzle or Juice directly and are on Node <18 or you're seeing errors about undici or ReadableStream, pin cheerio to the last rc version:
Maizzle 5 Beta is now available 🥳
🧑💻 New dev server
💨 10x faster local dev
🏄♀️ Streamlined configs
✨ Enhanced Tailwind CSS
... and much more!
Try it out: https://t.co/D0aomtGxrq
It's been some time since my last update for @formifyflow. I wanted to send emails to my users, but I couldn't find an affordable email marketing tool, so I created my own, MailifyFlow. It uses @laravelphp , @filamentphp , @maizzlejs , and Amazon SES.
Check link below👇
🎉 This week is the 10-year anniversary of the weekly @laravelnews newsletter! If you've ever been curious on how I make it each week I created a video.
https://t.co/IaTNNxWtf2
Hey #buildinginpublic , excited to share my new find: crafting responsive Mailables using Tailwind CSS! While I used to design emails with regular CSS, Tailwind feels like home. Found @maizzlejs while creating emails for @formifyflow and it's a game-changer. Check below👇
@snider224@shrutibalasa They’re usually decently sized, like under 20KB for simple transactional emails.
But the cool thing is you can make them as complex as you want. Including plain/“rich” text. You get full control 🫡
I started using Maizzle a few days ago and I’m totally loving it.
No more manually adding long inline styles for email views. You can use Tailwind to style your emails 🪄
You can integrate it with your Laravel project, so everything is super seamless.
Here’s a quick video👇
🚀 Released Maizzle v4.8.1 with a small QoL update: you no longer need to @{{ }} ignore variables you'd like to preserve.
Useful for ESP merge tags - this will be rendered exactly as-is as long as `unsub` is not defined:
<a href="{{ unsub }}">Unsubscribe</a> from my emails.
🚀 Released Maizzle v4.8.0
- define arrays of asset sources/destinations
- support more tags/attributes for urlParameters
- fixed some template.source path issues
- switch to fast-glob
- added more types
Thinking of changing the Maizzle build command signature in v5.
Instead of:
maizzle build production
… I’m considering:
maizzle build -c [config-name].js
This way you can use any file name for other build targets.
Thoughts?