What do you do when the UI libraries you love don't have licenses compatible with the CMS you're building?
You build your own.
In my latest video, I share the full story behind ArtisanPack UI — the licensing issues that started it all, how Mary UI helped me get unstuck, the new components I've added, and what v2.0 brings with Livewire 4 support.
If you're in the Laravel ecosystem, I'd love to hear what you think.
The story behind the ArtisanPack UI Livewire Starter Kit: I engineered it to solve the custom starter kit docs puzzle. The key? Packagist + Laravel's new --using flag.
The result is a starter kit that lessens the friction for starting a new Laravel app or website. Here's how I built it.
The journey of #javascript is the poster child of out of control #complexity. What started as tiny client side code to introduce some interactivity has eaten html itself (virtual #dom) and then metastasized also on the server side. A gargantuan duplication of functionality between client and server that eventually backlashed into the #htmx and #livewire type approaches.
When you throw in the explosion of mobile clients (with architectures controlled by a duopoly) you get to the lunacy of today.
It’s been a busy sprint. Episode 3 of What I'm Working On is out now.
In this update:
- Livewire UI Components v2.0: I added a new Glass design system, switched to ApexCharts for better visuals, and added Sparklines.
- Livewire 4: Full compatibility added.
- Visual Editor: A first look at my custom block editor. I demo how I'm handling responsive styling and state-based styles (hover/focus) differently than WordPress.
Watch here: https://youtu.be/P0LxdmmrZwI
#TheMetalDogArticleList
#Blabbermouth
MÖTLEY CRÜE To Release 'Live Wire' EP For April 2026 'Record Store Day'
https://blabbermouth.net/news/motley-crue-to-release-live-wire-ep-for-april-2026-record-store-day
#EP #ToRelease #LiveWire #newrelease #anniversary #vinyl #Blabbermouth #metal #music
I saw a direct debate in the survey responses regarding the frontend stack.
When asked what they would improve about the ecosystem, requests for "More #Livewire support" sat right next to simple demands to "Get rid of Livewire."
The community has strong, mixed feelings about the TALL stack versus other approaches.
Beyond the framework wars, the survey revealed deep insights into what #Laravel devs actually want from the ecosystem.
Read the community responses here https://coz.jp/knr8Tr
My January wrap-up for ArtisanPack UI is here! I'm making good on my goal to talk about what I'm building.
Highlights:
- Launched 3 new essential Laravel packages: Forms, Analytics, SEO.
- Released a major v2.0 update for the Livewire UI Components package, including full Livewire 4 compatibility and a complete visual and charting system overhaul.
- Started working on a long-term support plan.
@cyberseckyle I like to read about the detailed mechanics of how security works, such as the #TLS protocol, #SSH, #livewire, #Goblins, ...
The path to a robust Livewire UI library for Digital Shopfront CMS had a major turn: incompatible licenses forced a pivot. The result is ArtisanPack UI Livewire UI Components—an accessible, open-source, and pragmatic solution packed with custom features like vertical tabs & drag-and-drop image handling. It's built to help developers create fast, modern Laravel interfaces to empower small businesses.
Read the full story: https://tinyurl.com/jm-apui-livewire
Sometimes I think about building the complete Frontend new with #Livewire. But I guess I don't have time for this.
#Inertia SSR doesn't work for some reasons for this project (I wasted hours because I tried to get it work) and I'm honestly sick of big JS frameworks.
Some day I will do this, but I honestly have no idea when it will come to it.
#Livewire claims single-file components improve “colocation,” but in practice this is misleading.
Bundling #PHP, #HTML, and #JS in one file only shifts mental overhead into scrolling, reduces clarity, and weakens static analysis.
True cohesion comes from separating responsibilities, not cramming them together.
For small, throwaway components single-file may be fine, but for long-lived, testable, maintainable code, class-based components remain the safer choice.
• (Message|Action|Request) Interceptors
• Islands & nested islands
• Bundled & lazy requests
• Native drag-and-drop sorting
are an excellent addition.
--
The defaults are optimized for speed of authoring, not durability for strictly structured codebases.
Noise:
* Emoji filenames
* Single-file / multi-file components
* “colocation” pitch is misleading
Co-location ≠ cohesion
--
Class-based components remain the most:
- readable
- statically analyzable
- long-term maintainable
We’ve launched Filament v5 and Filament Blueprint today! 🤖
Filament v5 adds support for the newly-released Livewire v4!
Blueprint is a premium Laravel Boost extension that gives AI agents deep, structured knowledge of Filament, so they can write detailed implementation plans.
https://filamentphp.com/content/danharrin-filament-v5-blueprint
New year, new tools for your Laravel projects. ArtisanPack UI gives you 70+ accessible Livewire components—buttons, forms, modals, data tables, and more. All with proper ARIA, keyboard navigation, and focus management built in. Stop rebuilding the basics. Start building features.
Why #LiveWire’s new electric maxi-scooter could finally make Americans fall in love with #scooters
This isn’t some underpowered runabout meant as an afterthought. It’s built on the company’s S2 platform – the same architecture used for their #motorcycles. I happen to own a LiveWire S2 Del Mar, and with its 0-60 mph (96 km/h) time of just over 3.0 seconds, I’m nearly unbeatable when the light turns green.
https://electrek.co/2025/12/03/why-livewires-new-electric-maxi-scooter-could-finally-make-americans-fall-in-love-with-scooters/ #EV
If you slept on that Livewire CVE from July – like my lazy ass did – you should take immediate action as it's widely exploited right now.
https://github.com/livewire/livewire/security/advisories/GHSA-29cq-5w36-x7w3
It does look like this vulnerability is now being actively exploited in the wild:
https://xcancel.com/barryvdh/status/2005404768936865812
Looks ugly and I can find some comprised sites using a simple Google search…
CVE-2025-54068 #livewire #vuln #laravel #framework #web #application #threats #php #blade #informatique[ https://www.synacktiv.com/publications/livewire-execution-de-commandes-a-distance-via-unmarshaling.html ] La possession de l'APP_KEY sur une application Livewire en v3 ou supérieure permet d'avoir un contrôle complet.
De plus, plusieurs APP_KEY sont des valeurs par défaut sur des milliers d'app Laravel exposées publiquement.
L'équipe Livewire considère l’exposition de l'
APP_KEYcomme une frontière de sécurité suffisante. Or, compte tenu de la fréquence des fuites ou de l'utilisation de valeurs par défaut d'APP_KEYdans la nature, cette position semble sous-estimer les risques réels.
#LiveWire reveals more details on its new lower cost #S4Honcho #electricmotorcycle
125-cc equivalent available in both a street-legal capable of being operated by riders who possess #motorcycle license in Europe or in the US, and a license-free off-road version.
“The S4 Honcho Street will qualify for A1 licenses in Europe and the UK and M-endorsement in the U.S., offering lightweight, urban-friendly electric mobility with intuitive performance and removable batteries”
https://electrek.co/2025/10/28/livewire-reveals-more-details-on-its-new-lowerer-cost-s4-honcho-electric-motorcycle/