:–) Ok I’ll expound upon my singular sentence above. It just seems odd to me for the app to be contrary to the official Bootstrap migration by default. Users need to be made aware and learn at some point and it seems out of the gate is the best time to set such a precedent for those using Bootstrap v5. My contention is leave it off and be true to form with Bootstrap v5. By contrast if people want or need jQuery they can enabled it.
Though if the BSS developers truly feel it’s a concern they can simply auto detect the jQuery requirement in the app. Then no toggle is needed and the process is transparent for all users if indeed it’s an issue and they want to streamline the user experience for beginners.
I guess I would like to know what caused @Martin to create such a poll feeling a need to rethink things? Are the BSS Devs getting lots of direct support inquiries? Because here on the forum from what I’ve seen there has not been a slew of related questions ( one (others?)) from confused users. Bootstrap v5 has been supported in BSS for a while now, so the forum does not seem to be the measure. Plus a quick search by users in the ever expanding (currently being overhauled) Bootstrap Studio documentation yields a quick answer. Maybe the docs could be made more self-evident and it could be called out more explicitly in the docs side menu, BS4 vs BS5, jQuery, etc., ?
By the same token if people are averse to change, then what if users likewise want to use old Bootstrap v4 classes they have committed to memory for years, or still support IE ? In my opinion people need to be made aware and learn of all the changes that Bootstrap v5 brought forth including the absence of jQuery.
So in general it seems odd that the app would be contrary to the official Bootstrap migration by default in an app that tries to adhere strictly to the official Bootstrap standards. I’m not trying to be an adversary - thats just my personal point of view. 