We are finally here! A big milestone has been reached with the branching of Sakai 12.0. What is a "branch"? A branch means we've taken a snapshot in time of Sakai and put it to the side so we improve it, mostly QA (quality assurance testing) and bug fixing until we feel it is ready to release to the world and become a community supported release. We have a stretch goal from this point of releasing before the end of this year, 2017.
(posted on behalf of Jolie Tingen, Learning Technology Analyst, Duke University)
In the last few years, Sakai’s user interface and user experience has improved significantly. The community’s effort to make Sakai a responsive and easy-to-use application is evident in the latest release. Improved navigation, streamlined workflows, and a modern interface are all noticeable improvements in Sakai 11. Yet, these improvements have not been documented in a style guide for Sakai.
To address this gap, Duke University is partnering with the Sakai Community to develop an updated style guide for Sakai.
(posted on behalf of Matt Clare, Brock University, Chair of Sakai Accessibility Working Group)
Thursday, May 18 2017 is Global Accessibility Awareness Day.
Sakai should have a positive impact on all who encounter it, a key part of this goal is how accessible Sakai is.
Today is Global Accessibility Awareness Day (GAAD) and part of GAAD is building awareness of what we all can do to promote access for, and inclusion of, people with different abilities.
Sakai has a good history of accessibility but recent versions of Sakai have not been released with a thorough review of the accessibility and to what degree it meets recognized international standard like the WCAG 2. I’m pleased to share that thanks to community efforts in fundraising over $61,000 and 60 hours of development work Sakai’s accessibility has been reviewed by a recognized accessibility reviewer, SSB Bart, and our plans are to deliver Sakai 12 with an accessibility compliance statement.
Even though we have release notes , I was wondering if it would be helpful to make a blog post about our maintenance releases. Also motivated by the fact that in 11.2 we had to turn off one of the new features of Sakai 11 for the mobile view, and thought that would be important to communicate. This blog post is really about both Sakai 11.1 and Sakai 11.2 since combined there are 350 improvements since the 11.0 release on 23 July 2016.
We are pleased to announce a SakaiCamp un-conference in Orlando Florida January 21 - 25, 2017.
SakaiCamp is an informal gathering that is focused solely on Sakai. The people who show up decide on the topics of discussion, and in some cases, working sessions. Attending we get a nice mix of developers, instructional designers, managers, etc. And we have break out sessions so that developers can talk tech and users can talk function. And we all come together in full group debriefs and discussions.
The University of Virginia has released a short promotional video highlighting the power and potential available in its instance of Sakai, as well as the role of its instance in expanding the university’s mission into the digital world.
We are so happy to share with the community that the University of Murcia's Sakai instance was upgraded to Sakai 11.1 on September 15th, 2016.
Sakai 11 has had a facelift! The new version of Sakai supports a responsive design meaning that it can be used on any device with any screen size, any place, anytime, anywhere! The new release represents one of the biggest, if not the biggest, improvement in Sakai in years. Sakai 11 is, of course, still 100% open source and its redesign was informed by UX testing with real users and delivered by the worldwide Sakai community.