As was mentioned earlier this week, today is the day Drupal 8 becomes official and is released for public consumption. The last time CMS Report was given the opportunity to talk about a major Drupal release was in January 2011 with the release of Drupal 7. If you thought the three year waiting period from Drupal 6 to Drupal 7 was long, waiting nearly half a decade for Drupal 8 certainly feels like a lifetime in the world of content management. During this cycle of development, Drupal's own open source community has evolved and its developers have introduced hundreds of changes into the Drupal content management platform.
Since the release of Drupal 7, the Drupal community considered not only how they could influence the content management industry, but has also looked outward to consider how the best practices of developers, designers, and publishers could influence Drupal's own to build a better Drupal. Dries Buytaert, founder and project lead of Drupal, in a blog post remarked that "Drupal 8 has been a big transformation" for the open source community.
The pace of change in the digital world has become dizzying. If we were to ignore these market forces, Drupal would be caught flat-footed and quickly become irrelevant.
I admit it. When looking at the calendar my eyes have been focused on November 19, 2015. This is the date that Drupal 8, under development since 2011, is expected to be released. But for Drupal 6 users, the beginning of Drupal 8 also marks the beginning of the end for Drupal 6 support. Announced on Drupal.org, Michael Hess writes that Drupal 6 will reach end-of-life on February 24 2016.
As announced in the Drupal 6 extended support policy, 3 months after Drupal 8 comes out, Drupal 6 will be end-of-life (EOL).
On February 24th 2016, Drupal 6 will reach end of life and no longer be supported.
What this means for you:
- Drupal 6 will no longer be supported by the community at large. The community at large will no longer be creating new projects, fixing bugs in existing projects, writing documentation, etc. around Drupal 6.
- There will be no more core commits on Drupal 6.x to the official tree. (see What if I have a Drupal 6 site still)
- The security team will no longer provide support or Security Advisories for Drupal 6
All Drupal 6 releases on project pages will be flagged as not supported.
- At some point in the future update status may stop working for Drupal 6 sites.
The policy of the Drupal community is to support only the current and previous stable versions. (When Drupal 8 is released, Drupal 7 will continue to be maintained but Drupal 6 be marked unsupported.) This policy was created to prevent Drupal's core and module maintainers from having to maintain more than two active major versions of Drupal.
Three years ago, CMS Report made the jump from Drupal to the Agility CMS featuring its Magazine Publishing Suite. Since then, I've had the opportunity to see Agility's software evolve including improved delivery in the mobile space through responsive web design. While gradual improvements were made in the CMS, probably the biggest change for Agility Inc. was in late 2013 with the appointment of their new CEO, Jonathan Voigt. When Jon was appointed CEO he promised a refocused vision for Agility that would provide better products and improved services for Agility's paying customers. This autumn, Agility fulfills that promise as it rolls out a significant rebuild and redesign of the content management system's interface.
Agility has announced that they have started pushing out the new version of its popular web content management solution. Besides the interface improvements, the new version of Agility CMS also introduces a new Dashboard feature as well as significant improvements in software performance and task workflow.
"This a huge step forward for Agility CMS. The legacy content manager was built out 8 years ago, and it served us and our customers well. This new, upgraded version provides the same user-friendly experience – but it’s sleeker, faster and provides more value to all that login to the platform,” Jon Voigt, CEO of Agility CMS, said.
Over the weekend, the core developers for CMS Made Simple, an open source project, announced the release of CMSMS 2.0. While not a complete rewrite, CMSMS 2.0 is a significant re-factoring and renewal for the content management system. Many of the changes involved are focused on giving the web professional an easier and simpler editing experience within the CMS.
In the announcement, Robert Campbell further explains how CMSMS 2.0 came to a final release.
After a very, very long wait (around three years for this attempt alone) and a great deal of effort, we are overjoyed to announce the public release of CMSMS 2.0. The next generation in the evolution of making managing web content simple.
CMSMS 2.0 has been a long and tiring uphill war, with many large and small battles; some of which we won, and some of which we lost. Throughout our battles the Dev Team has always remembered our primary goal and tagline: "Power for the Professionals, Simplicity for the End Users." This means that the professionals have a standards-oriented, powerful engine to build websites and web based applications, and the system still remains simple and fast for the average non-technical user to be able to manage the content of his or her website.
The primary focus for the developers along with feature changes of CMSMS 2.0 include:
- Significant improvements in the editing experience:
CMSMS 2.0 includes a new WYSIWYG editor, an improved and dynamic file manager, and a brand new content managing module. Content editors can now easily find, control and edit thousands of pages without concern that they will accidentally erase somebody else's work (that's important!).
When it comes to posting online about my own personal misfortune, I have one simple rule. Don't talk about it until you can tell the story with a sense of humor. When it comes to a visible personal injury the first question you inevitably have to answer is, "What happened to you"? Three weeks ago, I was in a bicycle accident where I landed on my shoulder and broke my clavicle (collar bone). I'm better now but I'm still wearing an arm sling. My first attempt of bringing humor to the situation was on Twitter.
I'm starting to think exercising is hazardous to your health. Visiting the doc.
— Bryan Ruby (@MrBryanRuby) August 10, 2015
In the past, I've joked with my wife that every time I've had a physical injury it when I'm doing some type of physical exercise. My accident happened during a 26 mile bike ride on the bike trail when a skateboarder accidentally or on purpose (I want to believe it was the former and not the latter) put his skateboard in front of my bicycle wheel. I flipped over on the bike, landed on my shoulder, and by the next day found that I had broke my collar bone. The doctor said to expect my arm to be in a arm sling for two to six weeks. It took me almost a week to admit the specifics of my injury online. This time with a little less humor on Twitter.
With a broken clavicle (collar bone) I'm finding it difficult to be at the keyboard for any length of time. Getting frustrated...
— Bryan Ruby (@MrBryanRuby) August 16, 2015