[META] Make creating slot content more intuitive

Created on 10 November 2024, 5 months ago

Problem/Motivation

Now that we have a stable release technically spoken, we should focus on making the UI more intuitive for content creators.
Adding slots already is pretty simple, so I'd like to focus on the content creators experience in this issue.
There has been platy of very valuable feedback at DCBerlin2024 during our session and in various hallway-talks.

This issue should be used to keep track of those issues so we can see what exiting new things will happen in 1.1.0.

Remaining tasks

* Use a select field on the slot condition, providing the available slots
* Remove the slot condition from all condition definitions, since it only makes sense in the context of slots
* Hide and prepopulate the condition and condition_group operators for content creators since only one setting makes sense (always)
* Provide slot condition automatically in the slots field widget, since it's always required in order to work
* Add the possibility to "unpublish" condition groups
* Make the "This content shall be displayed in slots." checkbox actually work when disabling
* Make it more intuitive to add more conditions (by using a dropbutton)
* Add content creator oriented documentation page on d.o.

This is a living document.

Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇩🇪Germany Hydra

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

Comments & Activities

  • Issue created by @Hydra
  • 🇩🇪Germany Peter Majmesku 🇩🇪Düsseldorf

    I've tested slots and they look really promising. In my previous project, we anticipated blocks that were intended to be filled in the future.

    However, I strongly advocate for improving the form display widgets for the slot selector in the custom block type. Typing a unique ID into a text field every time feels somewhat "hackish" and isn't intuitive enough for content editors, in my opinion. It would be great if the site builder could choose either a select or autocomplete widget here for custom blocks.

  • 🇩🇪Germany Hydra

    Hey @peter majmesku! Thx for the feedback on this. We are definitely planning on doing this. The current UX work goes into the overall widget handling, here a preview of my recent (working) mockup:

    The next step would be implementing a mechanism to track the id's in order to do what you suggest.

    If you'd like to contribute, let's get in touch!

  • 🇩🇪Germany Peter Majmesku 🇩🇪Düsseldorf

    > If you'd like to contribute, let's get in touch!

    Sure, I've sent you a PM via your user profile.

  • 🇩🇪Germany Hydra

    Version 1.1.0 contains all the enhancements. Care when updating, one of the dependencies changed so it might be necessary to disable the "plugin_config_form_builder" module first.

  • 🇩🇪Germany Peter Majmesku 🇩🇪Düsseldorf

    Great! Thanks for the new minor release. 🥳🎉

Production build 0.71.5 2024