.cspell-project-words.txt

+behaviours
+ctahref
+hotwire
+htmx
 canonicalizer
 canonicalized
+coloris
+contextful
 corge
 criticals
+daisyui
+dsfr
 endsandbox
+favourite
 getattr
 grault
 kint
 maxcontains
 mincontains
+pdureau
 proptype
+pymdownx
 recursivity
 sameas
 sdc's
+spottable
 subcomponent
 toolset
+uswds

.gitlab-ci.yml

@@ -28,7 +28,7 @@ include:
     - vendor/bin/phpmd --version
     - vendor/bin/phpmd $_WEB_ROOT/modules/custom/$CI_PROJECT_NAME gitlab $_WEB_ROOT/modules/custom/$CI_PROJECT_NAME/.phpmd.xml --exclude 'tests/*,**/tests/*' > phpmd-quality-report.json || true
     - vendor/bin/phpmd $_WEB_ROOT/modules/custom/$CI_PROJECT_NAME text $_WEB_ROOT/modules/custom/$CI_PROJECT_NAME/.phpmd.xml --exclude 'tests/*,**/tests/*'
-  allow_failure: true
+  allow_failure: false
   artifacts:
     expose_as: phpmd
     when: always
@@ -39,5 +39,69 @@ include:
     paths:
       - phpmd-quality-report.json
 
+.twig-lint-base:
+  stage: validate
+  before_script:
+    - composer require --dev vincentlanglet/twig-cs-fixer
+  script:
+    - vendor/bin/twig-cs-fixer lint --config=$_WEB_ROOT/modules/custom/$CI_PROJECT_NAME/.twig-cs-fixer.php $_WEB_ROOT/modules/custom/$CI_PROJECT_NAME
+  rules:
+    - changes:
+        - "**/*.twig"
+    - if: '$CI_PIPELINE_SOURCE == "push"'
+  allow_failure: false
+  artifacts:
+    expose_as: twig-lint
+    when: always
+    expire_in: 6 mos
+    reports:
+      codequality: twig-lint-quality-report.xml
+    name: artifacts-$CI_PIPELINE_ID-$CI_JOB_NAME_SLUG
+    paths:
+      - twig-lint-quality-report.xml
+
+.prettier-lint-base:
+  stage: validate
+  script:
+    - echo "Prettier version $(${CI_PROJECT_DIR}/${_WEB_ROOT}/core/node_modules/.bin/prettier --version)"
+    - ${CI_PROJECT_DIR}/${_WEB_ROOT}/core/node_modules/.bin/prettier --check ${CI_PROJECT_DIR}/docs/
+  rules:
+    - changes:
+        - "docs/*.md"
+        - "docs/**/*.md"
+  allow_failure: false
+  artifacts:
+    expose_as: prettier-lint
+    when: always
+    expire_in: 6 mos
+    reports:
+      codequality: prettier-lint-quality-report.xml
+    name: artifacts-$CI_PIPELINE_ID-$CI_JOB_NAME_SLUG
+    paths:
+      - prettier-lint-quality-report.xml
+
 phpmd:
   extends: .phpmd-base
+twig-lint:
+  extends: .twig-lint-base
+prettier-lint:
+  extends: .prettier-lint-base
+composer-lint:
+  allow_failure: false
+cspell:
+  allow_failure: false
+  variables:
+    _CSPELL_IGNORE_PATHS: '**/tests/fixtures/config/*.yml, **/tests/fixtures/*.yml'
+eslint:
+  allow_failure: false
+phpcs:
+  allow_failure: false
+phpstan:
+  allow_failure: false
+phpunit:
+  allow_failure: false
+  variables:
+    _PHPUNIT_EXTRA: ''
+
+
+

.twig-cs-fixer.php

+<?php
+
+$ruleset = new TwigCsFixer\Ruleset\Ruleset();
+
+// Add a default standard.
+$ruleset->addStandard(new TwigCsFixer\Standard\TwigCsFixer());
+
+// Add some specific rules.
+$ruleset->addRule(new TwigCsFixer\Rules\File\FileExtensionRule());
+
+$config = new TwigCsFixer\Config\Config();
+$config->setRuleset($ruleset);
+
+return $config;

README.md

@@ -8,28 +8,27 @@ Components are reusable, nestable, guided by clear standards, and can be assembl
 
 The UI Patterns project provides 3 "toolset" modules:
 
