Weave Code
Frontend Laravel Package
capell-app/frontend
Public rendering package for Capell CMS that resolves core page, site, language, layout, and theme records into Laravel responses. It provides frontend page routing, rendering hooks, Livewire integration, extension points for themes and add-ons, and a built-in default Blade theme fallback.
Public routing, rendering, caching boundaries, and theme integration for Capell CMS.
Frequently asked questions about Frontend
- What is capell-app/frontend used for?
- It is the public rendering package for Capell CMS. It resolves Core page, site, language, layout, and theme records into Laravel responses and provides the public page routes, frontend middleware, context resolution, and rendering actions. It also exposes the extension points themes and frontend add-ons build on, and ships a minimal built-in default Blade theme fallback.
- How do I install capell-app/frontend in a Laravel application?
- Install it with Composer using composer require capell-app/frontend, then run the package's frontend install command so routes, middleware, and assets are wired up. The package also ships after-install and upgrade commands to keep the frontend layer in sync as Capell releases change. It targets a Capell CMS install, so make sure the rest of the Capell packages and Core records are in place first.
- Do I need to install a theme before capell-app/frontend can render pages?
- No. The package owns a minimal built-in default theme fallback with navigation, content, listing, CTA, and footer views, so public pages render without any extra theme package. Richer visual themes and in-page authoring are optional add-ons layered on top of the frontend extension points.
- Which PHP and Laravel versions does capell-app/frontend support?
- The package requires PHP 8.4 and tracks the Capell release line, so check the Laravel compatibility badge on Packagist and the requirements section of the docs before upgrading. Because it builds on Laravel routing, middleware, Blade, and Livewire, confirm your Livewire version matches as well. If you are pinned to an older Laravel release, read the version constraints on Packagist rather than assuming compatibility.
- Does capell-app/frontend replace Laravel's routing and view layer?
- It does not replace Laravel routing or Blade views; it adds public page routes, frontend middleware, context resolution, and rendering actions that run inside your normal Laravel application. Existing routes in routes/web.php keep working, but watch for duplicate or conflicting route definitions if you map current CMS URLs onto the package. Treat it as a Capell rendering add-on rather than a drop-in router replacement.
- How does caching work in capell-app/frontend, and how is the cache invalidated?
- The package includes page-view and cache integration hooks plus cache invalidation registries, so caching boundaries can be applied at route and theme level. Invalidation is registered so content and theme changes can clear the affected entries, and those listeners should line up with Laravel cache tags or queue-based invalidation. Confirm how cache keys are derived (per route, site, or locale) before trusting the defaults in a distributed Redis or Memcached setup.
- Can I use capell-app/frontend with Livewire, or with an Inertia and Vue/React SPA?
- Blade and Livewire are first-class: the package ships Blade components, Livewire page integration, render hooks, frontend asset manifests, and Tailwind source aggregation. Inertia, Vue, or React SPAs are not the default rendering paradigm, so you would need to wrap or adapt the page rendering instead of expecting JSON props. If your frontend is entirely client-side rendered, assess whether the server-rendered default theme path fits at all.
- How do I customize the default theme or register my own theme views?
- The default theme is intentionally a fallback, so most projects override it by publishing or replacing its Blade views and assets, or by hooking a theme in through the frontend extension points. Richer themes and frontend add-ons are separate packages, which keeps the built-in fallback minimal and easy to reason about. Validate that theme asset manifests and Tailwind sources do not collide with your existing CSS and JavaScript bundles.
- Is capell-app/frontend production-ready, and how should I test and benchmark it before migrating?
- Test against a sandbox Capell instance: audit the package's composer.json and config for required CMS services, then benchmark route rendering with and without the package to find bottlenecks. Use the static HTML generation and public render performance reporting commands to see what gets written and cached. Before switching real traffic, exercise 404s, missing-theme fallbacks, and cache invalidation on content and theme updates, then roll out one URL section at a time.
- What are the alternatives to capell-app/frontend, and when should I skip it?
- If you are not running Capell CMS, the package has little standalone value because it resolves Capell Core page, site, language, layout, and theme records and assumes those services exist. Alternatives are typically a full Laravel CMS such as Statamic or a custom Filament or Nova-backed build, or a thin frontend layer you write yourself on Laravel routing and Blade. Even inside a Capell install, skip it if you only need the editor UI, settings pages, or admin dashboards, since those belong to the Admin surfaces.
Weaver
How can I help you explore Laravel packages today?