FAQ

Can we customize the content structure?

Configure CatchCMS content models and dynamic fields. Check stored values, translations and theme readers before changes, then use live MCP schemas to update an

Yes. CatchCMS lets teams configure content models and dynamic fields in the admin, defining fields, choices and validation rules for products, case studies, articles and FAQs. Content records store the values. Developers read those fields through the theme and implement lists, detail pages and mobile layouts. See content models and dynamic fields for real field examples and implementation steps.

Before changing a field's type, choices, meaning or required-value rules, back up existing content and translations, review stored values and where themes read those fields, then plan any data conversion and page changes. Start with one complete record and verify entry, editing and display in each language before applying the change to other records. Conversion and migration of existing materials are implemented according to the project's requirements.

For dynamic fields maintained separately by language, first enable field translation and confirm the enabled languages bound to the target site. Check that each language's values meet the current field types and rules. A missing field translation uses the base value; stored null values, empty strings, zero and false retain their actual values.

When maintaining content through MCP, use search to discover the operation's current schema, then read the target site's model and field definitions. Read the target record and save its original values before updating the specified records, fields and languages within the account's permissions. Read the result back and compare it, then check the Chinese and English public pages. Follow the MCP guide and use project enquiries to confirm modeling or theme requirements.