Weave Code
Block Library Laravel Package
capell-app/block-library
Reusable content blocks for Capell with typed definitions, screenshots, and Filament Builder blocks. Ships admin and frontend surfaces, including hero, features, pricing, FAQ, and more for consistent content across packages.
Block Library (capell-app/block-library) adds reusable, typed content blocks to Capell with screenshots, Filament Builder blocks, and Blade frontend views. It helps developers ship consistent foundation blocks without pushing behaviour into core or application code.
Admins get package-owned management surfaces, while frontend users see package-owned block output.
- Typed block definitions with variants, settings, compatibility, and accessibility contracts
- Filament Builder blocks including Hero, Features, Pricing, FAQ, Accordion, and more
- Reusable Blade views for catalog and frontend rendering
- Admin management for block registry, editor forms, and asset settings
- Health checks and actions for validating and resolving block catalogs
Frequently asked questions about Block Library
- What is capell-app/block-library and what does it add to a Laravel application?
- capell-app/block-library is a Capell Foundation companion package that provides reusable, typed content-block primitives for Capell content packages. It ships Filament Builder blocks such as hero, features, pricing, FAQ, accordion, call to action, comparison, counter, divider, logos, and content. It also adds package-owned admin management surfaces and frontend Blade rendering. Treat it as a content-model dependency for Capell, not as a general-purpose Laravel utility.
- How do I install capell-app/block-library in a Laravel project?
- Install it with Composer as capell-app/block-library, then register the Capell\BlockLibrary\Providers\BlockLibraryServiceProvider according to Capell package conventions. Publish any package config or migrations if the release provides them, and wire the block definitions into the Capell page builder. Confirm first that your application already uses Laravel, Filament, and Capell core, because this package is designed for that stack.
- Which Laravel, PHP, Filament, and Capell versions does block-library support?
- The authoritative answer is the version constraints in the package's composer.json, so check those against your runtime before installing or upgrading. The v1.0.48 release is documented only with a changelog link, so do not assume its platform floors are unchanged from earlier patches. Pin an exact patch in composer.json and flag any PHP, Laravel, Filament, or Capell constraint changes for your platform owner.
- What content blocks ship with capell-app/block-library?
- The package includes Filament Builder blocks for hero, features, pricing, FAQ, accordion, call to action, comparison, counter, divider, logos, content, and additional catalog blocks. Each block has typed definitions and supporting data objects, with screenshots and admin management screens. Frontend rendering is provided through package Blade views under the blocks catalog namespace.
- Does capell-app/block-library require Filament, or can I use it standalone for block rendering?
- It assumes Laravel, Filament, and Capell core, and it is built primarily for Capell's admin authoring experience. The README describes it as a Capell Foundation package that extends admin, frontend, and shared surfaces. If you are building a bespoke CMS and only want block rendering, this package brings limited value and meaningful coupling. It is a good fit when you are already committed to Capell and Filament as your admin layer.
- Is capell-app/block-library v1.0.48 safe to upgrade to?
- v1.0.48 ships with a changelog link and no described fixes, migration notes, or deprecations, so it should be treated as an unassessed change until reviewed. A patch bump in a package that defines persisted content structure is not automatically low risk, because block schema, validation, or view changes can alter rendered output. Read the v1.0.47 to v1.0.48 diff and classify it as security, bugfix, feature, or metadata only before upgrading. Deploy to staging and run a render-comparison pass on representative pages.
- Does installing block-library change my database schema or require migrations?
- The README describes Block Library as an Available, No schema impact Capell package, which suggests it does not introduce core database schema changes. Even so, review each release for changes to block schema, stored JSON shape, migrations, or validation rules before upgrading. If a release does touch stored block data, confirm a rollback path for existing page content and avoid combining a bulk content migration with a version bump.
- How do I customize or override the Blade views for hero, features, pricing, and FAQ blocks?
- The package provides Blade views under packages/block-library/resources/views/blocks/catalog, including catalog blocks such as accordion and others. Follow Capell's publishing and view-override conventions rather than editing vendor files directly, so upgrades remain manageable. Treat block markup changes as a content-governance decision, and validate rendered output on staging before production. Snapshot high-traffic pages before and after any view override or package upgrade.
- How should I test block rendering and avoid breaking existing pages when upgrading block-library?
- Snapshot a representative sample of high-traffic pages before the upgrade, then compare rendered output after deploying to staging. Exercise the editor experience as well as the public frontend, because block settings and templates can affect both. Classify any differences as expected or regressions, and check whether stored block JSON or validation behaviour changed. Keep the upgrade separate from content migrations so failures are easier to isolate and roll back.
- What are the alternatives to capell-app/block-library for reusable content blocks in Laravel?
- If you are already on Capell, block-library is the foundation option for reusable typed blocks and Filament Builder integration, while the main alternative is defining your own block catalog inside Capell. If you are not on Capell, you would be comparing it with building custom Filament Builder blocks or using a different page-builder approach in a bespoke CMS. The package is not positioned as a standalone block-rendering library, so evaluate alternatives against your admin stack and content-governance needs. Also consider vendor support commitment and release cadence when choosing a small-vendor content dependency.
Weaver
How can I help you explore Laravel packages today?