Skip to main content
Capell home
Live demo

We use cookies for essential features and optional analytics.

Manage cookie preferences

Choose which optional cookies Capell may use.

Essential
Always on

Required for Capell to work — login, security, page rendering.

Analytics

Anonymous usage telemetry to improve editor performance.

Marketing

Personalization for the Capell marketing site.

Cookie policy

What's New is the short, readable account of shipped Capell work. It adds audience and action context to the exact version history kept in the changelog.

Each entry answers

  • What became available?
  • Who is affected?
  • Is any upgrade, migration, package review, or documentation change needed?
  • Where is the complete release detail?

Ideas and unfinished work belong on the roadmap. Experience from a named contributor belongs in Field Notes.

What's New

What shipped, in plain language.

Read the notable changes with dates, affected roles, and a link to the complete release record.

Read the full changelog Follow occasional updates
A dated Capell release card with affected roles, upgrade action, and changelog link.
Capell updates

Get the useful release notes by email.

An occasional digest of shipped changes, upgrade checks, and Field Notes. There is no fixed send schedule.

Release Featured

Capell 1.0.2 foundation released

Core, Admin, Frontend, Installer, and Marketplace now ship as one lockstep compatibility release.

Capell Release Foundation

Capell 1.0.2 publishes Core, Admin, Frontend, Installer, and Marketplace at one shared version. Their internal Composer requirements now follow that release version, so a project resolves a tested foundation set instead of mixing package generations.

Improvement

Fresh Capell installation path verified

The public 1.0.2 packages now complete installation, asset setup, health checks, and first-page delivery in a clean Laravel application.

Installer Laravel Verification

The Capell 1.0.2 installer completes package discovery and lifecycle work in fresh processes, builds the frontend assets, and performs its final health check against the completed application. Two independent Laravel 13 installations resolved the public tags and returned the homepage and admin login successfully.

Fix

Filament panel setup now includes the Capell theme entrypoint

New Capell admin panels now scaffold the theme file expected by the generated Vite configuration.

Admin Filament Vite

Creating a Capell Filament panel now writes the matching admin theme entrypoint before the first frontend build. The generated Vite inputs and the application filesystem therefore agree on a fresh installation.

Take the action the release calls for

Most updates do not require every reader to do the same thing. Maintainers may need an upgrade check, editors may need a workflow note, and buyers may only need to know that a package is now ready to inspect.

Use the linked record that owns the detail instead of treating a product highlight as installation guidance or a promise about future work.

Check the exact version Use the changelog for version numbers, fixes, compatibility notes, and the complete release sequence. Open the changelog
Inspect the listing before adoption When a package ships, check its current maturity, compatibility, install impact, support, and access terms on the marketplace listing. Browse package listings
Prepare the version change If the release affects an active application, review compatibility, stage the change, run the relevant checks, and keep a recovery path ready. Plan the upgrade
Keep future work separate A roadmap item can be open, planned, or in progress without being available. Depend on the shipped record when planning a live project. Check roadmap status
Loading footer