jahia-dev-define-content-type

To generate a Jahia CND file from natural language, you provide a plain text content type specification and the tool outputs a deployable package containing the CND definition, TypeScript types, translations, and an asset icon.

Modeling Jahia content types with the SDC pattern involves stepwise guidance from identifying component location and namespace to writing the CND, creating TypeScript types, adding translations, and deploying the package.

You create TypeScript types for Jahia content type definitions by passing a natural language spec to the modeling workflow, which automatically generates a types.ts file alongside the CND and translation assets.

Yes, you can update existing Jahia content types and mixins by providing the updated natural language specifications, which the tool converts into revised CND definitions, constraints, and link patterns.

No, you do not need to manually package Jahia definitions, translations, and icons; the workflow produces a ready-to-deploy package containing the CND, types.ts, translations, and asset icon.

Using natural language to define Jahia CND definitions limits granular control over complex syntax, as the automated generation relies on standard SDC patterns, mixins, and constraints applied to the provided spec.