Add Components Module to Drupal Core

Idea summary

What is the problem to solve?

Component-based design/implementation is an evolving-best practice for front-end development, whereby individual components are created one-by-one (header, footer, card display mode, accordion, etc) and packaged with all their frontend assets in one place (twig template, (s)css, js). See Driesnote from DrupalCon Dublin (I think, it was Dublin).

At the moment, if a developer creates these components as standalone items (using PatternLab, Fractal, or some other system), there is no way for Drupal to have knowledge of them. This means (at a minimum) the twig files need to be duplicated into the Drupal /templates folder of the current theme, leading to duplication of code, and some sort of gulp task or otherwise getting the CSS and JS assets to the Drupal theme and other extra maintenance. It means that it is much more difficult to maintain living styleguides created by PatternLab or KSS or a custom system.

With the advent of the 'Out of the Box' initiative, there is going to be a new theme in Drupal core → . The developers of this theme (I am one of these) will be builing this with best-practice in mind and are aiming to build a styleguide into the theme, using component-based design principles. Having a way to reference components would make this much easier for us (and any developer in the future who wishes to use component-based design in their custom or contrib themes, opening up many new avenues to Drupal front-end development). It would also mean that contrib themes would not need to depend on a contrib module.

Though quite a small module (it does one thing, and does it well!), it would open up/encourage a lot of new frontend possibilities.

Who is this for?

This is a utility tool for front-end developers.

Result: what will be the outcome?

The components module allows Drupal to reference twig files outside of the /templates folder, making component-based design much easier and more maintainable for developers.

How can we know the desired result is achieved?

As long as we can reference templates outside of the theme's /templates folder we know the result has been achieved.

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 3 months ago →
🇭🇺Hungary Gábor Hojtsy Hungary
Are there benefits for the whole ecosystem in this additionally to SDCs that are in core?
Comment 3 months ago →
🇺🇸United States brianperry
> Are there benefits for the whole ecosystem in this additionally to SDCs that are in core?

While SDCs probably reduce the number of cases where this is critical, I don't think they completely eliminate the need for this type of Twig namespacing.

Did any of the experience builder work introduce a Twig namespace equivalent? Want to say that I vaguely remember someone mentioning that, but I might just be continuing to imagine XB addressing all of my possible FE hopes and dreams.
Comment 3 months ago →
🇺🇸United States effulgentsia
Did any of the experience builder work introduce a Twig namespace equivalent?

Nope. Sorry to disappoint. XB uses SDCs but does not use namespaced non-SDC Twig files.
Comment 8 days ago →
🇳🇿New Zealand quietone
The Ideas project is being deprecated. As discussed in a core committer meeting issues that are adding modules are being moved to the Drupal CMS project for discussion.
Comment 8 days ago →
🇳🇿New Zealand quietone
Comment 8 days ago →
🇺🇸United States tim.plunkett Philadelphia
Comment 2 days ago →
🇦🇺Australia pameeela
I don't see this as a Drupal CMS issue to solve, since it's more about developer experience. Closing for that reason but if folks think it is something for core to address, please re-open or possibly create a new issue to restart the discussion.

Add Components Module to Drupal Core

Idea summary

What is the problem to solve?

Who is this for?

Result: what will be the outcome?

How can we know the desired result is achieved?

Comments & Activities