-- **UI Patterns**: the main module, based on Drupal Core SDC API, with additional powerful API and quality-of-life improvements
-- **UI Patterns Library**: generates a pattern library page available at `/patterns`
+- **UI Patterns**: the main module, based on Drupal Core SDC API, with some extra features and quality-of-life improvements
+- **UI Patterns Library**: generates a pattern library page available at `/admin/appearance/ui/components`
   to be used as documentation for content editors or as a showcase for business. Use this module if you don't plan to
   use more advanced component library systems such as Storybook, PatternLab or Fractal.
-  [Learn more](https://www.drupal.org/docs/contributed-modules/ui-patterns/define-your-patterns)
 - **UI Patterns Legacy**: Load your UI Patterns 1.x components inside UI Patterns 2.x
 
 4 "integration" modules:
 
 - **UI Patterns Layouts**: allows to use components as layouts. This allows patterns to be used with Layout Builder,
-  [Display Suite](https://www.drupal.org/project/ds) or [Panels](https://www.drupal.org/project/panels)
-  out of the box. [Learn more](https://www.drupal.org/docs/contributed-modules/ui-patterns/use-patterns-as-layouts)
+  [Display Suite](https://www.drupal.org/project/ds) or [Layout Paragraphs](https://www.drupal.org/project/layout_paragraphs)
+  out of the box.
 - **UI Patterns Blocks**: allows to use components as Blocks plugins.
 - **UI Patterns Field Formatters**: allows to use components as Field Formatters plugins.
 - **UI Patterns Views**: allows to use components as Views styles or Views rows plugins.
-  [Learn more](https://www.drupal.org/docs/contributed-modules/ui-patterns/use-patterns-with-views)
-
-1 "devel" module:
-
-- **UI Patterns Devel**: provide some tools to help developers working with Component. Currently a Twig static
-  validator to detect errors and help follow good practices for UI Patterns.
 
 ## Documentation
 
 Documentation is available [here](https://www.drupal.org/docs/contributed-modules/ui-patterns).
+
+## Testing
+
+### Performance testing
+UI Patterns uses [Gander](https://www.drupal.org/docs/develop/automated-testing/performance-tests) to automate performance measuring.
+We suggest to use ddev with the [Gander Addon](https://github.com/tag1consulting/ddev-gander) to view render results. 

config/schema/ui_patterns.schema.yml

+ui_patterns_component:
+  type: mapping
+  label: 'Component configuration'
+  constraints:
+    FullyValidatable: ~
+  mapping:
+    component_id:
+      type: string
+      label: 'Component ID'
+      nullable: true
+    variant_id:
+      type: ui_patterns_prop
+      nullable: true
+      label: 'Variant ID'
+    # @todo make a mechanism that will check the props keys depending on the
+    # the component ID. And so maybe convert into mapping.
+    props:
+      type: sequence
+      label: 'Props'
+      sequence:
+        type: ui_patterns_prop
+        label: 'Prop'
+    # @todo make a mechanism that will check the slots keys depending on the
+    # the component ID. And so maybe convert into mapping.
+    slots:
+      type: sequence
+      label: 'Slots'
+      sequence:
+        type: ui_patterns_slot
+        label: 'Slot'
+
+ui_patterns_prop:
+  type: mapping
+  label: 'Prop'
+  mapping:
+    source_id:
+      type: string
+      label: 'Prop source ID'
+    source:
+      type: ui_patterns_source.[%parent.source_id]
+      label: 'Prop source configuration'
+
+ui_patterns_slot:
+  type: mapping
+  label: 'Slot'
+  mapping:
+    sources:
+      type: sequence
+      label: 'Slot sources'
+      sequence:
+        type: ui_patterns_slot_source
+        label: 'Slot source'
+
+ui_patterns_slot_source:
+  type: mapping
+  label: 'Slot source'
+  mapping:
+    source_id:
+      type: string
+      label: 'Slot source ID'
+    source:
+      type: ui_patterns_source.[%parent.source_id]
+      label: 'Slot source configuration'
+    _weight:
+      type: string
+      label: 'Slot source weight'

config/schema/ui_patterns.sources.schema.yml

+ui_patterns_source.checkbox:
+  type: mapping
+  label: 'Source: checkbox'
+  mapping:
+    value:
+      type: boolean
+      label: 'Checkbox value'
+
+ui_patterns_source.attribute:
+  type: mapping
+  label: 'Source: attribute'
+  mapping:
+    value:
+      type: boolean
+      label: 'Attribute value'
+
+ui_patterns_source.path:
+  type: mapping
+  label: 'Source: Path'
+  mapping:
+    value:
+      type: path
+      label: 'Path value'
+
+ui_patterns_source.url:
+  type: mapping
+  label: 'Source: URL'
+  mapping:
+    value:
+      type: uri
+      label: 'URL value'
+
+ui_patterns_source.textfield:
+  type: mapping
+  label: 'Source: Textfield'
+  mapping:
+    value:
+      type: string
+      label: 'String value'
+
+ui_patterns_source.select:
+  type: mapping
+  label: 'Source: Select'
+  mapping:
+    value:
+      type: string
+      label: 'Select value'
+
+ui_patterns_source.selects:
+  type: mapping
+  label: 'Source: Selects'
+  mapping:
+    value:
+      type: sequence
+      label: 'Selects value'
+      sequence:
+        type: string
+        label: 'Values'
+
+ui_patterns_source.attributes:
+  type: mapping
+  label: 'Source: Attributes'
+  mapping:
+    value:
+      type: string
+      label: 'Attribute value'
+
+ui_patterns_source.attributes_class:
+  type: mapping
+  label: 'Source: Attributes Class'
+  mapping:
+    value:
+      type: string
+      label: 'Attributes Class value'
+
+ui_patterns_source.list_textarea:
+  type: mapping
+  label: 'Source: List Text area'
+  mapping:
+    value:
+      type: string
+      label: 'Source List Text area values'
+
+ui_patterns_source.number:
+  type: mapping
+  label: 'Source: Number'
+  mapping:
+    value:
+      type: string
+      label: 'Number value'
+
+ui_patterns_source.wysiwyg:
+  type: mapping
+  label: 'Source: WYSIWYG'
+  mapping:
+    value:
+      type: text_format
+      label: 'WYSIWYG value'
+
+ui_patterns_source.component:
+  type: mapping
+  label: 'Source: Component'
+  mapping:
+    component:
+      type: ui_patterns_component
+
+ui_patterns_source.checkboxes:
+  type: mapping
+  label: 'Source: Checkboxes'
+  mapping:
+    value:
+      type: sequence
+      label: 'Selects value'
+      sequence:
+        type: string
+        label: 'Select Item Value'
+
+ui_patterns_source.entity_link:
+  type: mapping
+  label: 'Source: Entity Link'
+  mapping:
+    template:
+      type: string
+
+ui_patterns_source.menu:
+  type: mapping
+  label: 'Source: Menu'
+  mapping:
+    menu:
+      type: string
+      label: 'Menu Name'
+    level:
+      type: string
+      label: 'Entry Level'
+    depth:
+      type: string
+      label: 'Menu depth'
+
+ui_patterns_source.token:
+  type: mapping
+  label: 'Source: Token'
+  mapping:
+    value:
+      type: string
+      label: 'Token value'
+
+ui_patterns_source.field_property:*:*:*:
+  type: mapping
+  label: 'Source: Field Property'
+  mapping:
+    type:
+      type: string
+      label: 'Field Property type'
+
+# block uses dynamic subkeys not under a specific key.
+# The configuration looks like:
+# plugin_id: block_id
+# block_id:
+#  config_1: #
+# I cant find a solution to handle this correct. Sequences would work
+# if the the block_id key would be under an extra key. Something like config.block_id
+ui_patterns_source.block:
+  type: ignore
+
+# Same here ui_patterns_source.block
+ui_patterns_source.entity_field:
+  type: ignore
+
+# This source uses a dynamic subkey.
+# The configuration looks like:
+# source_id: entity_reference
+# source:
+#   derivable_context: 'context:id'
+#   'context:id':
+ui_patterns_source.entity_reference:
+  type: ignore

docs/1-users/0-component-form.md

+# Component form
+
+The biggest feature of UI Patterns is the generation of forms from the components definition:
+
+| From component definition....     | ... to component form   |
+| --------------------------------- | ----------------------- |
+| ![](images/bs-alert-example.webp) | ![](images/form-1.webp) |
+
+Those forms will be shown everywhere a component is used:
+
+- [as blocks](1-as-block.md)
+- [as layouts](1-as-block.md)
+- [in field formatters](1-as-block.md)
+- [in views](1-as-block.md)
+- ...
+
+## Data sources
+
+Values are taken from sources:
+
+- "Widgets": simple form elements storing directly the data filled by the user. For example, a `textfield` for a string or a `checkbox` for a boolean.
+- Sources retrieving data from Drupal API: they can be context agnostic (ex: a menu for links) or context specific (ex: the title field for a string)
+- Context switchers: They don't retrieve data but they give access to other data sources. For example, the author fields from an article content.
+
+If there is only a single source available, the source form is directly displayed:
+
+![](images/sources-1.webp)
+
+If there are at least 2, a source selector is shown:
+
+![](images/sources-2.webp)
+
+Some sources doesn't have a form, selecting the source is enough:
+
+![](images/sources-3.webp)
+
+## Context
+
+Sometimes sources require another object in order to retrieve the data. This is known as context.
+
+Some source doesn't need a context and are site wide, for example:
+
+- All “widgets” which are source plugins with only direct input: Textfield, Select, Checkbox…
+- List of all menus
+- The breadcrumb
+- …
+
+But some of them will need context. Examples:
+
+| Context         | Source              | Prop type | Description                                |
+| --------------- | ------------------- | --------- | ------------------------------------------ |
+| Content entity  | Data from a field   |           | Switch to a Field context.                 |
+| Content entity  | Entity link         | URL       |
+| Content entity  | Referenced entities |           | Switch to an other Content entity context. |
+| Field           | Field formatter     | Slot      |
+| Field           | Field label         | String    |
+| Field           | Field prop : \*     | (many)    |
+| Reference field | Field prop: entity  |           | Switch to a Content entity context.        |
+| View            | View title          | String    |
+| View            | View rows           | Slot      |
+| View row        | View title          | String    |
+| View row        | View field          | Slot      |
+
+## Variant selector
+
+Some components have variants, a list of different "look" of the component. Variants doesn't change the model or the meaning of the component, only the look.
+
+![](images/variant-1.webp)
+
+## Slots
+
+SDC components are made of slots & props:
+
+- **Slots**: “areas” for free renderables only, like Drupal blocks or other SDC components for example.
+- **Props**: strictly typed data only, for some UI logic in the template.
+
+You can draw the slots areas in a component screenshot:
+
+![](images/slots-vs-props.webp)
+
+For each slots, its is possible to add one or many sources:
+
+![](images/slot-1.webp)
+
+For example:
+
+- "Component": nest another SDC component in the slot.
+- "Block": add a Drupal block plugin
+- "Wysiwyg": a simple text editor, using the text formats defined in your site.
+
+Other modules can add other sources. For example, "Icon" in this screenshot is brought by https://www.drupal.org/project/ui_icons
+
+Once a source is added, it can be configured and we can add more because the selector is still present:
+
+![](images/slot-2.webp)
+
+Sources can be reordered inside a slot.
+
+Using the "Component" source, we have access to the embedded component slots and we can nest data:
+
+![](images/slot-3.webp)
+
+## Props
+
+A bit like the form for slots with 2 main differences:
+
+- We don’t allow multiple items, so we can replace the source but not add some (and of course no reordering)
+- The default source form is already loaded.
+
+![](images/props-1.webp)
+
+The available sources are varying according to both:
+
+- the prop type. Each prop as a type, which is related to its JSON schema typing, but not exactly the same. You can check what type has a prop in the [component library](../2-authors/1-stories-and-library.md). A prop without a type is not displayed in the form.
+- the context, as explained before.

docs/1-users/1-as-block.md

+# Using a component as a Drupal block
+
+You need to activate `ui_patterns_blocks` sub-module.
+
+Blocks are boxes of content rendered into an area, or region, of a web page (such as "User Login" or "Who's online") that can be displayed in regions (such as footer or sidebar) on your page or content display.
+
+## In Block Layout (`/admin/structure/block`)
+
+Every UI component is a Drupal block plugin, available in the "Place block" modal:
+
+![](images/block-1.webp)
+
+For example, to assign any component in the Header region, click on "Place Block" button and choose the component to be placed in this particular region.
+
+The component is configurable as an usual block plugin, with the [Component form](3.0-component-form.md) alongside the block title, the visibility settings and the block placement:
+
+![](images/block-2.webp)
+
+### Contextual data sources
+
+There is no specific context here. Only the generic data sources are available.
+
+## In Layout Builder
+
+Drupal's Layout Builder allows content editors and site builders to create visual layouts for displaying content. Users can customize how content is arranged on a single page, across types of content, or even create custom landing pages with an easy to use drag-and-drop interface.
+
+The Layout Builder provides the ability to drag and drop site-wide blocks and content fields into regions within a given layout.
+
+![](images/block-3.webp)
+
+Component props are available in the sidebar as block settings:
+
+![](images/block-4.webp)
+
+### Contextual data sources
+
+| Context        | Source              | Prop type | Description                                |
+| -------------- | ------------------- | --------- | ------------------------------------------ |
+| Content entity | Data from a field   |           | Switch to a Field context.                 |
+| Content entity | Entity link         | URL       |
+| Content entity | Referenced entities |           | Switch to an other Content entity context. |

docs/1-users/2-as-layout.md

+# Using a component as a layout
+
+You need to activate `ui_patterns_layouts` sub-module.
+
+## Layout plugins
+
+SDC components have a model quite similar to Drupal layout plugins:
+
+- Component slots are layout plugin regions
+- Component props are layout plugin settings
+
+## In Layout Builder
+
+Drupal's Layout Builder allows content editors and site builders to create visual layouts for displaying content. Users can customize how content is arranged on a single page, across types of content, or even create custom landing pages with an easy to use drag-and-drop interface.
+
+The Layout Builder provides the ability to drag and drop site-wide blocks and content fields into regions within a given layout.
+
+Each section can contain content arranged in a certain layout. Each UI component is exposed as a layout plugin:
+
+![](images/layout-1.webp)
+
+If a component has a `thumbnail.webp`, it will be shown in the layouts list:
+
+![](images/layout-3.webp)
+
+Section configuration is a [Component form](3.0-component-form.md), without the slots because slots are directly managed by Layout Builder as regions of the layout:
+
+![](images/layout-2.webp)
+
+### Contextual data sources
+
+There is no UI Patterns sources for slots here because slots are directly managed by Layout Builder as regions. So, only Drupal blocks plugins are available.
+
+| Context        | Source              | Prop type | Description                                |
+| -------------- | ------------------- | --------- | ------------------------------------------ |
+| Content entity | Data from a field   |           | Switch to a Field context.                 |
+| Content entity | Entity link         | URL       |
+| Content entity | Referenced entities |           | Switch to an other Content entity context. |

docs/1-users/3-in-field-formatter.md

+# Using a component in field formatters
+
+Field Formatters are Drupal plugins formatting the output of a content field. For example:
+
+- Date field formatted as "... time ago"
+- Date field formatted with a custom date format
+- Entity reference field formatted as label
+- Entity reference field formatted as a rendered entity
+- ...
+
+There are 2 field formatters provided by `ui_patterns_field_formatters` sub-module:
+
+- **Component per item**: Each item will be displayed as a component.
+- **Component**: Available only for multi-valued fields. The full field is displayed as a component.
+
+## In Manage Display
+
+Manage display manages the way your content is displayed on the frontend.
+
+The UI Patterns field formatters are available in the format select list, for every fields,
+
+![](images/formatter-1.webp)
+
+Once selected, the field formatters are configurable as usual field formatters, with the UI Patterns 2's [Component form](3.0-component-form.md)
+
+![](images/formatter-2.webp)
+
+### Contextual data sources
+
+| Context         | Source              | Prop type | Description                                |
+| --------------- | ------------------- | --------- | ------------------------------------------ |
+| Field           | Field formatter     | Slot      |
+| Field           | Field label         | String    |
+| Field           | Field prop: \*      | (many)    |
+| Reference field | Field prop: entity  |           | Switch to a Content entity context.        |
+| Content entity  | Data from a field   |           | Switch to a Field context.                 |
+| Content entity  | Entity link         | URL       |
+| Content entity  | Referenced entities |           | Switch to an other Content entity context. |
+
+## In Layout Builder
+
+Drupal's Layout Builder allows content editors and site builders to create visual layouts for displaying content. Users can customize how content is arranged on a single page, across types of content, or even create custom landing pages with an easy to use drag-and-drop interface.
+
+Fields are available as blocks:
+
+![](images/formatter-3.webp)
+
+Once selected, the field formatters are configurable as usual field formatters, with the UI Patterns 2's [Component form](3.0-component-form.md):
+
+![](images/formatter-4.webp)
+
+### Contextual data sources
+
+| Context         | Source              | Prop type | Description                                |
+| --------------- | ------------------- | --------- | ------------------------------------------ |
+| Field           | Field formatter     | Slot      |
+| Field           | Field label         | String    |
+| Field           | Field prop : \*     | (many)    |
+| Reference field | Field prop: entity  |           | Switch to a Content entity context.        |
+| Content entity  | Data from a field   |           | Switch to a Field context.                 |
+| Content entity  | Entity link         | URL       |
+| Content entity  | Referenced entities |           | Switch to an other Content entity context. |
+
+## In Views
+
+Drupal Views is both:
+
+- a query builder: fetch content from the database, with filters, sorts and grouping.
+- a display builder: present the results as lists, galleries, tables, maps, graphs, reports...
+
+If your display accepts fields, the field formatters are available:
+
+![](images/formatter-5.webp)
+
+Once selected, the field formatters are configurable as usual field formatters, with the UI Patterns 2's [Component form](3.0-component-form.md):
+
+![](images/formatter-6.webp)
+
+### Contextual data sources
+
+| Context         | Source              | Prop type | Description                                |
+| --------------- | ------------------- | --------- | ------------------------------------------ |
+| Field           | Field formatter     | Slot      |
+| Field           | Field label         | String    |
+| Field           | Field prop: \*      | (many)    |
+| Reference field | Field prop: entity  |           | Switch to a Content entity context.        |
+| Content entity  | Data from a field   |           | Switch to a Field context.                 |
+| Content entity  | Entity link         | URL       |
+| Content entity  | Referenced entities |           | Switch to an other Content entity context. |

docs/1-users/4-with-views.md

+# Using a component with Views
+
+Drupal Views is both:
+
+- a query builder: fetch content from the database, with filters, sorts and grouping.
+- a display builder: present the results as lists, galleries, tables, maps, graphs, reports...
+
+You need to activate `ui_patterns_views` sub-module.
+
+## View style plugin
+
+To build the display around the results:
+
+- the table and not the rows
+- the slider and not the slides
+- the map and not the points of interest
+- the mosaic and not the pictures
+
+### Steps
+
+Pick "Component" in the modal:
+
+![](images/views-1.webp)
+
+Select the component and fill the configuration form:
+
+[Component form](3.0-component-form.md)
+
+![](images/views-2.webp)
+
+### Contextual data sources
+
+| Context | Source     | Prop type | Description |
+| ------- | ---------- | --------- | ----------- |
+| View    | View title | String    |
+| View    | View rows  | Slot      |
+
+## View row plugin
+
+To build the display of each result:
+
+- the rows instead of the table
+- the sliders instead of the slides
+- the point of interests instead of the map
+- the pictures instead of the mosaic
+
+Pick "Component" in the modal:
+
+![](images/views-3.webp)
+
+Select the component and fill the configuration form:
+
+![](images/views-4.webp)
+
+### Contextual data sources
+
+| Context        | Source              | Prop type | Description                                |
+| -------------- | ------------------- | --------- | ------------------------------------------ |
+| View row       | View title          | String    |
+| View row       | View field          | Slot      |
+| Content entity | Data from a field   |           | Switch to a Field context.                 |
+| Content entity | Entity link         | URL       |
+| Content entity | Referenced entities |           | Switch to an other Content entity context. |

docs/1-users/5-presenter-templates.md

+# Using a component in Drupal templates
+
+## Presenter templates
+
+Presenter templates are standard Drupal templates that:
+
+- transform data received from Drupal
+- use Twig [include()](http://twig.sensiolabs.org/doc/function/include.html) function to include one or more components and pass the transformed data.
+- should be totally free of markup
+- use [theme suggestions](https://www.drupal.org/docs/8/theming/twig/twig-template-naming-conventions) to plug itself to data model
+
+For example, a “normal” template has markup:
+
+```twig
+{% if subtitle %}
+<h3 class="callout__subtitle">{{ subtitle }}</h3>
+{% endif %}
+```
+
+But a presenter template has only a call to a component (and sometimes a bit of logic):
+
+```twig
+{{ include('my_theme:menu', {
+  'items': items,
+  'attributes': attributes.addClass('bg-primary'),
+}, with_context=false)}}
+```
+
+Examples of presenter templates can be found on those folders:
+
+- https://git.drupalcode.org/project/ui_suite_bootstrap/-/tree/5.1.x/templates
+- https://git.drupalcode.org/project/ui_suite_daisyui/-/tree/4.0.x/templates
+- https://git.drupalcode.org/project/ui_suite_dsfr/-/tree/1.1.x/templates
+- https://git.drupalcode.org/project/ui_suite_material/-/tree/2.0.x/templates
+- https://git.drupalcode.org/project/ui_suite_uswds/-/tree/4.0.x/templates
+
+More about presenter templates:
+
+- https://www.aleksip.net/presenting-component-projects (May 2016)
+- https://www.mediacurrent.com/blog/accommodating-drupal-your-components/ (Broken link)
+
+### Don’t use presenter templates when site building is possible
+
+Presenter templates are a clever trick, however they hurt the site building because everything which is normally set in the display settings by the site builder has to be done in a Twig file by the developer.
+
+However, there are some cases when site building is not easily possible. For examples:
+
+- rendering a menu. Menu are config entities without configurable displays.
+- rendering a content entity where the configurable display has no admin UI.
+
+🚫 Don't do presenter templates when display building is available:
+
+- Node: `/admin/structure/types/manage/{bundle}/display`
+- BlockContent: `/admin/structure/block/block-content/manage/{bundle}/display`
+- Comment: `/admin/structure/comment/manage/{bundle}/display`
+- Media: `/admin/structure/media/manage/{bundle}/display`
+- Taxonomy Term: `/admin/structure/taxonomy/manage/{bundle}/overview/display`
+- User: `/admin/config/people/accounts/display`
+- Views
+
+✅ Presenter templates are OK for renderables without display building:
+
+- Page layout: `page.html.twig` and `region.html.twig`
+- Menu config entity: `menu.html.twig`
+- ...
+
+### Slots & props
+
+Most of those templates have distinct variables for data to send to slots or props.
+
+For example, in `node.html.twig`:
+
+- `node` variable has the typed data to send to props
+- `content` has the renderable data to send to slots
+
+Other example, in `user.html.twig`:
+
+- `user` variable has the typed data to send to props
+- `content` has the renderable data to send to slots
+
+## Clean default templates
+
+Even without doing presenter templates, template overriding can be useful to clean some cruft from templates provided by core or contrib modules.
+
+The node.html.twig template is a good example, because it carries a lot of legacy junk, like a title base field display condition based on view mode name (!) and a poor man submitted by.
+
+It is better to keep those templates as lean as possible, and to push the complexity to layouts and other display modes plugins.
+
+For example:
+
+- `field.html.twig`
+- `block.html.twig`
+- `node.html.twig`
+- `taxonomy-term.html.twig`
+- `media.html.twig`
+- `comment.html.twig`
+- ...
+
+Those templates content can be replaced by:
+
+```twig
+{% if attributes.storage() %}
+<div{{ attributes }}>
+{% endif %}
+  {{ content }}
+{% if attributes.storage() %}
+</div>
+{% endif %}
+```
+
+Or sometimes, by more complex stuff like:
+
+```twig
+{% if attributes.storage() %}
+<div{{ attributes }}>
+{% endif %}
+  {{ title_prefix }}
+  {{ title_suffix }}
+  {{ content }}
+  {% if attributes.storage() %}
+  <div{{ content_attributes }}>
+  {% endif %}
+   {{ content }}
+  {% if attributes.storage() %}
+  </div>
+  {% endif %}
+{% if attributes.storage() %}
+</div>
+{% endif %}
+```
+
+Some markup of components or some utilities style expect specific markup with direct children like flex feature. Currently when trying to use those components in lists the wrappers inside templates like field.html.twig and node.html.twig will interfere with the expected markup. So sometimes even the wrappers need to be removed with templates override.
+
+Use the <a href="https://www.drupal.org/project/entity_vdts" rel="nofollow">Entity View Display Template Suggestions module</a> to be able to remove the wrapper of some entity displays. If the theme provides templates with bare minimum markup like just the "content" variable printed, for content entities with the module you will be able to remove the wrapper with configuration.