Skip to main content

· One min read

The Morea team is delighted to announce the release of Version 3.1. This release adds a number of useful new features to Morea, including:

Many users might decide to wait to obtain these features until the next time they create a Morea site. If you want to upgrade an existing site to Version 3.1, then we provide guidance in the Morea User Guide Chapter on Updating.

Have fun and let us know if you run into problems.

· 3 min read

The Morea team is delighted to announce a new major release of the system. This release should be mostly backward compatible with existing Morea instructor content, though there are extensive changes (and simplifications!) to the way sites are developed and managed.

Summary of changes

Here is a summary of the changes from Version 2:

  1. Morea 3 uses the latest releases of Jekyll (Version 4.2.0), Bootstrap (5), Bootswatch (5), FullCalendar (5.8), and ChartJS (3.5).

  2. Create a new Morea 3 site using the GitHub "template" mechanism. Templates have advantages over the previous approach of cloning: you can create a private repository even though the template is a public repository, and you can create multiple repositories in a single organization from the same template.

  3. Morea 3 sites are automatically built and deployed via GitHub Actions whenever there is a commit to the main branch. Unlike Morea 2, Morea 3 does not use custom scripts (such as,, etc.).

  4. Morea 3 does not require local management of multiple branches. Unlike Morea 2, there are no "src" and "gh-pages" subdirectories.

  5. To build and run a Morea 3 site locally, you no longer use a custom script ( Instead, you use the standard Jekyll command bundle exec jekyll serve.

  6. To publish a Morea 3 site, you no longer use a special script ( Instead, you just commit your changes and push your repository to GitHub. Morea 3 uses GitHub Actions to automatically build and publish the site whenever there is a commit to the main branch in GitHub.

  7. Morea 3 is (finally!) cross-platform: there should be no significant differences between development on MacOS, Linux, and Windows platforms.

Astute Morea users will also observe that has been reimplemented using Docusaurus. This will make documentation easier to maintain.

Migrating your V2 content to V3

Instructors who have existing Morea V2 sites for a course taught in a prior semester and who wish to build a new Morea site for a future semester will need to migrate their content. Here are the issues that have been discovered with this migration:

In Morea 3, Assessments are no longer "page fragments" (like Outcomes), but rather their own page. This leads to several breaking changes:

  • The morea_summary field is now required for Assessment pages.
  • The URL for interior linking to an Assessment page has changed. Please see this page.

Morea 3 updates JSChart from Version 1 to Version 3. As a result:

Morea 3 updates Bootstrap from Version 3 to Version 5. As a result:

  • Pages that embed Bootstrap CSS and HTML must be updated to Bootstrap Version 5.

Getting started

If you are a current user of Morea, please read the Getting Started section of the Instructor Guide and try building a new site using your old Morea files. If you run into problems, please create an issue or send an email so we can address it.

A list of known issues and desired enhancements for Morea 3 is available at

· One min read

Unfortunately, several of the Morea "cerulean" style themes (i.e. cerulean_green, cerulean_red, etc.) were loading the Open Sans font using the http: protocol. Now that GitHub uses https: by default, sites built using those themes were not displaying the Open Sans font correctly when retrieved from a domain. (Instead, the Open Sans font fails to load and the site falls back to the use of the Times Roman font.)

We just published a fix to these themes in the core repo so that Open Sans will be loaded correctly regardless of the protocol (http: or https:) used.

To get the fix, cd into your Morea top-level directory, then invoke the script to incorporate the corrected code into your local copy of these themes.

Then republish your site and all should be well.

Other themes (SuperHero, SpaceLab, etc.) did not have this bug and so you should not have noticed this problem if you were using them.

Our apologies for the inconvenience!

· One min read

We've neglected the Gallery page for quite a while, so we spent a few minutes today updating it with links to additional sites using Morea---some in quite interesting ways! Take a look and let us know if you'd like your site included.

· 2 min read

The Morea team is delighted to announce the addition of breadcrumbs as a standard feature of Morea sites.

Breadcrumbs are located just below the navbar and provide an indication of where you are in the site. For example, this page shows you are at the page "WODs: An athletic approach to software engineering", inside the "Introduction" module, which is inside the "Modules" page, which is below the "Home" page.

Upgrade instructions

To update your current Morea site to support breadcrumbs with minimal hassle, please do the following:

  1. Inspect your current master/src/_layouts/default.html. Do you add any navbar items (or anything else) to that file? If so, copy the added lines to a text buffer someplace and remember where they were located in your default.html file. If you didn't add anything, great.

  2. Invoke You will get a merge conflict in default.html. Don't panic.

  3. Edit your master/src/_layouts/default.html file. Make it identical to this default.html file.

  4. If you had added navbar links or something to your original default.html file, then edit the master/src/_layouts/core.html file to put them back in. This will look almost exactly like your old default.html file. Add back in whatever customizations you saved to your text buffer in Step 1.

  5. There is a slight chance your master/_config.html file also has a merge conflict. If so, just edit it back to your original version. (the changes are just the addition of comments.)

That's it. Now invoke and see if everything looks OK. If not, fix it. If you can't fix it, send me an email.

Now invoke to publish your cool new breadcrumbs to the world!

· One min read

The Morea team is delighted to announce the release of morea-watch.rb, a ruby script you can use instead of and which will automatically stop and restart whenever files in the morea directory change.

Morea-watch.rb was developed by Dan Port. Please check it out and let us know what you think!

· One min read

The Morea team is delighted to announce the release of morea-lintui, which combines "lint" content validation with a refreshingly retro terminal user interface (tui) for manipulating the structure of Morea sites.

Morea-lintui was developed by Henri Casanova. Please check it out and let us know what you think!

· One min read

The Morea team is delighted to announce the 2.0 release. Enhancements include:

  • Improved user interface
  • Improved calendar integration
  • Module meta-data
  • Google analytics
  • LaTeX equations
  • Eliminate dependency on Python
  • Page overviews
  • ... and much more!

Please see the release notes for details and a migration guide for current users.

· One min read

Cam Moore has contributed an include file that makes it easy for you to track the use of pages in Morea sites with Google Analytics. To learn more, see the documentation.

· 2 min read

The Morea team is happy to inform you of several updates to the user interface:

  • The themes have been updated to use the latest release of Bootstrap (3.3.1).

  • Morea themes are based on Bootswatch. We have incorporated two new Bootswatch themes into Morea: paper and sandstone.

  • In response to user request, we have created four new themes based upon cerulean: cerulean_green, cerulean_brown, cerulean_purple, and cerulean_red. If you like cerulean, but are tired of blue, try one of these!

  • To save space in the NavBar for additional menu items, we have removed the "Home" link and made the site title in the NavBar into a link.

  • Also in response to user request, we have made the icons in the module page into links to their corresponding module. Apparently everyone wants to click on them, so we might as well let them.

To use these features, set the basic-template as an upstream repository and merge into your master branch. You can do this using the morea-merge-upstream script.

Note that you may well get merge conflicts, but these should be easy to address.

If the merge conflict involves changes to the "Qux" module that you've deleted in your site, do the following to re-delete the directory:

% cd master/src/morea
% git rm -r qux

If the merge conflict involves changes to your master/src/css/style.css file, or master/src/_layouts/default.html file, then simply view those files in your editor, edit to resolve the conflict and remove the conflict indicator lines, and save your changes.

Happy course design in 2015 and don't hesitate to let us know if you encounter problems with these enhancements.