Quick update; the Utility Components module now has 3 new components:

• Styled text: Single line of text with support for font size, style and weight, letter spacing (tracking), line-height (leading), and capitalisation. It's good for those little colourful labels of all-caps text that AI likes to add to designs, or for extra large text (e.g. in a "key numbers" row).
• Carousel: Displays multiple slides of content, one or more at a time. Choose between a "slide" and "fade" animation. Navigation between slides can be automatic, or controlled via swiping, scrolling, or arrow buttons. Built using Splide.
• Marquee: Displays elements like images or text in a continuously-scrolling bar. Can be paused, and has controls for things like speed, gap, direction, etc. Built using Marquee6k.

They're vanilla and mostly independent, so you can just copy them into your existing theme if you want instead of installing the module. Just make sure to copy the relevant library if you do.

Hi everyone. Last week I posted about a new module I made for the Canvas layout builder called Layout Components (it has a beta release now).

Today I've just published the complimentary module to it: Utility Components (also beta release).

It contains a bunch of components that are quite popular in most layout builders: • Cover • Expander • Heading • Hero • Icon • Image • Image card • Image beside text • Line • Quote • Text

I made them with the same philosophy; Super simple and lightweight, so that they can easily work with existing themes; independent, so that you can just copy-paste the ones you want to use into your own theme; and completely hand-made (no AI).

I've set up live demo pages to check them out: Layout Components demo and Utility Components demo

I hope they're useful 😄

I've been making Drupal sites for about 12 years, so it's rare that I get stumped when trying to figure out a good solution to a problem, but this one is tricky...

Okay so this is quite a big site (approx. 5000 nodes), with like 10 taxonomy vocabularies. One of them is Tags, with like 2000 tags.

And for almost all of those vocabs, the standard Taxonomy Term view (that appears on route /taxonomy/term/%) that appears on their term pages is just fine.

But for one of the vocabs - called Organisations - I need to use a different view. This view needs to have different fields and filters, and a different treatment for the Title override.

My first thought was to use a unique alias pattern (from Pathauto) to show those term pages at different URLs (e.g. /organisations/*), and then make the new view and make it show on the same route. However that doesn't matter, because the Taxonomy Term view shows on the route /taxonomy/term/%, so it applies to the Organisations pages no matter what I make their URLs / aliases.

And that Taxonomy Term view still applies even if I add a filter that excludes the Organisations taxonomy. In other words, the filter only reduces the results, but it doesn't affect whether the view is applied to that page or not.

Then I though perhaps I could make new pages for each organisation, then place block views on those pages to simulate the term fields and the grid of tagged content, similar to the other term pages. But this doesn't really work, because for those block views, they have to get their "contextual filter" value of the term ID from somewhere. The Taxonomy Term view just gets it from the URL, but with these new pages, the term IDs wouldn't be in their URLs (or I could put the ID in the URL, but that would look bad).

Do you have ideas on how to solve this in a practical way?