Reusable CMS modules
In CMS v2, a module is an Astro component shipped by a Caraer app. Its manifest declares the fields a content editor can configure. Modules can provide page sections, complete pages, headers, or footers.
Why integrate
Section titled “Why integrate”You can turn your website functionality into something editors can reuse. A component’s code and supported inputs remain under developer control, while editors choose content and field values through the CMS interface.
What you could build
Section titled “What you could build”Ship a vacancy listing, a branded application block, or a product-specific widget as an app module. Editors can find it in the installed app’s library and use its declared fields without editing the component’s source.
Start integrating
Section titled “Start integrating”Follow the CMS module reference for manifests, grouped fields, runtime inputs, and module publishing. Use the CLI to validate the app before deployment and preview the component with real record values.
CMS v2 modules are compiled into the website build. Installing or removing an app and promoting a pending module version can require a rebuild; publishing a package is not proof that every company’s website is already using it. Check the installed version and rendered website after promotion. Companies using CMS v1 keep its separate component contract.