I finally have a little time to test gpEasy 4. This is my first real interaction with Bootstrap and I'd like to learn the best way to customize it.
My first idea was to copy a Bootstrap theme and override all the default settings in that theme's settings. That would work well for minimal changes, but not for significant customization. From a design standpoint, it would prevent me from using the power of LESS to adjust all mixins at once. From a performance standpoint, having many styles defined twice is inefficient.
So, I suspect I should bypass all the CSS files in thirdparty/bootstrap and include my own customized bootstrap in the theme folder. Should I simply replace
common::LoadComponents( 'bootstrap-all' );
common::LoadComponents( 'bootstrap-js' );
to load just the js part of Bootstrap?
In that case, where should I store the CSS files to be accessed by the template? base.css?
I'm looking forward to having an updated section in the documentation on Bootstrap themes.
I set up a theme that allows you to customize bootstrap with LESS. Since it requires a LESS compiler (preferably on a local server), it's not really for the average user. It's really aimed at theme developers. It also could use a bit more testing.
As such, should I load it to the themes section or should I send it to a few people for testing first?
It would still work with LESS, but could not be customized so it wouldn't have any advantage over the built-in bootstrap theme. I'll try uploading it with a good description on what it does and does not do.
Maybe we should have an option to tag add-on plugins and themes as beta to warn users about potential issue. It would also encourage developers to share not-ready-for-primetime add ons.
Alright, I added the theme Cobbler for everyone to test.
Without modifications, it should look and work like gpEasy's Bootstrap. With modifications, your imagination is the limit.
Find out more about our Provider Spotlight