This might initially seem unrelated to the issue title, but please bare with me...
There is this slight WTF (or feature, depending on how one looks at this) with visibility conditions not being available unless the right context is selected. This has made me scratch my head quite a few times before a final aha! moment. Examples include the node/% context that provides the "Node type" and "node_nid" conditions and the taxonomy/% and taxonomy/term/% contexts that provide "Vocabulary" and "taxonomy_term_tid" conditions.
Now, say that for example I want a specific design to be applied in specific terms/vocabularies and in specific nodes or node types. The way to achieve this currently is to create two different layouts, one with a taxonomy context and one with a node context in order to be able to specify those conditions separately. In such situations, we are not offering the option to have a single layout that one can use in both contexts. So the site admin/builder needs to apply the same changes to two (or more) layouts. Tedious UX there.
Add the WTF I mentioned at the start to this and you have really confusing things going on UX-wise.
My question is this: would it make sense to implement any of the below things...
a) Allow multiple contexts to be added to a single layout ...so that multiple visibility conditions become available. This way, we save people from having to create and maintain multiple layouts with the exact design.
b) Allow people to select visibility conditions and have the context be filled in automatically (or present a drop-down with options if there is more than one available). Visibility conditions are easy to grasp contrary to the context thing which is pretty vague to a newcomer. We currently have it so that people need to select the right context in order to allow certain visibility conditions. I feel that it should be the other way around.
c) Perhaps we should replace the "Path" text field in the layout create/edit form with a drop-down. The options would be the most commonly used ones (node/%, taxonomy/%, taxonomy/term/% etc) and there would either be a "Advanced" or "Manual" or "Other" checkbox (or drop-down option) to allow advanced users to manually enter a path.
Thoughts?
Recent comments
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5
Worked like a charm! Exactly what I envisioned... now I can edit the ruby text right in the editor, sweet:) Thank you! For those who may have a similar issue, try TinyMCE, create a new "text...
Specific tags to work in CKEditor 5
Yes, you can use TinyMCE on some content and CKEditor5 in others. There is no problem having both enabled on a system.
Specific tags to work in CKEditor 5