@espenmn... funny you mention all of this.. I composed the response below about 2 hours ago but just got around to posting it. Your solution is intriguing, I'll have to look at that.
Regarding themesitesetup, I mentioned it because I'm assuming TTW all the way, but it means they would be on a installation with all those prerequisites.
Exactly, these hacks solve the problem but....
The problem we have is that #content, which is where everything gets rendered is wrapped in a .container. I've thought of using a Diazo rule to kill the wrapping
.container but haven't gotten around to the experiment.
What I'd like to see:
It would be nice to make it possible for mosaic to use the
.container-fluid as they were designed.
So two options (both I have not explored):
- Tweak barcelonta to ship with
.container-fluid instead of
.container by default.
- Create Diazo rules that remove the
.container dynamically when mosaic is enabled.
It would then mean that every mosaic row would be wrapped in a
.container by default making each row fixed-width by default.
Then when a user selects fullwidth, it would switch to toggle
.container-fluid to make the row become fullwidth. I haven't dug deep enough to know what will happen with such an approach. Best case, the implementation will just work but I'm guessing that something will break with the current mosaic implementation if this is done.