Good morning/afternoon/evening fellow Adaptors!

On the 24th May we released Framework v2.1.0 (with two subsequent 'bug fix' releases  - v2.1.1 and v2.1.2 -  and another on the way).

The headline feature of this release is that it adds the ability to allow content to be 'personalised' for the user by making the data that SCORM Learning Management Systems make available (via the data fields cmi.core.student_name and cmi.core.student_id) to be included in the course content.

This data is then made available to the course content as:

• _globals._learnerInfo.name (as stored in the LMS, typically in the format "Lastname, Firstname")
• _globals._learnerInfo.firstname
• _globals._learnerInfo.lastname
• _globals._learnerInfo.id (typically - but not necessarily! - the user's email address... varies from LMS to LMS, so consult your LMS' documentation)

Which you can insert into your JSON using Handlebars Expression Syntax* to get the Framework to replace that bit of content with the actual data when the course runs. You can see an example of this here.

Note that this feature requires v2.1.0 (or better) of the Spoor plugin as well as v2.1.0 of the Vanilla theme.

Additionally if the personalised content is to appear on the menu, you'll need an updated menu - as per v2.0.6 of boxmenu. Any custom plugins you are using will need their handlebars templates updating in order to be able to take advantage of this new feature.

Full a full list of changes in 2.1.0, see the CHANGELOG.

This release is also an important milestone in the development of Adapt as it is the final release to include any new features that include official support for Internet Explorer v8, v9 and v10. As discussed in this forum post from earlier this year, we will no longer be developing any new functionality for IE8/9/10 - so v3 of Adapt will require IE11 as a minimum. However, we will continue to issue 'bug fixes' for v2 of Adapt for the next 6 months, after which we will review whether we should continue to do so or not.

Over the next couple of weeks we will be imposing a 'code freeze', during which time we will get as many outstanding pull requests in the core plugins merged and a final 'v2' version of each released.

During this time, we will prepare for v3 release of the Framework and all core plugins. At this stage, the changes in v3 are not expected to be extensive, it's more of a 'symbolic' release that will involve dropping some things specifically related to supporting older versions of IE - such as removing v1 of the JQuery library. Some of the plugins may not actually change at all save for the bump in version number.

Finally, as from now we are adhering properly to the Semantic Versioning system of versioning - up to now we've been changing the last digit in the version number whenever we do any kind of release when really that should indicate a release that only contains bug fixes and therefore no new features. A release that includes new features will now be reflected with a change in the middle digit of the version number.

* A handlebars expression is a {{, some contents, followed by a }}