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:
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.
On March 24, 2015, the Drupal community lost Aaron Winborn who was diagnosed with ALS a few years ago. In honor of Aaron, the Drupal Association and Angie Bryon recently announced the Aaron Winborn Award. The announcement reads as is:
Announcing The Aaron Winborn Award to honor amazing community members
In honor of long-time Drupal contributor Aaron Winborn (see his recent Community Spotlight), whose battle with Amyotrophic lateral sclerosis (ALS) (also referred to as Lou Gehrig's Disease) is coming to an end later today, the Community Working Group, with the support of the Drupal Association, would like to announce the establishment of the Aaron Winborn Award.
This will be an annual award recognizing an individual who demonstrates personal integrity, kindness, and above-and-beyond commitment to the Drupal community. It will include a scholarship and stipend to attend DrupalCon and recognition in a plenary session at the event. Part of the award will also be donated to the special needs trust to support Aaron's family on an annual basis.
Thanks to Hans Riemenschneider for the suggestion, and the Drupal Association executive board for approving this idea and budget so quickly. We feel this award is a fitting honor to someone who gave so much to Drupal both on a technical and personal level.
Spring brought to South Dakota plenty of rain. The lawns are green, the flowers are in full bloom, and it seems we can't go beyond a couple days without a rain shower or thunderstorm. While water is usually plenty for my city, we do things smart around here and restrict water usage for our lawns year round. It's not uncommon in my part of the country to see the weather pattern quickly change from wet to dry. What once was green can turn brown in a hurry.
If you want a green yard when summer is in full swing, you will do best to respect the water restrictions and program your sprinkler controller the smartest way possible. Here in my city, watering lawns is not allowed during the hours of 12 p.m to 5 PM. Homeowners with even-numbered addresses may water lawns on even-numbered calendar dates and users with odd-numbered addresses may water lawns on odd-numbered calendar dates. Last summer though, my traditional sprinkler controller decided this responsibility was too much of a burden. The failing controller couldn't even keep the time of day correctly yet alone maintain an ideal watering schedule. So this May, I replaced my failing controller with Blossom's Smart Watering Controller in hopes of a greener lawn and a better sprinkler system.
Last week, we started a conversation on The ez Publish Show hosted by Netgen's Ivo Lukač. The we included Ivo, Digital Clarity's Marianne Kay and myself. The odd question that started the conversation: Did modern CMSs sacrifice good editor experience (EX) for improving customer experience?
I'm not sure how well we answered the question, but the show was an acknowledgement that while CXM may get a lot of attention these days in the CMS world, there is still plenty of room for improving the EX too. I'll let the video speak for itself, but if you prefer an overview, then you can checkout Ivo's re-cap.