- How do I install bebo925/tall in a Laravel application?
- Run composer require bebo925/tall, which also pulls in wire-elements/modal, then run php artisan tall:install. That command installs the JS dependencies, creates a tailwind.config.js, updates your webpack.mix.js, and generates an app.blade.php layout. Afterwards you edit the host variable in vite.config.js so hot module reloading works, and optionally publish views with php artisan vendor:publish --tag="tall-views". Treat it as one-time scaffolding rather than something you re-run.
- What Laravel, PHP, and Livewire versions does bebo925/tall support?
- The README does not publish composer.json constraints for PHP, Laravel, Livewire, or wire-elements/modal, so check the package's composer.json and its Packagist entry before pinning it. It targets a TALL shape: Laravel 10 or 11 with Blade, Livewire 3, Alpine 3, Tailwind 3, and Vite 5. Confirm that the modal layer matches Livewire 3 event and dispatch semantics before your next upgrade. Laravel 12 or Livewire 4 compatibility is undocumented.
- Which Blade components are included in the TALL preset?
- It ships buttons (x-tall::button with default, primary, secondary, warning, and danger styles plus flat, circle, and outline types), inputs (x-tall::input wrapping text, checkbox, radio, textarea, rich-text, and select children), panels with body and footer slots, page headings with meta and actions slots, tables with heading slots, dropdowns, multiple selects, messages, and a modal layout. Livewire components such as tall-markdown-x and a confirmation dialog are included as well. Everything is referenced through x-tall:: prefixed tags.
- Does bebo925/tall require Livewire and wire-elements/modal?
- Livewire is effectively required: the modal, dropdown, and notification flows assume it, and the modal layout is built on wire-elements/modal, which Composer installs as a dependency. Alpine-only or Inertia-based frontends would need to replace those components rather than configure them. Buttons, inputs, panels, and headings still work in plain Blade, but you lose much of what the package provides.
- Will php artisan tall:install overwrite my existing Tailwind, Mix, Vite, or layout files?
- Yes, potentially: the installer writes to tailwind.config.js, webpack.mix.js, vite.config.js, and a new app.blade.php, so commit your work first and diff the result before accepting it. The vite.config.js host edit is environment specific and a common source of HMR CORS problems on shared hosting and non-local domains. If you build with Laravel Mix instead of Vite, expect a manual merge of the generated config. On a greenfield repository this is closer to a 30-minute setup.
- How do I customize or theme the TALL components?
- Publish the Blade views with php artisan vendor:publish --tag="tall-views" and edit them directly. There is no design token or theming layer and no documented slot or extension API beyond publishing, so brand alignment becomes per-component surgery and you inherit maintenance of the forked views. Style variants are hardcoded prop strings such as style="primary" or button.flat rather than composable primitives. That is acceptable for internal tools and admin CRUD but weak for customer-facing brand surfaces.
- How do I show flash messages and notifications with x-tall::messages?
- Place x-tall::messages in your layout, which the generated app.blade.php already does, and flash a message with session()->flash('message', ['type' => 'success', 'message' => 'Saved!']). The type key controls the styling variant, and the component accepts a dark prop for dark backgrounds. You can also trigger it by dispatching a browser event from Livewire.
- How do I use modals and confirmation dialogs from this package?
- Render x-tall::modal with the title and actions slots; the behaviour comes from wire-elements/modal, which the package requires. A confirmation dialog is also provided as a Livewire component. Because the modal layer is a third-party dependency, test it against your Livewire 3 event semantics and pin both packages to fixed versions together.
- Is bebo925/tall safe and maintained enough for production?
- Runtime risk is low: these are Blade templates with no network calls, MIT licensed, and rendering cost is trivial. The maintenance profile is the real concern, with a single author, one star, no visible CI or test suite, no changelog, and no documented semver or upgrade guide. Pin a fixed version or fork and internalize the components, particularly if you rely on the modal or table behaviour. Also note that the table and select components do not appear to paginate, so Livewire round trips are yours to manage.
- What are alternatives if I need a proper design system instead of this preset?
- If you need design tokens, theming, and a documented component API, this is not a design system: look at Flux UI, Tailwind UI, or another component library with a real release cadence. For project starters, compare laravel/breeze and laravel/jetstream, which cover auth scaffolding this preset does not. bebo925/tall fits internal tools, admin panels, and form-heavy MVPs on a TALL stack, while public brand surfaces or Inertia and Alpine-only frontends will pay more to replace the Livewire-dependent pieces than they save.