AI-Ready Capell
Capell is AI-ready because its CMS foundation is already structured, permissioned, extensible, and safe to render.
AI features work best when they have trustworthy context: page records, URLs, language state, media metadata, package boundaries, workflow state, permissions, queues, cache dependencies, and a clear public output contract. Capell gives Laravel teams that foundation before an AI provider is added.
Sales Copy For Homepage Or Landing Pages
Section titled “Sales Copy For Homepage Or Landing Pages”Headline: The Laravel CMS foundation ready for AI-assisted publishing.
Subheadline: Capell gives AI features structured content, editor workflows, package extension points, and safe public output. Editors can plan, draft, translate, and improve content with review gates; developers keep Laravel models, queues, policies, tests, and deployment.
Primary CTA: Explore AI-ready Capell
Secondary CTA: Browse AI-capable packages
Feature cards:
| Feature | Copy |
|---|---|
| Core gives AI context | Pages, URLs, translations, media, settings, package state, workflows, permissions, and cache dependencies are explicit Laravel records. |
| AIOrchestrator adds the AI layer | Provider connectors, prompt orchestration, approval-aware runs, and optional package integrations live in a focused commercial package. |
| Public output stays safe | AI, authoring, model, field, selector, signed URL, and package metadata stay out of cached public HTML. |
What Core Provides
Section titled “What Core Provides”Core does not need to become an AI package to be useful for AI. It gives AI-capable packages the stable CMS context they need:
- structured sites, pages, URLs, translations, layouts, settings, and media relationships;
- multi-site and multi-language primitives;
- queue-ready publishing and cache invalidation;
- package discovery, manifests, install state, and extension contribution types;
- Filament admin surfaces, permissions, and settings boundaries;
- public frontend safety rules that keep admin and authoring state out of anonymous HTML.
That means an AI feature can ask better questions. It can understand which page is being edited, which language is active, which packages are installed, which public URLs may be affected, and where an editor review should happen.
What AIOrchestrator Adds
Section titled “What AIOrchestrator Adds”capell-app/ai-orchestrator is the commercial AI layer. It should own AI-specific dependencies and workflows instead of pushing provider clients into every free package.
AIOrchestrator is the right home for:
- provider connectors;
- prompt templates and run orchestration;
- approval-aware execution;
- AI run history and review state;
- optional integrations with packages such as Content Sections, SEO Suite, media, search, campaigns, and translation workflows.
Core stays lean. Packages opt into AI where the feature needs it.
AI-Ready Feature Areas
Section titled “AI-Ready Feature Areas”Capell is shaped for practical AI assistance across the CMS:
| Area | How Capell helps |
|---|---|
| Content planning | Page trees, package state, and existing content give planning prompts real context. |
| Draft page generation | AI can create draft structures and section suggestions without bypassing editor review. |
| SEO and discovery | Metadata, structured data, internal links, sitemaps, llms.txt, and search checks can be package-aware. |
| Translation | Language records and translation state give AI a clear place to suggest locale-specific drafts. |
| Editorial review | Workflow packages can turn AI checks into review notes before publish. |
| Campaigns | Campaign pages, CTA blocks, UTM context, and conversion goals can be generated or reviewed from structured inputs. |
| Diagnostics | Site health, broken links, package impact, and cache state can be summarised without hiding the source of truth. |
Safety And Governance
Section titled “Safety And Governance”AI assistance belongs inside admin and package workflows. Public visitors should not be able to tell that an editor, authoring package, AI run, signed admin URL, model identifier, field path, permission name, or package selector exists.
Keep these rules:
- AI-generated changes should become drafts, suggestions, review notes, or explicitly approved writes.
- Public Blade views should receive hydrated render data and must not query for AI context.
- Cached HTML must stay safe for anonymous users, signed-in non-admin users, admins, crawlers, and static exports.
- Packages should expose AI-capable Actions or extension points without forcing AI dependencies into unrelated packages.
- Provider configuration and prompt execution should be centralised in AIOrchestrator or a purpose-built integration package.
Developer Path
Section titled “Developer Path”Start with the CMS foundation:
- Read How Capell works for the page, URL, translation, and layout model.
- Read Types for how page, widget, layout, and package behaviour is shaped.
- Read Package product groups to understand where AIOrchestrator belongs commercially.
- Read Extension point API reference before exposing package capabilities.
- Keep the public HTML safety contract close when touching public rendering, cache, themes, authoring, or AI-assisted output.
The practical rule is simple: let Capell core describe the site, let AIOrchestrator coordinate AI work, and keep public output boring.