Synopsis
Time marches on and with that time we seek to improve upon what we have created. So has been true of the Bootstrap framework ( getbootstrap.com ), first finding its way to Moodle in version 2 via a contributed plugin ( moodle.org/plugins/theme_bootstrap ) by Bas Brands, David Scotson with contributions by others. Then it became a core base theme, ‘Bootstrapbase’ alongside the existing ‘Base’ theme with a child theme of ‘Clean’ in Moodle 2.5. In Moodle 3.2 the Boost theme arrived encapsulating an alpha version of Bootstrap V4. Between this time the contributed ‘Bootstrap’ theme was updated to Bootstrap V3 and a few themes like my Shoehorn theme ( moodle.org/plugins/theme_shoehorn ) depended upon it either directly or indirectly. Finally in Moodle 3.5 Bootstrap V4.0.0 stable was applied (the current stable version of the framework is 4.1.3).
This passing of time and the maintenance cost of maintaining two themes sharing the same framework at different versions has given rise to a new core plan for themes. There are Moodle trackers for this but the principle read and discussion can be found on the ‘Themes’ forum: moodle.org/mod/forum/discuss.php?d=373899 – and this is what this post is really about.
Link
Post link on eLearningWorld: To Boost or not to Boost, that is the question .