Themes: UIkit

Maintained by Picture of Eduardo RamosEduardo Ramos
This theme is built from its core to work with UIkit (a framework similar to Twitter Bootstrap). It is designed to be easily customizable using an interactive visual styles manager.
205 sites
18 fans
Current versions available: 1

UIkit Theme for Moodle

  • Features a very advanced and interactive visual styles customizer
  • 3 base themes to build your site appearance
  • 2 different page layouts: the original Grid based layout and a new one based on new CSS Flex features
  • Fully responsive design
  • Support of Google fonts
  • Integrates Fontawesome 4.5 for displaying most icons in Moodle
  • A renovated Slideshow with many animations and effects, marketing spots and social networks for your site frontpage like in the essential theme
  • Many other cool features such as: login page and navigation menu customization, possibility of showing only enrolled courses in combo lists and google analytics integration

It supports Moodle 2.5 to 3.0

License GNU GPL v3 or later

This theme is based on the UIkit CSS framework version 2.24.3 (

It is inspired by bootstrapbase theme and essential theme ( A big thank you to the creators of these two themes.

Many features and settings are based on the essential theme, while others are new for this theme, specially the visual style manager.

This theme includes an advanced Visual Style Customizer to change the appearance of the whole site with a few clicks. This customizer is inspired by the UIkit customizer (

Notice: these theme is NOT an official UIkit team release.


Screenshot #0
Screenshot #1
Screenshot #2
Screenshot #3
Screenshot #4
Screenshot #5


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

Comments RSS


  • Picture of Eduardo Ramos
    Thu, Sep 10, 2015, 2:01 AM
    the theme does not support docking at all.
  • Picture of stefan weber
    Thu, Sep 10, 2015, 10:22 PM
    hi eduardo,
    does it actively surpress docking somewhere? im currently trying to add docking to it, but i fail to get the dock icons to show up, even after including dock.js from bootstrap and enabling docking in the config.php. am i missing something?
  • Picture of stefan weber
    Fri, Sep 11, 2015, 9:16 PM
    hi eduardo

    one more issue - when text is set to italic (/em) in tinyMCE, text display color is red.

    i cannot find this setting anywhere in the visual style manager - maybe this is fixable with custom css or you can tell me where this setting is?
  • Picture of Eduardo Ramos
    Sat, Sep 12, 2015, 9:33 PM
    Hi stefan,
    I never tested docking with this theme, but I guess you can add the following to /themes/uikit/config.php and see what happens.

    $THEME->enable_dock = true;

    About emphasized text with red color, this is part of UIkit base styles, but you can override it with custom CSS similar to:

    em {
    color: inherit;
  • Picture of David Walser
    Sat, Oct 10, 2015, 1:21 AM
    Adding custom CSS does not work correctly. It seems to be injected in the wrong place and get overridden. If you put "important" in it, then it will work, but that should not be needed.
  • Picture of Eduardo Ramos
    Sat, Oct 10, 2015, 1:30 AM
    Can you show an example? Custom CSS is added to the bottom of the theme stylesheet.
  • Picture of David Walser
    Sat, Oct 10, 2015, 3:12 AM
    Thanks Eduardo.

    We are trying to fix the issue in the Quiz results display where it puts a horizontal scrollbar *in the page* on the table, rather than at the bottom of the whole page, which makes it practically unusable.

    My co-worker figured out that the appropriate CSS to add to fix this is:
    #main-content-box {overflow:visible}

    and we tried adding that through the web interface in the UIKit Visual Style Manager, but it did not take effect. Adding an important in our CSS made it work. My co-worker traced through the UIKit theme code and found in theme/uikit/config.php that the code injected from the web interface gets added at the end *before* slides.css. It is not apparent what in slides.css is overriding our CSS code, but regardless, our custom CSS code should be after everything.

    Loading moodle/theme/styles.php/uikit/1444417668/all in the browser let's us see the CSS that gets generated, so we can see that an adjustment needs to be made in config.php for our custom CSS to get properly added at the very end.
  • Picture of Luckas luckas
    Tue, Oct 13, 2015, 4:10 PM
    I have a question:
    It will support Moodle v 2.9 (I have a problem with date selections with 2.9).
  • Picture of David Walser
    Mon, Oct 26, 2015, 10:07 PM
    Hi Eduardo. Did you get a chance to look at the CSS issue?
  • Picture of Eduardo Ramos
    Tue, Oct 27, 2015, 5:21 AM
    Hi Luckas, I intend to support 2.9. Can you describe the date selection problem in 2.9 and maybe create an issue in github?
  • Picture of Eduardo Ramos
    Tue, Oct 27, 2015, 5:29 AM
    Hi David,
    Slides CSS won't affect your rule.

    Your rule should overrid #main-content-box overflow, and it does for me in firefox. The only posssible problem is that #main-content-box overflow is defined twice in the code (to be fixed in next version).

    Could you inspect with your browser developer tools what rule is overriding your custom CSS if you don't use important?
  • Picture of Luckas luckas
    Wed, Oct 28, 2015, 5:17 AM
    Sí, passa al seleccionar una fecha.
    Aquí puedes ver una imagen:
  • Picture of David Walser
    Sat, Nov 7, 2015, 3:24 AM
    Hi Eduardo,

    Sorry for the delay. My co-worker is unavailable and I'm not a web developer, so I'm trying to figure out developers tools in Chrome myself. When I use what she added to config.php, in developer tools I can see the visible property she set and the CSS file listed as a separate source at the top of the Styles box. When I disable that, I don't see the CSS we added in the theme designer anywhere. If I go in the theme designer and add the !important;, then I also will see that as a separate section (different line number) and listed at the top of the Styles box. Looking at the Source file it does have it at the very bottom. It seems like it doesn't even use your custom CSS at all unless you have an !important in it. Of course, I'm trying to go back to check it again without the !important and it won't go back to how it was before (even with designer mode on and I purged caches). I remember my coworker running into this issue and I don't know how she got around it.
  • Picture of Eduardo Ramos
    Sun, Nov 8, 2015, 12:08 AM
    Hi David,
    Can you see any rules overriding your rule (when not putting !important) in the developer tools?

    If your site is available somewhere, I can help you trace the problem.
  • Picture of stefan weber
    Mon, Nov 9, 2015, 8:43 PM
    Hi David,

    not sure if that is your issue here, but i made the experience that the visual style manager does not always integrate custom CSS on the first take.

    I dont know the technical background for this, but I had to click OK at twice for most new CSS to work, and occasionally even re-loading the visual style manager site itself and then clicking on OK again
Please login to post comments