The error you can see in this screenshot when running recess seems to match this bug report:
https://github.com/twitter/recess/issues/102
David Scotson
Posts made by David Scotson
One of the ideas behind using Bootstrap is a) there's a community of people out there building on it, and b) you can create quite nice things just by using the HTML editor and the standard Bootstrap HTML.
A combination of these things is this follow link. Bootsnipp is a place where people share nice little "chunks" of websites based on Bootstrap HTML. Here's a footer, similar to what you would see on many websites:
http://bootsnipp.com/snipps/company-footer
Mary had the clever idea of adding a customisable footer to the Clean theme, to which you can add any HTML like. If you take the above Bootsnipp HTML and paste it into the correct place in the theme settings you get a fairly pleasant looking, and relatively easily customisable way of creating a footer that suits your own site. (Note also that it collapses into vertical list on iPhones etc.)
The example actually overcomplicates things more than it needs to (e.g. there's no need to set the width via a style tag), but it's still a fairly simple way to customise your Moodle without needing to edit files etc.
This one is also fairly simple and may suit your theme, though this time you'd need to edit your layout PHP file to use it:
http://bootsnipp.com/snipps/product-or-company-header
A combination of these things is this follow link. Bootsnipp is a place where people share nice little "chunks" of websites based on Bootstrap HTML. Here's a footer, similar to what you would see on many websites:
http://bootsnipp.com/snipps/company-footer
Mary had the clever idea of adding a customisable footer to the Clean theme, to which you can add any HTML like. If you take the above Bootsnipp HTML and paste it into the correct place in the theme settings you get a fairly pleasant looking, and relatively easily customisable way of creating a footer that suits your own site. (Note also that it collapses into vertical list on iPhones etc.)
The example actually overcomplicates things more than it needs to (e.g. there's no need to set the width via a style tag), but it's still a fairly simple way to customise your Moodle without needing to edit files etc.
This one is also fairly simple and may suit your theme, though this time you'd need to edit your layout PHP file to use it:
http://bootsnipp.com/snipps/product-or-company-header
Currently Moodle's Bootstrap theme requires you to use the original .less files, add the bootswatch ones to change some settings and add some extra css then compile to get the output CSS file.
I believe that Bas Brands did a talk about the best way to do this at the recent iMoot. Possibly there are slides available? Ah, here is a very comprehensive blog post about his talk:
http://basbrands.nl/blog/2013/05/21/building-with-bootstrap/
You can also refer to his Bootstrap theme for 2.4 which has the files already in place for this.
And see a public demo:
http://theming.sonsbeekmedia.nl/index.php?theme=amalia
http://theming.sonsbeekmedia.nl/index.php?theme=superhero
http://theming.sonsbeekmedia.nl/index.php?theme=united
I believe that Bas Brands did a talk about the best way to do this at the recent iMoot. Possibly there are slides available? Ah, here is a very comprehensive blog post about his talk:
http://basbrands.nl/blog/2013/05/21/building-with-bootstrap/
You can also refer to his Bootstrap theme for 2.4 which has the files already in place for this.
And see a public demo:
http://theming.sonsbeekmedia.nl/index.php?theme=amalia
http://theming.sonsbeekmedia.nl/index.php?theme=superhero
http://theming.sonsbeekmedia.nl/index.php?theme=united
A more detailed post on this topic:
"About HTML semantics and front-end architecture"
by Nicolas Gallagher (who is also known for the Normalise library, which is used by YUI and Bootstrap amongst many other projects)
http://nicolasgallagher.com/about-html-semantics-front-end-architecture/
Highly recommended.
"About HTML semantics and front-end architecture"
by Nicolas Gallagher (who is also known for the Normalise library, which is used by YUI and Bootstrap amongst many other projects)
http://nicolasgallagher.com/about-html-semantics-front-end-architecture/
Highly recommended.
Possibly related sub-question: if I have a small library of theme related functions that I want to use in my theme, but might also be useful for child themes where would I put that?
For example, Bootstrap does alerts in a certain way. There's multiple renderers where I might want to use that same code. So I put it in a class and call it in my Bootstrap theme's renderers. That all works fine.
However, if someone wants to override my theme in a child theme, but still wants to do Bootstrappy things they might also want to use that function, or even slightly tweak that function so that it does something different. How do I structure things so that it's easy for them to do so?
The renderer structure seems like it's in the same area, but it also seems quite tightly tied to the idea of a page, rather than just some functions you call from a library.
For example, Bootstrap does alerts in a certain way. There's multiple renderers where I might want to use that same code. So I put it in a class and call it in my Bootstrap theme's renderers. That all works fine.
However, if someone wants to override my theme in a child theme, but still wants to do Bootstrappy things they might also want to use that function, or even slightly tweak that function so that it does something different. How do I structure things so that it's easy for them to do so?
The renderer structure seems like it's in the same area, but it also seems quite tightly tied to the idea of a page, rather than just some functions you call from a library.