Is there an easier ways to have tabs inside tabs?

[AmyRoxwell]

Hello! Thank you so much for the work made with this plugin! It has come pretty handy and made it really easy to display a lot of info n a single page. But our team are currently facing a big issue with the TabberNeue plugin, a little bit of context:

I'm currently working on a monster hunter wiki, monster hunter has a lot of information for even a singular monster and we would like to display said data using tabs, that way if the user needs to find info of a specific version of a monster, they can just click the tab and see that info, but the issue we are encountering is that we need sub-tabs inside those initials tabs.

Every monster drop table changes depending of the rank you fight it, so in a single page for a monster that has appear in all games, we are easily needing a grand total of 13 main tabs (Where we include the tab of the game data they have for that game) and 39 sub tabs (Mostly for the different drop tables items and chances they have per rank), for a grand total of 52 tabs.

Is there a way we could implement this without using the Nested tabbers system? Cuz as of right now, it makes the code pretty messy even while using <!-- -->, due to the huge amount of Curly brackets we have to end up using and keep track.

Maybe something like <subtabber></subtabber> system for Simple tabbers where you can put those commands at the beginning and end of the tab content and the plugin would display it as a subtab of the main tab. I don't know how feasible this is due to not being a programmer but mostly an editor and it's understandable if there is no way to have simple subtabs.

Once again, thank you so much for your hard work maintaining and upgrading this plugin and it's understandable if this niche issue is not worth fixing.

[alistair3149]

The nested tabber syntax was something that I inherited from the old Wikia extension and I am not sure why was the decision made. My guess is that there were some incompatibility issue with nesting parser tags. If that is the case, that might require a rewrite of how the Tabber syntax works. It is not something that I am comfortable of doing at the moment until more work is done on the MediaWiki parser migration to Parsoid.

To solve the maintainability issue on your side however, you can wrap Tabber in a wikitext template so you don't have to deal with all the curly brackets. Alternatively for complex templates like that, it is much more manageable to use Lua modules instead.

[AmyRoxwell]

The nested tabber syntax was something that I inherited from the old Wikia extension and I am not sure why was the decision made. My guess is that there were some incompatibility issue with nesting parser tags. If that is the case, that might require a rewrite of how the Tabber syntax works. It is not something that I am comfortable of doing at the moment until more work is done on the MediaWiki parser migration to Parsoid.

To solve the maintainability issue on your side however, you can wrap Tabber in a wikitext template so you don't have to deal with all the curly brackets. Alternatively for complex templates like that, it is much more manageable to use Lua modules instead.

Thank you so much for the quick answer and also for giving us some tips! I will be passing this to our programmers.