Themes: FlexiBase

Maintained by Picture of Richard OelmannRichard Oelmann
This is the flexibase theme for Moodle. It is a Bootstrap3 theme, but uses flexbox to create the layouts, rather than the bootstrap grid. This theme depends upon Bas Brands' bootstrap theme for bootstrap3.
194 sites
13 fans
Current versions available: 5

About this theme

 * @package    theme_flexibase
 * @author     2015 Richard Oelmann
 * @copyright  2015 R. Oelmann
 * @parents    Bootstrap
 * @copyright  2014 Bas Brands
 * @credits    Essential - Julian Ridden, Gareth Barnard;
 *             Elegance - Julian Ridden, Danny Wahl;
 *             BCU - Jez H, Mike Grant
 *             Decaf - Paul Nichols
 *             Many others for non-specific but vital inspirations,
 *             suggestions and support
 * @license GNU GPL v3 or later

This is the flexibase theme for Moodle. It is a Bootstrap3 theme, but uses
flexbox to create the layouts, rather than the bootstrap grid.

This theme depends upon Bas Brands bootstrap theme for bootstrap3.

The aim of the theme is to provide an experimental format for making use of the
flexbox css layouts to provide greater options for administrators and to simplify
the layout code when considering rtl languages, editing on/off, use of side-bars
and docking as well as other factors which influence the layouts. The theme allows
administrators to choose layout structures for set page layout types (standard pre
and post, 2 pre, 2 post etc) from a settings page without the need to edit theme

The theme also makes use of less compilation on the fly through its settings pages.
It has a range of colour and branding options which affect the less variables, but
also makes use of a 'CustomLess' setting in the same manner as many themes have a
'CustomCSS' (as flexibase also does).

IMPORTANT NOTE: Older versions of IE do not support any version of the flexbox

  • IE9 and older: no support - Will appear in theme as if on a small screen (mobile first layout)
  • IE10: Legacy support, supported in theme - Should appear as designed
  • IE11+: Full support

I hope you find the theme useful. Please submit any comments and feedback via the forums or any bugs via the github issues page


Screenshot #0
Screenshot #1
Screenshot #2
Screenshot #3


Picture of Richard Oelmann
Richard Oelmann (Lead maintainer)
Please login to view contributors details and/or to contact them

Comments RSS


  • Picture of Plugins bot
    Fri, Mar 20, 2015, 5:55 PM
  • Picture of Richard Oelmann
    Sat, Mar 21, 2015, 7:45 PM
    Working through the errors and notices above (noting that over 2000 of the warnings are in the js which has been directly uploaded from bootstrap).
    Please could I have some feedback on the indenting of IF statements - is the intention really that IF statements are brought back to the left and not indented inline with (and from) the parent container (div, aside, etc) as that seems to be the implication of many of those errors. If that is the requirement then I can change it, but it appears to me to adversely affect the readability enormously.
  • Picture of David Mudrák
    Mon, Mar 23, 2015, 12:23 AM
    Hi Richard. Please see for the full description of the Moodle coding style. We do not discriminate plugins just because of it, but it's always good to follow the guidelines of the open source project you are contributing to. We will get to human review of the theme code soon and will let you know more.
  • Picture of David Mudrák
    Mon, Mar 23, 2015, 12:24 AM
    BTW, there should be a way documented at on how to exclude third-party code from this automatic coding style check.
  • Picture of Richard Oelmann
    Tue, Mar 24, 2015, 12:14 AM
    Hi David, I have looked at those and tried to follow them as closely as possible (and have updated the zip file accordingly). But I can't see any mention of indenting levels of div/aside/header/etc, so I have followed what appears to be good practice in other moodle code and how I have written it before - by indenting those nested levels of div etc. That all passes the code checker. However, when the code checker finds an IF statement within that nesting, it reports that it should have 0 spaces. My question then - is this a bug in the checker? an oversight in specifications? or am I doing something wrong? I'm only asking in the hope of learning to present the code better, but in this instance, blindly following the code-checker seems counter intuitive to me and looks wrong. But as I said, if that is the intention of the guidelines I am happy to change it.
    I'll take a look at the thirdpartylibs.
    Thanks for your input David.
Please login to post comments