Don’t take it personal thats a historical occurrence with this community of users.
Some really interesting dialogue happening throughout this thread.
The general discussion about more core Blocs and Brics has likewise been duly noted historically by various users previously over time. Given both of their centralized meaning as part of the apps workflow, its proper and ok to expect more from the app natively out of the box in various ways. Even quick build sites require more features in todays dynamic connected web, static sites are dying making the need of the “basics” a far more reaching scope within modern web requirements for most all sites.
I think @norm is aware of such things, so time will tell regarding how things progresses.
I was gonna post originally but then just watched the discussion unfold.
@DanielF Back to the topic …
Lets recap a bit (even though your orginal post has now been edited 8 times).
So in its current state, Blocs uses and is based upon Bootstrap. So the required associated CSS (bootstrap.css) and JS (bootstrap.js) for Bootstrap are already present, in addition to the jQuery library. Also since you mentioned it, you would not want to mix Foundation with Blocs, as Bootstrap and Foundation are two totally separate frameworks. That would become a mess and redundant quickly within the same site.
Since Blocs is a visual based app it already has many custom CSS classes and override styles already in place in the “style.css” which is exported with each site. When you use the Class Manager your custom class styles also get included into the “style.css” upon export.
In addition to the features this “style.css” provides with Blocs being a visual tool, it also includes the “blocs.js” file. This JS file also includes custom jQuery logic and overrides that allows for Blocs to be a visual approach with added functionality without requiring users to self code these functions for various features the app offers visually. Beyond the existing custom CSS and JS that Blocs already provides, it also already includes other libraries (Icon Libraries, Animate.css, Form Handling, etc.,) for various other things which allows the user to implement features through visual methods.
So beyond those aspects it then offers various methods for the user to add additional custom user CSS and JS, full CSS or JS libraries, etc. But when you get to this point you need to understand how to implement them via the HTML Bric, Page Settings Add Code and Attachments, ID’s, Custom Classes, Sub-Classes, Selectors, Specificity, etc., along with any additional required setups and implementations regarding what you are trying to accomplish and implement.
As an example, in the case of Bootstrap Tabs, currently you would need to be aware of how the Bootstrap Tabs are constructed. What Classes to then override, what conflicts could occur with the already existing “style.css” and how to rename and organize things for possible conflicts, overrides and desired custom styling. As you may have already noticed Bootstrap Tabs are closely tied to the Bootstrap Nav. So perhaps that is part of the reason they are not included currently in Blocs given crossover and possible conflict and segregation with the Blocs Menu Manager, but only @Norm could speak on why various aspects of the Bootstrap framework are absent.
In addition to Bootstrap, you can also implement other vanilla HTML, CSS or JS if you desire and understand how to do so.
Blocs Related - Custom HTML / CSS / JS:
- https://help.blocsapp.com/html-widget/
- page-settings – Blocs – User Documents
- Page Attachments – Blocs – User Documents
- Custom Classes Basics – Blocs – User Documents
The following link may also prove helpful with general aspects as you try to implement custom styling.
You can also find full lists of the Bootstrap base class list by Googling, but the included Blocs "styles.css is already providing custom styling and overrides as mentioned above. One benefit is with Bootstrap being the most prevalent framework used on the web you can find examples and questions of people already encountering much if not all of what you hope to accomplish, once you know what you are looking for.
@Pauland, your post today in another thread seems likewise relative in this thread. I think in a nutshell this same “ease of transparency” in general is what @DanielF is referring to concerning classes and other feature aspects.
I am sure all Blocs users would be well pleased with such a method and approach. Hopefully Blocs 3 will remedy many of these areas and sticking points for users in the app.