In general, I find the tabs very good because I no longer need to use a custom field. At this point I would like to say a big thank you to the tab field of afbore - https://github.com/afbora/Kirby-Tabs-Field - which I also found much easier to use because the elements are not nested as complex as they are now had. But this only as a note. Possibly, you could solve this again as it was really uncomplicated.
I have the problem that in my Kirby a lot of options have to be accommodated. So first my question how I bring the whole in the settings of Kirby? That did not work out so far. Now I have a lot of settings but this must be in the dashboard accommodate and the settings tab is totally empty.
But even if I could do that, the tabs are still causing massive problems as they are simply not designed to accommodate a lot of information and settings. Or can tabs possibly synonymous nested?
Here is a screenshot of what the current looks, and unfortunately are not all positions housed. My idea for better tabs in the appendix is sometimes pushed with quite rudimentary CSS. So could be placed significantly more tabs. In the ideal case, the tabs are then at a smaller viewport width to a kind of Accordion or something in the way. Maybe this will be a option for the Tabs in future?
- Why are the Blueprint tabs so complicated and nested?
- Current tabs have a problem with many entries
- Can tabs currently be nested?
- do tabs work in Structure Fields?
- how do I get settings in the settings bar?
- new idea for better tabs