This is a follow-up task that was mentioned in #2074 (where we removed the tag default from all core views).
Now with Views in core and also with admin_views in core, I think that it would make sense to be adding:
- a core tag for all views provided by core
- a custom tag for all views manually added to the site
- a %module name% tag for all views regardless of whether they are core/contrib/custom (we currently have a "Default (module-provided)" indication in the "Storage State" column, which is not very useful, but it would be if the module providing the view was also indicated). If not a tag, this could be a new provided-by property.
As it is now, these tags would have no value, but if we added an instant search filter at the top of the views list (#503), then it would be very useful, because as you must have also experienced yourselves, most sites end up with a few dozens of views.
Anyways, I have previously filed #1897 in which I mention the same issue. Similar/related but different problems.
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