Hey Liam! In case we want to support UI Patterns next to CL Editorial we could have soft-dependencies and allow using both ecosystems and not just one module.
Should I work on making this more pluggable so we can have two different plugins for the integrations that will have different user interface?
Hey! That is amazing news, huge thank you for making this possible <3
I would like to opt-in for the following projects:
Really looking forward to see that in action 🥁
We need to use lifecycle_link and not lifecycle-link. See
https://www.drupal.org/node/3215042 →
I had this problem with Frontend Editing module which is adding a pseudo field to the display.
Hello again 👋 I wanted to share the minimal plugin implementation based on Embedded Content → module ➡️ ✨ Embedded Content plugin Active .
Even if we don't want to introduce new dependencies I think that can be helpful for people so they could already place components in CKEditor.
I had to create a follow-up issue since we are not allowing dots to be used in the library name which is needed when you want to load a SDC library ➡️ 📌 Fix RegEx for Icon library schema definition Active
yannickoo → made their first commit to this issue’s fork.
The Frontend Editing module is making use of hook_entity_view_alter which is not a preprocess but some other sort of altering the data. Do you think support for that can be possible?
@mogtofu33 already made it clear that any module which is using pseudo-fields won't show up. E.g the Frontend Editing → is also using a pseudo-field to provide the markup for the markup that is needed.
If we wouldn't support those we would need to allow something that can be added and which is context-sensitive.
Oh wow, so nice to see that this was committed <3 Thank you very much 💪
Thank you for the presentation, really impressive what happened in the meantime 💪
For anonymous users we will other placement options like "Sticky" or "Inline" later.
It seems like the spellchecker is not able to run, so how should we deal with that? https://git.drupalcode.org/issue/drupal-2895477/-/jobs/6300642
yannickoo → created an issue.
I have adjusted the condition for the validation so that from now on only elements with type="submit" attribute are used for validation.
yannickoo → made their first commit to this issue’s fork.
Thank you very much 💪
Hello 👋 I am coming from #2807857: Exposed filters do not appear on attachment display → and can confirm that the patch #40 has fixed the issue, thanks for that 💪
Since the other issue 🐛 Attachments on Views Content Panes don't always inherit exposed filters Postponed: needs info is taking care of the same problem and a working patch is there I am closing this issue
I have experienced the same issue and can confirm that that the patch linked above 🐛 Attachments on Views Content Panes don't always inherit exposed filters Postponed: needs info fixed the problem 💪
This looks good from my side! Let's get this forward with another review so setting to RTBC 😎
g4mbini → credited yannickoo → .
yannickoo → created an issue.
Thank you ksenzee, really nice change! I have requested a small thing to change the way we are accessing the configuration, otherwise approved from my side 😇
Thank you for the quick feedback! I will forward this this to the kitchen 🧑🍳
Fresh out of the oven four new candidates for the logo 🔥
Here you can find a screenshot of the changes with explanations:
yannickoo → created an issue.
yannickoo → created an issue.
It is important for me to add classes for styling purposes directly on the link, therefore the flexible function is very useful 🎉
In order to provide a quick overview about all the current candidates I have prepared this here to make it easier:
I think it is important to have a proper logo for the Experience Builder that is not just a 💧 but something on its own. When you check the Modules → overview page on drupal.org you will see that many projects are just having a drop with something inside. The Experience Builder should have something unique because it will be visible in presentations where we cannot just two drops next to each other, that would look too similar.
Here are few logos of other projects that are using the drop approach which we should not necessarily follow:
I forgot to post my feedback for the stacked layers: I think that can confuse people since this is exactly the same icon we use in the Navigation for the Structure link.
I'm closing this one here so we can continue in 📌 Storage key of Paragraph behavior should not come from default configuration keys Active .
I have created a MR that is allowing setting the key to access the Paragraph behavior setting manually. I think it's not needed to let the user choose from the default values since they are not being used to set the value as mentioned in the issue description.
Furthermore I have renamed the paragraphs_behaviors plugin to paragraph_behavior which is the better term in this case since we are only fetching a value from one Paragraph behavior.
Let me know what you think 😇
In my case it was not applied due to Gin theme. I have added 2 more selectors which are covering the Gin vertical toolbar and the "fake navigation" bar that the theme provides as well.
Wouldn't it be nice to just have the local version which could be automatically installed via composer.libraries.json file?
After a while I was able to figure out the root cause for this: Ensure that your normalize / reset CSS code is not having generic selectors like [type="checkbox"] but input[type="checkbox"] instead to avoid overriding the CSS style of the contextual menu items 💡
Closing this one but might be helpful for future ✨
I have created a new follow-up issue to handle this after the refactoring: 🐛 Z-index is still too low to cover Navigation bar Active
yannickoo → created an issue.
I can confirm that the fix is not there anymore, I think this has been changed in this here 🐛 Z index problems Active
Here are some more examples:
Hey together 👋 I have also noticed that the Twig function did not work as expected.
My goal was to create an obfuscated email link for info@example.com with an extra class attribute for styling. Unfortunately the MR that has been created could not help me since there is no support for attributes even if the module itself could handle that :(
After checking the code I figured out that we got a small mess here regarding the order of the arguments: Sometimes it was $email, $params, $text and somewhere else $email, $text, $params.
The MR I have created fixes
- The broken Twig function
- Wrong order for arguments
- Attribute support for Twig function
Example usages
Minimal example
{{ obfuscate('info@example.com') }}
➡️ <a href="mailto:info@example.com">info@example.com</a>
With link text
{{ obfuscate('info@example.com', 'Link text') }}
➡️ <a href="mailto:info@example.com">Link text</a>
With link attributes
{{ obfuscate('info@example.com', 'Link text', {
class: 'font-bold'
}) }}
➡️ <a href="mailto:info@example.com" class="font-bold">Link text</a>
yannickoo → made their first commit to this issue’s fork.
kristen pol → credited yannickoo → .
kristen pol → credited yannickoo → .
I have just asked ChatGPT and it's saying the following:
🔍 Interpretation of the Logo
Puzzle Piece Shape 🧩
This suggests modularity, plug-and-play architecture, and customizability — all key traits of Experience Builder and Drupal functionality.
Pencil Icon ✏️
Indicates editing, customization, or content creation — a natural fit for a WYSIWYG (what you see is what you get) or low-code editor.
Color Scheme 🔵
The blue and white color is reminiscent of Drupal’s own branding, which strengthens the association.
I am really happy to share the work of my colleague Ángela → 🎉
The logo is showing a puzzle piece which stands for components that can be placed into the Experience Builder. The pencil inside of it indicates editing functionality which is a great combination! It is following the new CI of Drupal and looks very clean so it can be used for promotion of Experience Builder.
SVG and 512×512 PNG files have been attached ✅
What do you think about it?
So we have a new MR now that is against 11.x branch. Tests are still missing.
yannickoo → changed the visibility of the branch 11.x to hidden.
I am happy that I found this and never needed to use that in my time working with Drupal - until now :D Even when having the patch applied I cannot see a differen action attribute in the exposed filters forms.
Do you think we should also try to read that configured Custom URL first before taking the <current> URL like this?
$form_action = $view->display_handler->getPath() ?: Url::fromRoute('<current>')->toString();
Hey 👋 I just wanted to let you know that the design department of 1xINTERNET is currently working on a logo for this, I will provide it here once it is available.
I can report another BC break in Embedded Content → module: 🐛 Uncaught CKEditorError: Cannot read properties of undefined (reading 'pencil') Active
yannickoo → created an issue.
I can confirm that we need to investigate here because of the size calculation with the new navigation :/
I have no clue how I encountered this but the merge request was a quick fix for that, thanks 🎉
I agree that removing the type="checkbox" needs to be there but I am still wondering what could be the reason that the contextual menu doesn't render properly in a custom theme.
pdureau → credited yannickoo → .
In case that people are still interested in seeing how to solve this nowadays: You can use the combination of Menu Item Extras → and UI Icons to get this working 💪
yannickoo → created an issue.
yannickoo → created an issue.