- Issue created by @idiaz.roncero
- 🇬🇧United Kingdom very_random_man
Yes I'm thinking this might be handy too. At the moment gin_lb is presenting issues with consistency. The main use case is where there are users who do page editing but don't use the admin theme for anything. For example, you may have site admins / editors using the admin theme for both content and general tasks but group editors only editing content and layouts in the front end theme. Gin LB adds loads of improvements that enhance the group editors' experience but the more 'Ginny' bits don't make sense to them.
Another kind of inconsistency is the media browser. It looks great on layout builder pages but none of the benefits are available on other media elements, like node edit forms. This requires a certain amount of effort to figure out how gin_lb is working and how to activate it on non-LB forms.
As mentioned above, the next example I'm dealing with is Toastify. Currently I have toastified messaging on only LB pages and nothing on the rest of the front end. I think it would be a good idea to remove it entirely and maybe just recommend using this module: https://www.drupal.org/project/toastify → which would apply it across the theme by the looks of things. I'll raise this as separate ticket.
Maybe this module needs a broader remit to provide ginnyness to front-end themes as a whole? I'd love to apply some of the normal Gin node editing functionality to the front-end theme, such as having the form actions pinned to the top.