Weave Code
Ux Blocks Core Laravel Package
symfinity/ux-blocks-core
A Laravel package providing core primitives for building reusable UX blocks—base block classes, registration, rendering, and layout helpers—so you can compose dashboard widgets, page sections, and dynamic content consistently across your application.
Atomic UX Twig components with registry-aligned markup and role CSS
Frequently asked questions about Ux Blocks Core
- What is symfinity/ux-blocks-core used for in a Laravel application?
- The package is the foundational layer for composing reusable UX blocks in Laravel. It provides block registration, resolution, configuration, a composable render pipeline, and layout helpers so dashboard widgets, page sections, and dynamic content can be rendered consistently. It is not a full UI kit; your application still supplies templates, styles, and business logic.
- How do I install symfinity/ux-blocks-core?
- Install it with Composer and rely on Laravel package auto-discovery for the service provider, then publish any config or views if the README instructs you to. The provided release notes do not confirm the exact publish commands, so verify them before wiring it into an app. Pin the exact 0.1.6 release rather than using a caret constraint, and commit the lockfile.
- Which Laravel and PHP versions does this package support?
- The package's Laravel and PHP support matrix is not confirmed in the provided release information, so check its composer.json constraints before adoption. Compare its illuminate/* requirements against your current LTS and your next upgrade target. Run the package's tests inside your application's CI matrix before relying on it.
- Does it work with Blade views or only JavaScript front-ends?
- It is intended for server-rendered, Blade-first Laravel applications where a shared block library reduces duplicated markup. It is a poor fit for API-only backends or Inertia, React, and Vue front-ends, where it would become a parallel rendering stack. A design-system layer can use it for structure while your own CSS layer handles styling.
- How do I register and render UX blocks in Laravel?
- The package provides lightweight block registration and resolution plus extensible contracts for custom blocks. You configure blocks centrally and render them through the composable pipeline in your views. Because the exact config schema and API surface are not detailed here, confirm them in the README and a short spike before building templates around them.
- Should I use symfinity/ux-blocks-core in production at version 0.1.x?
- Treat 0.1.x as pre-1.0 software where breaking changes are possible, even in patch releases. Pin an exact version, review lockfile diffs as a standing gate, and avoid retrofitting the package into an established component library. Introduce it greenfield on a new page or internal admin screen behind a feature flag.
- What are alternatives to using ux-blocks-core for reusable Laravel UI components?
- Native Laravel Blade components, view composers, and existing design-system or component libraries are the main alternatives. If you only need reusable markup, built-in Blade components may be enough. This package adds registration, configuration, and rendering primitives, so compare that convenience against the maintenance and lock-in cost.
- How do I reduce vendor lock-in if I adopt this package?
- Keep your own thin wrapper components in front of the vendor's blocks so template call sites reference your names, not theirs. That wrapper turns a future replacement from a codebase-wide rewrite into a change confined to one directory. Also avoid letting the package's markup conventions leak into unrelated templates.
- What changed in v0.1.6 and are patch releases safe?
- The v0.1.6 release notes point only to CHANGELOG.md, with no diff summary, migration notes, or linked issues. That means prior patch releases should be treated as unverified for breaking changes until you review them. Pin exact versions, inspect lockfile diffs, and run your test suite before any upgrade.
- How should I test and evaluate this package before adopting it?
- Run a half-day spike in a throwaway branch: install the package, publish what it requires, and render two or three blocks inside an existing layout. Confirm the public surface, whether it owns routing, asset compilation, or storage concerns, and how much markup convention it imposes. Add a CI check that fails if the exact version constraint is loosened.
Weaver
How can I help you explore Laravel packages today?