CMS Framework - v2.3.0

Added in 2.3.0.

The CMS Framework ships five AI-powered content-authoring agents built on top of the artisanpack-ui/ai foundation. Each agent maps to a feature key, validates its own input and output, and is auto-discovered by the AI package's FeatureRegistry at boot — hosts get the surfaces for free once the AI package is installed.

Feature keys

Every agent honors the toggle in artisanpack.ai.features.<key>.enabled. When the toggle is off, the agent throws FeatureDisabledException before any model call.

The canonical list is exposed as CMSFrameworkServiceProvider::AI_FEATURE_KEYS — the Livewire component, the REST controller, and any host bundle wiring read from there so a future 6th feature only lands in one place.

Installation

The AI foundation is a soft dependency, declared in composer.json under suggest and require-dev. To unlock the AI features in a host application:

composer require artisanpack-ui/ai:^1.0

Without it, aiFeatures() returns and the AI Livewire component + REST routes stay unregistered — the framework still boots normally.

Configure credentials on the AI package side. See the AI package's Configuration guide for details.

Trigger surfaces

The same five agents are reachable through two independent transports, so the AI features work uniformly across Livewire, React, and Vue front-ends.

Livewire component

ArtisanPackUI\CMSFramework\Livewire\Ai\AiTools, registered as ap-cms-ai-tools:

<livewire:ap-cms-ai-tools />

The component holds no state — it's a transport. Front-end code dispatches browser events; the component runs the agent and dispatches a status event back:

Livewire.dispatch('ap-cms-ai:suggest-post-titles', {
    content: draft.body,
    tone: 'authoritative',
    count: 5,
});

Livewire.on('ap-cms-ai:cms.post_title:success', ({ output }) => {
    // output.titles → [{ title, rationale }, ...]
});

Status suffixes: success, disabled, missing-credentials, invalid-input, error.

REST endpoints

Mounted at /api/v1/cms/ai/* and protected by auth:sanctum so React and Vue SPAs with bearer tokens can hit them directly:

Success responses: 200 { feature, output }. Error envelopes:

Because the transport is plain HTTP, @artisanpack-ui/react and @artisanpack-ui/vue do NOT need to know anything about CMS AI features — hosts add a new capability entirely on the backend.

Agent contracts

Each agent validates input and shapes output; front-ends and controllers can trust the returned envelope.

cms.post_title — PostTitleSuggestionAgent

Input

Output

[
    'titles' => [
        [ 'title' => string, 'rationale' => string ],
        // ...
    ],
]

Titles longer than 80 characters are clamped; entries with an empty title or rationale are dropped.

cms.excerpt — ExcerptGenerationAgent

Input

Output

[
    'excerpt'    => string,
    'char_count' => int, // recomputed from returned excerpt, not model-reported
]

cms.suggest_tags — TagSuggestionAgent

Input

Output

[
    'selected' => [
        [ 'tag' => string, 'confidence' => float ], // 0.0-1.0
        // ...
    ],
    // Only present when allow_new is true:
    'suggested_new' => string[],
]

Tags returned by the model that are not in available_tags are silently dropped. Confidence values are clamped to [0, 1]. Whitespace on model-returned tags is trimmed before the allow-list lookup.

cms.suggest_category — CategorySuggestionAgent

Input

Output

[
    'selected'   => string, // slash-delimited path or '' if no fit
    'confidence' => float,  // 0.0-1.0, forced to 0 when selected is ''
    'rationale'  => string,
]

Nodes whose name contains a / are rejected during path collection — they would collide with real parent/child paths and make the model pick ambiguous.

cms.suggest_slug — SlugSuggestionAgent

Input

Output

[
    'slug'       => string, // sanitized kebab-case, <= max_chars
    'alternates' => string[], // 0-2 backup slugs for uniqueness collisions
]

Slug sanitization delegates to Illuminate\Support\Str::slug() — non-ASCII characters are transliterated (café → cafe), and the length cap is applied on a hyphen boundary so words aren't truncated mid-token.

Uniqueness against your existing slugs is intentionally NOT part of the agent's contract — callers enforce uniqueness (Eloquent lookup, DB constraint, ...) using the returned slug.

Extending

Override an agent

Bind a subclass in the container to replace an agent globally:

use ArtisanPackUI\CMSFramework\Ai\Agents\SlugSuggestionAgent;
use App\Ai\Agents\OpusSlugSuggestionAgent;

$this->app->bind(SlugSuggestionAgent::class, OpusSlugSuggestionAgent::class);

SlugSuggestionAgent::for(…) resolves through the container, so the subclass takes over on every consumer without touching the trigger surfaces.

Register additional CMS AI features

Add a aiFeatures() method to your own service provider — the AI foundation walks every loaded provider and merges the results:

public function aiFeatures(): array
{
    return [
        'myapp.suggest_seo_meta' => [
            'agent'   => \App\Ai\Agents\SeoMetaAgent::class,
            'package' => 'myapp/seo',
        ],
    ];
}

Then hook it into AiTools / AiController (or your own controller) the same way the five built-ins do.

Related

• artisanpack-ui/ai documentation
• artisanpack-ui/visual-editor AI features — cross-cutting ai.alt_text, ai.content_rewrite, and the visual-editor-owned visual_editor.* agents.