Single Directory Components are an exciting new tool for #Drupal developers. However, putting components in a page still requires a developer editing some Twig code to embed it.
What if front-end developers could build a library of components, that site builders can put in the page. In this video (<5 min) I will start exploring some of those ideas.
One of the goals of the Single Directory Components initiative is to promote and encourage the development of #Drupal modules that provide features using Single Directory Components.
In this video I show two key tools for your module's settings screens that will improve the UX of site builders.
In this video I show my current progress on the SDC Display module. I will render an entities using a card component only using the admin UI. At the end I will use a similar technique to render a field using a component. It also includes software bugs.
After reading feedback from several of you, and careful consideration, @pcambra and I have decided to block threads.net from our instance. This aligns us with lots of instances that have done the same.
This little module I wrote for IBM (a previous client) will help you preview pages with entity references. It will show the latest changes, even when you are not using paragraphs.
I just submitted the last MR to make Single Directory Components part of core itself, and not a module. This was one of the goals of the stabilization effort.
Once this is merged to our feature branch, we can have core committers reviewing the big merge request.
We are done with our #lego set from #legoland. I think it looks awesome next to our live orchid (which had its 8th blooming earlier this year #humblebrag)
Do you want to help out to make Single Directory Components stable 🧭? Here there is a template issue you can clone to refactor tiny parts of Umami to use components.
