noNameWEB/livewire-material
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Scaffold the Livewire Material package
tests / lint (push) Successful in 1m14s
Details
tests / feature (8.4) (push) Successful in 56s
Details
tests / feature (8.5) (push) Successful in 56s
Details
tests / browser (chrome, chromium) (push) Successful in 2m9s
Details
tests / browser (firefox, firefox) (push) Successful in 1m34s
Details
tests / browser (safari, webkit) (push) Successful in 1m41s
Details

Browse Source 
The skeleton for nonameweb/livewire-material: service provider and config
(unprefixed components, blade-icons' own <x-icon> switched off, an opt-in
showcase at /material), the Testbench Workbench with its Vite build, the
CSS and JS entry points applications import, the Boost guideline and skill
with a drift test, and Gitea CI running Pint, feature tests on PHP 8.4 and
8.5, and browser tests in Chrome, Firefox and Safari.

The plan moved here from SealShare: docs/plans/livewire-material.md.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy
This commit is contained in:
Andreas Reinhold / reini
2026-09-13 04:59:21 +02:00
co-authored by Claude Opus 5
commit 9b53891a8e
33 changed files with 2731 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
resources/boost/guidelines/core.blade.php
+9
View File
@@ -0,0 +1,9 @@
@verbatim
## Livewire Material
This application uses `nonameweb/livewire-material`: Material 3 Expressive components for Laravel and Livewire, built on Tailwind CSS. It replaces UI kits such as maryUI, daisyUI and Flux in this application.
- Components are anonymous Blade components, unprefixed unless `config/livewire-material.php` sets a `prefix`. Before writing or changing a view that uses them, activate the `livewire-material-development` skill for the props, slots and traps of each component.
- Never write maryUI tags (`<x-mary-*>`) or daisyUI classes (`btn`, `card`, `badge`, `bg-base-200`, `text-base-content`…). They compile to nothing and fail silently.
- While the application runs locally, every component renders in the application's own scheme at `/material` (the showcase).
@endverbatim