Package Architecture

WebBlocks CMS is installed as the Composer package fklavyenet/webblocks-cms inside a Laravel host application. Composer owns the installed package under vendor/fklavyenet/webblocks-cms; the host owns its application code, environment and deployment.

The package supplies CMS routes, controllers, views, migrations, translations and public assets. The host supplies its own routes and application features, database connection, mail transport, scheduler and filesystem configuration. Keep host-specific code and content outside the installed package so package updates can replace CMS files safely.

Do not edit vendor/ files to customize a site. Use supported CMS settings, site/page assets and plugin extension points. See Public Assets, Plugin System and Installation.

Administration uses /webadmin. CMS public routes use fallback semantics so ordinary Laravel host routes take precedence. The optional installation-wide public mount isolates CMS content under a configured prefix. Review route constraints and existing links before changing that prefix. Coexistence describes the supported configuration and URL behavior.

Install the package through Composer and run the documented CMS setup in the host application. Updates must retain host-owned application files, environment settings and uploaded content. Follow Updates for supported update paths and Operations for backups and recovery.

Older root-managed installations have a version-specific bridge history. Use the applicable upgrade instructions rather than copying historical application-root files into a package installation.

User documentation and guides are maintained separately from the installable package. The package includes the runtime authoring inventory exposed by the Internal Content API. Use API Discovery to confirm the block types, fields and permissions available in the target installation.