Shared feature matrix for marketing site (externa.qiick.io), docs, and core README highlights. Use before GA messaging changes.

GA readiness · Changelog · Site: externa.qiick.io · Docs home: docs.externa.qiick.io · Core #24

Links (must stay bidirectional)

From	To
Website nav / footer	`https://docs.externa.qiick.io`
Docs callouts / README	`https://externa.qiick.io/en` (product story)
Core README Docs badge	`https://docs.externa.qiick.io`
GitHub org / Packagist	Same product name Externa + Qiick

Feature matrix (reviewed 2026-10-02)

Claim (website / README)	Documented?	Docs page
Open-source self-hosted CMS on Laravel	yes	Architecture · Installation
Admin UI for collections + typed fields	yes	Collections · Field types
Hierarchical file manager	yes	File manager · File tree model
Roles, groups, permissions (Spatie)	yes	Roles & permissions · Permissions
Public CMS API (`/api/v1`)	yes	Public CMS API
GraphQL	yes	GraphQL
HMAC outbound webhooks	yes	Outbound webhooks
Optional in-app AI (permission-gated)	yes	AI chat · AI configuration
Dashboard Overview + Health	yes	Dashboard · Pulse & Health
SQLite / MySQL / Postgres; optional Redis stack	yes	Supported databases · Minimal vs full
Headless starters (Next / Nuxt)	yes	Headless starter
Packagist `create-project`	yes	Packagist

Not claimed on website (OK): enterprise SSO marketing card (SSO is documented — SSO / OIDC — but not a homepage hero claim), Kitchen Sink as a product, Flow canvas.

Sign-off

[x] Matrix reviewed against core README Highlights + website Feature / Bento / Hero copy (externa-website src/content/messages/en.json)
[x] Docs ↔ marketing domain links present on this page and in site docsUrl / docs nav CTAs
Sign-off comment: post on core#24 when closing docs#50 (and note docs#47 / website GA if still open)

Out of policy

Do not invent homepage features that lack a docs page. Prefer “docs first, then website copy.”