About

About CatchCMS

Learn how CatchCMS manages multilingual business websites and multiple sites, structures products and case studies, and supports delivery and maintenance through source code, themes and MCP.

CatchCMS is an enterprise website CMS. It serves businesses and development teams that need self-hosted deployment, ongoing content updates, multiple sites and multilingual content. Teams can use AI to help develop themes and use MCP to maintain website data within the connected admin account's permissions. Product pages, articles, case studies and FAQs can share structured content models.

One system for admin, themes and public pages

CatchCMS runs the admin, themes and public pages within one application. The admin uses Vue ^3.5.22. Public pages are rendered on the server with Blade. The admin is a Vue SPA available at /admin, with business APIs under /api. Frontend development uses Blade templates, HTML, CSS and the JavaScript required by the website; the admin handles site configuration and content entry.

Developers can extend business logic with PHP, then connect content to themes through CMS components and helpers. Explore the server-rendered frontend or visit the demo site to inspect actual pages.

PHP environment and deployment

The project declares PHP ^8.3, and Composer resolves dependencies against a PHP 8.3 platform configuration. It explicitly requires ext-pdo and ext-zip; ZIP is used for theme uploads and extraction. Deployment also requires checking the installed dependencies, the database and its PDO driver, and read/write access for configuration, storage and cache directories.

Set the web document root to the project's public/ directory. For Nginx, follow the deployment instructions and include nginx.rewrite so public pages and requests under /api/ and /cms/ reach the runtime. Point each domain to the deployment service and configure its site, languages and theme in the admin. See multi-site management for domain and permission arrangements.

Content models, dynamic fields and custom development

Teams can define models, fields, options and validation for products, case studies, articles and FAQs, then maintain the records in the admin. Titles, body content, SEO information and translatable fields can be maintained per language. Theme development connects those fields to the public pages. Product filters, external system synchronization and dedicated business workflows should be defined and implemented within the project scope.

Start with one product record and verify content entry, validation, language switching and public display before extending the model to a full product range. Explore content models and dynamic fields, multilingual content and custom forms.

Develop and deliver themes with AI

Give an AI coding tool your page requirements, design references and CatchCMS theme conventions. Use it to help write Blade templates, styles and CMS data calls. Check the pages and data, package the theme's version.json, templates and assets as a ZIP, then upload it to the admin for installation and version management.

Themes contain executable server-side code, so trusted administrators handle uploads and activation as deployment operations. Delivery checks should cover page scenarios, assets, language links and field display. See AI theme development and the theme package system.

MCP connection requirements and verification

A compatible AI client needs Streamable HTTP and Bearer credential support to connect to https://your-domain/api/mcp. A super administrator issues a separate MCP access token. The token follows its admin account's operation permissions and assigned sites. Read the target site, language, models and fields first, use search to discover operations and parameter schemas, then run them through execute. Read records back and check the public pages after a change.

This workflow supports authorized content, SEO, form, configuration and theme maintenance. See the MCP guide for connection, token revocation and a first task, and MCP content management for capabilities. Confirm AI client, model service and billing arrangements with the tools you use.

Evaluate deployment and licensing

Before purchasing, list site and domain counts, languages, content types, deployment plans, custom development and client delivery needs. Use real source material in a demo or test environment to verify content entry, translation and publication against your project requirements.

The current pricing and licensing page describes source code, the official theme, updates and project use. Entitlements follow the agreed license terms. Use the contact page to confirm deployment, support and delivery arrangements.