Weave Code
Theme Agency Laravel Package
capell-app/theme-agency
An agency-style frontend theme for the Capell CMS, bundling ready-made Blade views, layouts, and design assets for building polished client or agency websites. Install it to scaffold a professional marketing site quickly using Capell's theme system and customization options.
A bold, motion-led theme for creative studios and marketing agencies
Frequently asked questions about Theme Agency
- What is capell-app/theme-agency and what does it do?
- It is a frontend theme package for the Capell CMS, which runs on Laravel, bundling Blade views, layouts, and design assets aimed at creative studios and marketing agencies. It plugs into Capell's theme system so you can scaffold a polished marketing site instead of writing every view from scratch. It is a presentation-layer package, not a CMS, admin panel, or page builder on its own.
- How do I install capell-app/theme-agency in a Laravel app?
- Install it with Composer, typically composer require capell-app/theme-agency, and pin an explicit version such as 1.0.50 rather than a floating constraint. The package is expected to auto-discover its service provider and expose publishable config, views, and assets through vendor:publish. Verify the exact publish tags and provider behavior in the README or composer.json before depending on them.
- Which Laravel and PHP versions does theme-agency support?
- The declared constraints live in the package's composer.json, and the technical review notes they were not verified, so read the require block for the laravel/framework and php ranges before adopting. Test against your current Laravel major plus one adjacent major and your minimum PHP version. Do not infer support from the 1.x version number alone.
- Does theme-agency require the Capell CMS, or can I use it in a plain Laravel app?
- It is described as an agency-style frontend theme for the Capell CMS, so it is built around Capell's theme resolution and view registration rather than vanilla Laravel view paths. Using it without Capell would mean reproducing that theme-resolution contract yourself. Treat it as a Capell-first package unless the source shows a plain Laravel fallback.
- How do I customize the theme's Blade views and design assets?
- Expect to publish the package's views and assets into your application, then override the published copies rather than editing vendor files directly. Keep your overrides in your own theme directory or resources/views so a Composer update does not wipe them. Watch for vendor:publish --force overwriting your customized files during reinstall.
- Is theme-agency safe to use in production?
- It is a 1.x package published by a single small GitHub organization, with no documented security disclosure process and no release notes for the reviewed version range, so treat adoption as a calculated risk. Pin the exact version, commit composer.lock, and wrap its entry points in a thin internal adapter so removal is a one-file change. Re-check the constraints and changelog before every upgrade.
- Why are there no release notes between v1.0.45 and v1.0.50?
- The only artifact for v1.0.50 is a compare link spanning the previous five patch releases, so the actual changes are not described anywhere. To reconstruct them, install each tag in a scratch project and diff the vendor tree, timeboxed to a couple of hours. The absence of notes is a finding in itself, not evidence that nothing changed.
- Does theme-agency add database migrations or hurt performance?
- A theming package should not ship migrations, but confirm by inspecting the package contents first, because a migration turns a simple deploy into a release with a data step. Also check whether theme resolution is cached or resolved per request and whether it touches the filesystem on the hot path. If resolution happens per request, cache the resolved theme in your own layer.
- Will theme-agency conflict with my existing Blade views or frontend build?
- Blade view names can collide with your resources/views entries, especially generic names like layouts.app, so test on a throwaway branch against a single low-traffic theme before rolling it out. Confirm the package does not require a specific Vite or Tailwind version that clashes with your toolchain. Keep your own view namespace as the override point for anything you need to change.
- What are the alternatives if theme-agency is abandoned?
- Because it only handles the presentation layer, an in-house replacement is realistic: a theme directory with Blade layouts, published assets, and a small theme resolver behind your own contract. Before adopting, check who else depends on it and whether the license permits your distribution model, whether SaaS or redistributed client builds. The safe exit ramp is the pinned version plus a thin adapter class around every package entry point you use.
Weaver
How can I help you explore Laravel packages today?