User blog comment:DaNASCAT/Technical Update: June 12, 2017/@comment-3218221-20170613135028/@comment-3218221-20170613141949

Yes, I read that forum post around the time it came out - and the ensuing prolific discussion it generated. I suppose I can accept the general move against javascript (less so re: CSS) but I still have my frustrations over this mentality of "decision paralysis" in which too many choices frustrate and paralyze my users. Frankly I find it almost infantlizing - not that I'm saying it can't happen, and not that I'm saying Extended Nav can't be misused (e.g. over-saturated) but this assumption does come across as somewhat condescending.

Not just to the users, to the admins as well. It implies off the bat the admins are incapable of using extended nav judiciously. Take how it was used sparingly on the Steven Universe wiki (e.g. Garnet->two further items) before the update. It suggests that all admins can't be trusted to apply extended nav with good judgment.

Isn't there a way you could allow for fourth-level navigation but limit available fourth-level slots to a certain number for wiki? I'd still dislike it, but it would at least give us some maneuverability while still giving ultimate control to you. I suppose you're saying it can only be implemented through Javascript, and thus impossible, but...