Home

Welcome to the drupal-govcon-2024-ui-patterns wiki!

Here we will demonstrate some of the functionality behind Ui Patterns with some hands on assignments.

UI Patterns Manifesto

The gap between the themers and the site builders has to be reduced. Too much PHP code (custom plugins, events, hooks preprocess, hooks alter...) is produced by the back-end developers, on each projects, to fill this gap.

Moreover, if this PHP code is not fully provided, the themer may need to overcompensate, adapting its work to provide peculiar markup or abusing templates overriding and suggestions mechanisms.

It was an issue when we were implementing plain dull mockups. This is even more the case today with new norms and approaches like Design Systems. So, we are finding and creating Drupal modules to cover all the parts (components, styles helpers/utilities, layout systems, examples pages...) of a design system, while:

• letting the themer owns and drives the implementation, easily declaring YAML files from the theme folder
• exposing this implementation directly to the site building, in Drupal backoffice (layout builder, manage display, views, blocks, flags...), as configurable plugins
• for specific business cases, exposing this implementation to the back-end developer as a nice and robust API

Resources

Ui Suite

• https://www.drupal.org/project/ui_suite
• https://www.drupal.org/project/ui_patterns
• https://www.drupal.org/docs/contributed-modules/ui-patterns/welcome-to-ui-patterns-documentation

Ui Suite USWDS

• https://www.drupal.org/project/ui_suite_uswds
• https://www.drupal.org/project/ui_suite_uswds_paragraphs
• https://www.drupal.org/project/ui_suite_uswds_extras

Single Directory Components

• https://www.drupal.org/docs/develop/theming-drupal/using-single-directory-components
• https://www.drupal.org/docs/develop/theming-drupal/using-single-directory-components/frequently-asked-questions