[2.0.0-beta4] Use Drupal entities & plugins for the Library pages

Created on 4 April 2024, 8 months ago
Updated 20 September 2024, about 2 months ago

Problem/Motivation

Today, UI Patterns Library 2.x works a bit like UI Patterns 1.x:

So, the opposite of what we (UI Patterns & UI Suite community) are proposing and promoting in Drupal: To leverage config entities & plugins.

Proposed resolution

So, 2 proposals:

  • From @pdureau: Expose components quick links as a menu with menu links.
  • From @smustgrave: turning the patterns library into a view, something that could be filtered and searched on. "Not sure how that would work but seems like an approach that could cover several scenarios. I can hide certain patterns, by ID or category tag, can search for project specific ones, etc"

The other goals if to keep able

ng-tasks">Notes

  • It may also be the opportunity to replace /patterns by /components or other more suitable path. See 💬 Route overlap with Examples module Active
  • Is it possible to create a view of plugin definitions? A view without DB table? We may need to hook views data
  • Do that mean that component metadata (title, description, tags, slots, props, stories...) are becoming "fields" were we can use field formatters?
  • The end goal is to get rid of the controller and the hook themes, not to have a mix of them
📌 Task
Status

Needs review

Version

2.0

Component

UI Patterns Library

Created by

🇫🇷France pdureau Paris

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024