On this page
-
Price and access
Review the price, licence and availability before deciding what to adopt.
-
Why this suite
Understand the work these packages are intended to support together.
-
Choose your members
See the role of each package and distinguish needed capabilities from optional additions.
-
Separate integrations
Check dependencies and integrations that are outside the suite.
-
Your first launch
Follow the suggested setup order and decide what your first release needs.
-
Buying individually
Compare the suite with selecting a single member for a narrower requirement.
-
Scope and limits
Check the boundaries and the application work this suite leaves with your team.
-
Included packages
Review each package, its available captures and its own listing.
Give a client a site their editors can run
Pages composed from approved widgets, menus editors can change, one media library that flags missing alt text, and a blog when the site publishes articles. All five members are free, and so is the suite.
Start with what the job needs
Every member also has its own listing, price, and terms. Open one to check it before you buy the group.
Needed for a first site
NeededLayout Builder is the core of the suite and depends on Block Library. Navigation gives editors the menu.
-
Layout Builder
Editors rearrange pages from widgets your team has approved, in named layout areas.
-
Block Library
The reusable content blocks Layout Builder is built on. Layout Builder depends on it.
-
Navigation
Menus for each site and language that editors reorder without editing templates.
Add when the site needs them
OptionalMedia Library suits sites with many images. Blog suits sites that publish articles.
-
Media Library
Folders, search, alt text, and a media health report that lists missing alt text and unused assets.
-
Blog
Articles with publish windows, archive and tag pages, and feeds. It depends on Tags and Layout Builder.
Separate dependencies and integrations
These listings are not included in this suite. Needed dependencies must be installed with the members that require them; optional integrations can wait until the site needs them. Check each listing for its price and terms.
-
Tags
Needed
Blog depends on Tags to tag articles and build tag pages. Tags is a separate free listing.
-
HTML Cache
Needed
Blog also depends on HTML Cache. It is a separate free listing.
A sensible order for the first site
Work down the list and stop when the job is done. Later members can wait.
- Install Layout Builder, which brings Block Library, and Navigation. Build the main menu.
- Compose the home page and one repeated page type from approved widgets.
- Add Media Library when editors start adding images, then work through its media health report.
- Add Tags and Blog when the first articles are due.
Take a member on its own when
You can skip the suite. Each member is listed separately.
- The site only publishes articles. Install Blog with the Tags and Layout Builder it depends on, and leave the rest.
- You already run some of these members. Each has its own listing, so install only what is missing.
- Editors need a review step before pages go live. That is Publishing Studio, which is listed separately.
Where this suite stops
- Capell Foundation covers
- Editing a page, its history, previewing the difference between versions, and rolling back to an earlier one.
- Publishing Studio adds
- Isolated workspaces, reviewer assignment, approval, scheduled or atomic publishing, activity history, and release recovery for Capell Pages. It is a separate paid listing and is not part of this suite.
Evaluator scenarios
What to check in Editorial Foundation Suite
Switch the evaluation lens to see how different roles should assess this bundle before adopting it.
The whole content stack present on day one — what to verify
Create a site, menu, media item and publishable page immediately after setup. The complete baseline should remain owned Laravel code rather than four partially connected products.
Read more Show less
A credible evaluation should confirm: There's no subscription that can raise its price or pull the rug, because site owners own the source outright. When site owners want a change, the site’s developer edits code teams hold rather than filing a request with a vendor.
When to look elsewhere: A single landing page can skip most of this. And owning the code still means budgeting for a Laravel developer to install and maintain it, which site owners do.
What's inside this suite
Every extension in the suite, with its own screens, standalone price, and rating. Nothing here needs a second page to judge.
Layout Builder
Compose Capell pages from reusable widgets and named layout areas: edit content first, rearrange layouts when needed, and roll out reviewed bulk layout changes...
- Standalone price
- Free
- Usefulness rating
- No approved reviews yet
capell-app/layout-builder
Block Library
Reuse Capell content blocks across layouts and packages, with typed definitions, screenshots and Filament Builder fields.
- Standalone price
- Free
- Usefulness rating
- No approved reviews yet
capell-app/block-library
Navigation
Build multilingual, per-site menus visually: link pages or URLs, nest dropdowns, and render them in your theme with one tag.
- Standalone price
- Free
- Usefulness rating
- No approved reviews yet
capell-app/navigation
Media Library
Give Capell one consistent media library with reusable assets, health checks for missing alt text and unused files, and a safe migration path from Spatie Media...
- Standalone price
- Free
- Usefulness rating
- No approved reviews yet
capell-app/media-library
Blog
Publish a multilingual and multi-site Capell blog with articles, archives, tag pages, and related-article widgets, without a separate blogging stack.