umbraco-cms-content-modelling-skills

Plugin umbraco-cms-content-modelling-skills from marketplace umbraco-cms-implementation-marketplace in umbraco/Umbraco-CMS-Implementation-Skills. Commands read from the repo's manifest — 22 days ago.

Skills (14)

• umbraco-add-block

  Add one block to an Umbraco 17+ site: the content element editors fill in, an optional settings element that controls how it looks, built from settings compositions, and, for a repeater, its `...Item` child element and the Block List that holds the children. Can also place the block in an existing b

• umbraco-add-composition

  Add one single-concern composition to an Umbraco 17+ site and apply it to the document types that need it: SEO fields, sharing fields, page details, visibility and the like. The change is written as a requirements doc, approved, applied through the Umbraco Developer MCP or a manual backoffice walkth

• umbraco-add-data-folder

  Add shared content that is not a page to an Umbraco 17+ site: a data folder document type at the content root, the data item it holds (authors, categories, locations, reusable content) and the picker data type pages use to choose items, including content-driven taxonomy. The change is written as a r

• umbraco-add-data-type

  Decide whether a property in Umbraco 17+ needs a new data type or can reuse one, pick the property editor, and name and file it in the Data Types tree. The change is written as a requirements doc, approved, applied through the Umbraco Developer MCP or a manual backoffice walkthrough, and read back.

• umbraco-add-document-type

  Add the schema of one document type to an Umbraco 17+ site: name, alias, folder by role, icon, description, tabs, properties, compositions and culture, never a template. Used directly for a type visitors never land on; other skills call it for the schema of a page, data folder or site settings. Asks

• umbraco-add-element-type

  Add one element type to an Umbraco 17+ site, in one of four roles: a content element editors fill in, the `...Item` child of a repeater, a settings model built from settings compositions, or a settings composition for one style concern, named and foldered by role. The change is written as a requirem

• umbraco-add-listing-page

  Add a listing section to an Umbraco 17+ site: the listing page type, the item page type it lists, the listing's own collection view data type and the allowed-children pairing between them, with both templates, hung under the right parent. The change is written as a requirements doc, approved, applie

• umbraco-add-page

  Add one page to an Umbraco 17+ site: the document type, its template, the SEO composition it takes and the parent that allows it, plus any block, block area or data type the page needs, in one changeset with one approval. The change is written as a requirements doc, approved, applied leaves first th

• umbraco-add-site-settings

  Add the site-wide settings node to an Umbraco 17+ site: a separate `siteSettings` singleton allowed at the content root, with no template and no children, its own tabs numbered 0 to 9 (general, header, footer, social, SEO defaults, scripts), and the settings fields in them. The change is written as

• umbraco-change-document-type

  Change a document type, composition or element type that already exists on an Umbraco 17+ site: add, remove or reorder a property, make one mandatory, change its data type, rename a type or property, change allowed children or compositions, or move a type into a folder. Says which changes lose conte

• umbraco-configure-block-editor

  Configure a block editor data type in Umbraco 17+ and the property that uses it: a Block Grid for each placement where editors lay out content (approach A), or a Block List for each repeater of one kind of item (approach B). Covers allowed blocks, settings models, column spans, limits, and adding a

• umbraco-content-model-conventions

  Reference index of the conventions for modelling content in Umbraco: names and aliases, the Document Types tree, tabs, groups and sort orders, compositions, property aliases, descriptions, icons and colours, allowed children and allow-at-root, and templates. It creates nothing; it is the rule book t

• umbraco-content-requirements-documentation

  Write an Umbraco 17+ schema change as markdown content requirements documentation, get it approved, then apply it through the Umbraco Developer MCP or a manual backoffice walkthrough and verify it. Owns the requirements page format, the changeset, the status lifecycle, the six-step change workflow,

• umbraco-review-content-model

  Audit an Umbraco 17+ content model against the content-modelling conventions and report what departs from them, ranked by severity, with the reason and the skill that would fix each finding. Reads the live schema through the Umbraco Developer MCP, or a markdown requirements folder, or schema the use

Similar plugins