After spending most of my years years in grade school working hard on experimental science fair projects and not receiving a ribbon, I finally gave up and wrote a "non-experimental" paper on the history of computers in the eighth grade. Despite the paper being weak even for eighth grade standards, I finally won a ribbon (third place) in the school science fair. Remember, this was the early 1980's and everyone was still fascinated with the then new concept of computers entering "everyday" life. Why am I going down memory lane? Well I came across an article on the 60th anniversary of ENIAC [via news.com, broken link] the "first" computer built which of course was mentioned in that paper of mine some 25 years ago.
Over the years, I've made it an unwritten policy not to sensationalize bug fixes and security vulnerabilities in content management systems. While there may be great interest in such stories, I believe such stories have a tendency to cause more harm than good. When sensationalized, such articles tend to cause customers to address security concerns with emotion instead of logic which is never a good thing. So, when the security vulnerability known as "Drupageddon" broke and Drupal developer Bevan Rudge posted "Your Drupal website has a backdoor", I knew this story was going to eventually reach mainstream media. In the meantime, I've been struggling on how best to write this article and what story need to be told.
Not long ago, my wife retired from the Air National Guard after having previously served in the U.S. Marine Corps. With 24 years of military experience, those that serve are almost always bound to walk away with a story or two to tell. This is one of those stories. In January 2006, Karen was given the opportunity to fly in the backseat of an F-16 (General Dynamics Fighting Falcon). Below, in her own words is what Karen experienced during that flight. She originally wrote this on our family blog that we're shutting down, but I felt compelled to make sure her story lived on within the contents of this blog.
Since retirement, Karen has become an accomplished photographer and is currently employed by a local capital investment group.
Last month, the Board of Directors for the Content Management Professionals announced the ending of CM Pros. The decision to close down the organization was evidently made by the Board in Summer 2014.
A couple years ago I joined CM Pros, paid for membership, never got billed, and never heard back from the organization. Knowing that some good people were involved in the organization told me that they were facing an uphill battle. The battle for an organization to have identity and play a role in the industry they wish to advocate.
The creation of CM Pros dated to the early 2000s. The organization was originally designed to unite professionals in all facets of the content management world.
In the years since, that world fractured and subdivided considerably, and other organizations emerged to serve the needs of the resulting sub-audiences. In particular, the emergence of the "content strategy" segment of the industry subsumed a large portion of the audience that CM Pros was originally intended to represent.
Given that the audience had become broad and fractured, the concept of a "content management professional" became too vague to effectively support. Thus, the Board determined that the organization had run its course and come to a natural end.
The LinkedIn group is still available, though it no longer represents any formal organization. It is unmoderated and open for unrestricted membership.
Although the CMS Pros didn't play a significant part in my content management endeavors, I'm nevertheless a little saddened by their departure. I understand the difficulties of advocating the technical side of content management when the more glitzy marketing side of the house is talking content strategy. But this isn't the cause of my sadness, it's my nostalgia for the days professional organizations had real value to people like you and me.
A few months ago, I had a problem. After eight years of non-stop writing, I found myself exhausted of all enthusiasm to blog. Let me tell you, it's a sad day in Web City when an advocate for content management systems has no real desire to author new content. I was also questioning in this age of "always on" social media whether the traditional blog had lost value not only to me but my readers. If content is no longer king, why should I spend so much effort creating new content? So as summer approached, I decided to take a break from blogging.
At the beginning of my sabbatical I made a secret promise to myself. If at the end of three months I found no value in blogging, I would call Agility to say it's time to shutdown CMS Report. I was prepared to resign myself to writing only an occasional post on Google+ (which "experts" claim no one reads) or on my personal blog (which I know nobody reads). If I did this, would I really miss CMS Report? Would the readers miss me if I was no longer blogging? On more practical terms, do I really need to blog in an era where Facebook, LinkedIn, Google+, or Twitter is available to me?
Honestly, three months ago I had hoped to find that blogging no longer has value. It would have been a revolutionary moment and raise the eyebrows of my peers. I was hoping to shock the world on my "discovery" that blogging didn't matter. Alas, after three months of not blogging, I've found that I will be given absolutely no opportunity to shock and awe. To my surprise, I've found that blogging still matters. Here is what I discovered...
So I'm halfway through my three month sabbatical from blogging and I get an email from my good friend, Shaun Walker. For those that don't know Shaun, he's the CTO and co-founder for DNN Corp. You know, the guy that started DotNetNuke. To make a long story short, Shaun wanted to remind me that the DNN community recently released 7.3 which focuses on platform performance. Shaun thought it would be a good idea to mention the release to readers here at CMS Report. Given that this was the man that identified wayback that the future of content management systems was in cloud, mobile and social media...it is difficult for me to ignore such requests.
WordPress 3.9 has been released with a number of refinements that WordPress hopes you'll "love". The changes and new features are solid but perhaps not as many as we've come to expect given past WordPress point releases. Some of the new features that can be found in WordPress 3.9 include improvements in the media editing experience, gallery previews, and live editing of widgets and headers.
Last month, CMS Report celebrated eight years of providing stories to readers focused on content management systems. Over the years, I've told you how grateful and even surprised I am of the success CMS Report has seen. All true, but for fear of sounding ungrateful I've never acknowledged the negatives of blogging over such an extended period of time. Today, I'm acknowledging the costs and the need to take a break from my routine of waking up before sunrise and going to bed late to maintain the site. Starting today, I'm taking a three month sabbatical away from blogging here and at CMS Report.
CMS Report will still be publishing articles from our contributors during my sabbatical, but you likely won't be seeing any articles written by me. I still plan on continuing working as editor but my office hours for the site will be reduced. I'm doing all this simply because I have responsibilities to the "day job" and myself that are begging for higher priority. In the draft for this article, I originally provided three reasons that I'm doing this sabbatical but deleted them from the published article. My reasons for taking such a break are not important but only the outcome. The end result is CMS Report will be fine without me and will likely be a better website as a result of my sabbatical.
So I end this article by simply saying: see you on the other side!