maizzlejs's profile picture. Quickly build HTML emails with @tailwindcss. Created by @cossssmin.

Maizzle

@maizzlejs

Quickly build HTML emails with @tailwindcss. Created by @cossssmin.

Maizzle reposteó

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™

cossssmin's tweet image. 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™

Maizzle reposteó

Published a Liquid starter for Maizzle 🚀 github.com/maizzle/starte…

cossssmin's tweet image. Published a Liquid starter for Maizzle 🚀

github.com/maizzle/starte…

Maizzle reposteó

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. 🗳️


Maizzle reposteó

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:

cossssmin's tweet image. A dependency we use in Juice, the CSS inliner, unexpectedly published some breaking changes from an RC.

If you&apos;re using Maizzle or Juice directly and are on Node &amp;lt;18 or you&apos;re seeing errors about undici or ReadableStream, pin cheerio to the last rc version:

Maizzle reposteó

Awww yisss... That "Maizzle" line right there... @maizzlejs compiling to mailables in a Laravel app via Vite instead of its own cli.

joshmanders's tweet image. Awww yisss... That &quot;Maizzle&quot; line right there... @maizzlejs compiling to mailables in a Laravel app via Vite instead of its own cli.

Maizzle reposteó

Maizzle 5 Beta is now available 🥳 🧑‍💻 New dev server 💨 10x faster local dev 🏄‍♀️ Streamlined configs ✨ Enhanced Tailwind CSS ... and much more! Try it out: next.maizzle.com

cossssmin's tweet image. Maizzle 5 Beta is now available 🥳

🧑‍💻 New dev server
💨 10x faster local dev
🏄‍♀️ Streamlined configs
✨ Enhanced Tailwind CSS

... and much more!

Try it out: next.maizzle.com

Maizzle reposteó

Today on Laracasts, learn how to rapidly build HTML emails using @maizzlejs in our newest Laracasts course. laracasts.com/series/build-h…


We're getting close to the v5 beta. July 🤞

⌛ update docs ✅ rewrite CLI tool ✅ update Starter



Maizzle reposteó

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👇


Maizzle reposteó

🎉 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. youtu.be/K67YbL_etQg

ericlbarnes's tweet card. 10 Years of sending a weekly Laravel newsletter

youtube.com

YouTube

10 Years of sending a weekly Laravel newsletter


Maizzle reposteó

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👇


Maizzle reposteó

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👇

shrutibalasa's tweet image. 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👇

Maizzle reposteó

Maizzle 5 test coverage is at 73.04% ███████░░░ 73.04%

Maizzle 5 test coverage is at 61.31% ██████░░░░ 61.31%



Maizzle reposteó

Maizzle 5 test coverage is at 61.31% ██████░░░░ 61.31%


Maizzle reposteó

🚀 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.

cossssmin's tweet image. 🚀 Released Maizzle v4.8.1 with a small QoL update: you no longer need to @{{ }} ignore variables you&apos;d like to preserve.

Useful for ESP merge tags - this will be rendered exactly as-is as long as `unsub` is not defined:

&amp;lt;a href=&quot;{{ unsub }}&quot;&amp;gt;Unsubscribe&amp;lt;/a&amp;gt; from my emails.

Maizzle reposteó

🚀 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


Maizzle reposteó

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?


🚀 v4.6.1 has been released You can now use `maizzle.config.js` config file names. github.com/maizzle/framew…


Maizzle reposteó

Context: when running `maizzle build production`, it knows to use config.production.js automatically. Is it better to just require the user to specify desired config file via a flag, i.e. `maizzle build --config=prodConfig.js` ?


Loading...

Something went wrong.


Something went wrong.