ZORAWEBDESIGN SEO • WEB DESIGN • BRANDING
DE
DE Skip to documentation
CARE CMSDOCUMENTATION
Back to Care CMS

Developers

AI-assisted drafts

Connect an external design workflow while keeping the CMS module and publishing boundaries intact.

English onlyReviewed 2 November 2026
On this page

Supported workflow

Read the public module specification, give an external AI tool a fictional content brief and the allowed local image paths, and request a version 1 JSON document. In the administrator editor, use Designer: import a module draft (JSON), validate it, inspect the generated markup and review it visually before saving. The CMS does not automatically send content or credentials to an AI provider. This is not an embedded chat assistant, MCP server or unrestricted agent session.

Example instruction

text
Use the Care CMS version 1 module specification.
Return a JSON document with only the listed module types and fields.
Use fictional practice content and the local image paths I provide.
Do not invent scripts, integrations, HTML fields or new component types.
If a component is unsupported, explain that developer review is required.
Do not request credentials, private drafts, bookings or patient information.

What the AI cannot authorise

  • Publishing content without the editor's deliberate save/review workflow.
  • Installing PHP plugins or executing generated code inside the CMS.
  • Connecting a provider, changing users, escalating roles or accessing appointments.
  • Creating an undocumented component by returning a new module name.

Further development

Fine-grained agency/client module locking, visual proposal diffs, approval records and scoped provider connections are not yet implemented. Treat any new module as a development task with validation, accessible rendering, sanitisation and tests.

Something unclear? Contact me about this guide.