Judge a theme by more than its homepage. Open the real preview, move through the page types and responsive states, then check tier, setup, support, editable content, and replacement cost.
Capell themes provide worked page designs that a Laravel team can inspect, adapt, and eventually replace. Use the gallery when a real preview fits the brief; use the custom theme guide when adapting a package would create more work than starting from the site's own design.
Available themes
The preview closest to the real brief
Updating themes
No released themes are available yet
The Foundation theme and custom-theme workflow remain available. Capell will list a theme here only after its package, compatibility, screenshots, demo, and support boundary pass release review.
Scaffold the Laravel views, layouts, assets, and tokens from the theme guide, then test them against the site's real page shapes. Editors can continue working with the same content while the frontend team owns the resulting markup.
A packaged theme can still be a reference. Reuse the useful setup patterns and replace the renderers that do not fit.
Packaged and custom themes follow the same practical path: establish the content assumptions, shape the page renderers, connect the visual tokens, test real pages and responsive states, then release with a replacement plan.
Every public first-party theme is reviewed by Capell only after its exact release passes the theme delivery subset and the shared package standard.
Review covers representative pages, responsive widths, keyboard access, reduced motion, light and dark presentation, content portability, query-free public Blade, shared package behaviour and screenshot truth.
Responsive and accessible delivery
Representative page families are inspected at desktop, tablet and mobile widths with keyboard focus and reduced motion.
Automated
AI-assisted
Human sign-off
Hydrated, query-free Blade
Theme views receive complete render data and do not fall back to Eloquent, query builders or relationship loading.
Automated
AI-assisted
Screenshot and content truth
Promoted screenshots, real content handling, setup guidance and compatibility must match the release a customer installs.
AI-assisted
Human sign-off
Role scenarios
What to inspect before choosing a theme
Checks for ownership, content fit, extension points, performance, and future redesigns.
Role-based checks drawn from product capabilities and fit boundaries.
Inspect Themes from the site owner perspective
Compare the marketplace swatch with the installed theme stylesheet, then switch a token preset. The preview colours should come from the real CSS and the project should retain editable Blade and styles.
Read more
Show less
The marketplace reverse-engineers the palette straight out of the theme's stylesheet, so the colours site owners previewed cannot drift from the real thing even though the theme's settings block is empty. The evaluator can compare the generated preview with the real stylesheet without relying on a marketing mockup.
Boundary of fit: It is a structure, not a finished brand. Real design, accessibility and content work still land on teams or whoever teams hire, and site owners would not pretend otherwise.
Render a deliberately broken theme section in development and production. Development should throw for diagnosis, while production should degrade that section safely without taking down the whole page.
Read more
Show less
The demonstration should show: A broken section throws in development but degrades safely in production, and sections inherit a default contract that keeps the theme thin. Inspect the inherited Blade and Tailwind extension path rather than relying on a bespoke templating DSL.
Scope check: No-code convenience is not the goal here, and the page says so plainly. A theme is a start, so distinctive brand and the accessibility pass are still their work, not something it finishes.
Create a new page from the theme's default sections, reorder them and preview the result. The page should begin with a useful structure and allow composition from real section types rather than a blank canvas.
Read more
Show less
A credible evaluation should confirm: The theme ships a per-section renderer registry, so editors assemble a page from first-class blocks that already know their job instead of styling an empty container. A preview lets editors read the result before it is live, and small changes are theirs to make without a design ticket.
When to look elsewhere: Content that genuinely breaks the usual patterns may still call for a bespoke layout from a developer. The theme gives editors a strong default, not a design for every unusual page editors dream up.
