Pressbooks LTI Provider plugin ready for testing!

Good news for everyone using Pressbooks in the education sphere: Over the last couple of months, we have been working on developing our own LTI Provider plugin, which is now almost release-ready!

The LTI Provider plugin will allow institutions to embed Pressbooks content in their Learning Management Systems (LMSs) using the LTI standard.

In terms of features, the LTI Provider plugin will provide the same set of functionalities as Lumen Learning’s Candela plugin.

Basic features include:

  • Creation of manual LTI configuration
  • Automatic configuration via LMS
  • Common Cartridge exports (versions 1.1, 1.2, and 1.3)
  • Deep Links

The plugin has been available for some time on our GitHub repository, and we have had valuable input from the Pressbooks open source community.

We encourage you to give the latest version a test and send us your feedback via GitHub!

Documentation for the Pressbooks LTI Provider plugin is available here:

Book Themes, Part 2: What’s Buckram?

In the early days of Pressbooks, each book theme was pretty much built from scratch, using trial and error (and adapting work that went into our first book theme, Luther). We used vanilla CSS for all book themes until Pressbooks 3.0 was released in December 2015, which supported themes built using the SCSS variant of SASS.

Our initial goal with adding SASS support to Pressbooks was limited in scope. We needed to support non-Latin character sets (Ancient Greek, Biblical Hebrew, Chinese, Japanese, Korean, and many more) but we wanted to keep book export sizes small by only bundling these additional fonts when they were needed. So we added a new theme option (Global Typography, now known as Language & Script Support) which allowed users to select additional non-Latin languages for their book which would be dynamically imported into their stylesheet during export.

After the release of Pressbooks 3.0, we realized the potential of SASS and SASS variables for allowing users to customize various aspects of their book’s theme which until then we had been forced to hard-code on a theme by theme basis (or insert by searching and replacing placeholder strings in vanilla CSS). Clarke was the first theme we converted to our new theme structure, now known as Buckram. When we released the rebuilt Clarke theme alongside Pressbooks 3.6.0 in June 2016, users gained access to a host of new PDF theme options, allowing margins, running content, and more to be customized via a settings page.

We wanted to bring this flexibility to our other themes, and since the release of Clarke 2.0 we’ve been slowly working towards that goal with Buckram. It’s been in the works for a couple of years now, but only over the past six months have we been able to dedicate significant time and developer resources to bringing it into a stable 1.0 release (coming early July!).

So, what is Buckram? Last September at our team retreat in Montréal, I demoed it to our friends at the Rebus Foundation, and Boris nicknamed it “Bookstrap”. That’s kind of what it is; like Bootstrap, Buckram is a set of styled components for book theming, with corresponding markup, that can be customized with SASS variables. It’s raw material for our book themes, so we named it after buckram, a material of physical bookbinding.

Here’s how Buckram works, in brief. A book theme imports Buckram’s component files and default variables via SASS imports, and then overrides specific variables with custom values.

Let’s say you’d like to customize the way your theme displays blockquotes. They’re found within the blockquotes partial and the corresponding variables file. If you’ve started by scaffolding a book theme with our command line tool, you’ll find the following file in /assets/styles/components/_elements.scss:

// Elements

// Override variables above this line, using the !default flag to allow further overrides.
@import 'variables/elements';

// Add custom SCSS below these imports and includes.
@import 'components/elements';

Let’s say you want to add a left border and padding to your blockquotes. You can just do this, with reference to the source variables file (or the docs):

// Elements

$blockquote-padding-left: 1em !default;
$blockquote-border-left-width: 2px !default;
$blockquote-border-left-style: solid !default;
$blockquote-border-left-color: #333 !default;

// Override variables above this line, using the !default flag to allow further overrides.
@import 'variables/elements';

Now the values you’ve supplied will override the defaults from variables/elements, giving your blockquotes a padding-left value of 1em and a border-left value of solid 2px #333. We take advantage of the SASS !default flag, which lets a variable that comes before another variable override it. In this example:

$color: red;
$color: blue !default;

The $color variable will be set to red, as it precedes a variable flagged with !default.

Using !default flags for the custom values in a theme, as demonstrated above, means that we can add theme options to allow further overrides that users control. So a theme may have a default font for body text, but in the future we’ll be able to let users customize body text by selecting an alternative typeface from a dropdown, overriding all rules where that font is referenced by changing a single variable. Moving our themes to Buckram will make the theme customization experience for Pressbooks users flexible in ways that we’ve always dreamed it would be.

So far, we’ve got three open source themes built with Buckram (Clarke, Jacobs and McLuhan). The newest member of our dev team, Daniel Fernandes, has been hard at work converting our backlog of premium themes to Buckram, and we’ll be releasing them over the coming months. We also will be expanding our documentation for Buckram, and improving the Pressbooks CLI tools for building new Buckram themes so that all Open Source users can benefit from the work that’s gone into our theme structure. We’re excited for what Buckram will let us do, and we welcome your feedback, bug reports and code contributions.

Q3 Roadmap Preview

Q2 is drawing to a close, and we managed to get a couple of big-ticket items out the door:

We didn’t manage to finish as many roadmap items as we expected, but here’s what we crossed out:

  • ✔ Improve textbox and table styling across all formats
  • ✔ Finalize new theme structure and begin migrating themes
  • ✔ Add support for Common Cartridge import and export

We’ll be going forward with a simplified list for Q3, with only a couple of big items. We want to focus Q3 on general housekeeping tasks such as UX improvements and backend optimisations:

Big projects

  • Provide basic support for Shibboleth SSO
  • Add new shortcodes to facilitate authoring
  • Begin researching analytics solutions

Housekeeping items

  • UX improvements to the webbook Table of Contents
  • UX improvements to the Export page
  • Other backend and frontend UX improvements
  • Accessibility improvements
  • Ongoing theme conversions

If you’re planning on working on any of these items or would like to collaborate, please let us know in the forums or tweet @pressbooksdev!

Sprint Preview: June 25 – July 6

This sprint, we’ll be working on:

Also, we’ll be off both Mondays this sprint, as it will be Québec and Canada’s national holidays, so the Open Source call will happen on Tuesday, July 3.