A more feature rich Joomla! has just been released.
This week, the Joomla! Project announced the release of Joomla 3.7. This new release in the Joomla! 3 series features over 700 improvements to the popular content management system, including many features which "make administration of Joomla! Web sites easier and more feature-rich, as well as several security updates". The following are the seven biggest new feature improvements I found in Joomla 3.7.
1) Custom Fields
Administrators now have the ability to add Custom Fields to their articles, users, and contacts. Extension developers can also use this feature within their own custom Joomla! Extensions. With Custom Fields, there are now 15 different field types that can be utilized to structure more complex content entry systems which in-turn allows content authors to easily enter their data in a standard manner and display it consistently for site visitors.
2) Multilingual Associations Component
The Multilingual Associations Component allows administrators and authors to easily translate content from one single, unified interface.
3) Improved Workflow
A category, article, or menu item can now all be created in one step from within the menu manager.
4) New Backend Menu Manager
Intended for sites where multiple people are accessing the Backend/Admin-side of the site is the ability to easily manage the admin menu with the new Backend Menu Manager. Now one can can create custom menus for the Backend just like you can for the Frontend. This feature allows site administrators to control which users can see what admin menu options
5) TinyMCE Improvements
More can now be done with the included rich-text editor including new buttons to easily add menu links and contacts.
Niels Hartvig recently posted that Umbraco 7.4 has been released. With much focus on improving the user experience, this new version of Umbraco is being subtitled as the "Content type editor update".
Features and improvements highlighted in this update includes:
- New content type editor
- Some UX polish + documentation
- Media library improvements
- Grid polish
- Password for user panel (no dashboard)
- Models Builder
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.
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!).
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.
Thank you so much to Aaron for sharing your personal journey with all of us. It’s been a long journey, and a difficult one. You and your family are all in our thoughts.
A couple years ago, if you would have asked me what I thought about Joomla! I would have told you I think they've lost their way. Their community of developers seemed to be searching on how best to innovate and take risks with a well established stable content management system. I feared that the open source group was stuck looking back and that all we could expect was dull incremental changes to their CMS. Despite the fear, I knew better. Open source communities have a way of reevaluating their priorities and creating spectacular results where you least expect them to do so.
In the second half of 2012, we started seeing something "new" from Joomla! As they started to embrace displaying and managing content on mobile devices, they also embraced the idea that not all core development has to be confined "in-house". With Joomla 3.0 they became the first major CMS that included the Twitter Bootstrap framework to help make their CMS better in the mobile arena. This week, Joomla! has turned the tables and now offers the opportunity for you to allow their framework to make your own web applications better. With Joomla Framework 1.0, Joomla! has proven that they're much more than content management but also a platform for developers to spread their wings.
The Joomla Framework is a new PHP framework (a collection of software libraries/packages) for writing web and command line applications in PHP, without the features and corresponding overhead found in the Joomla! CMS. It provides a structurally sound foundation that can be adapted and extended. This new initiative enables developers to more easily combine features from the Joomla Framework with features from other open source frameworks as they custom-build their own app or CMS.
I do not know when it exactly happened, but a number of years ago I decided to become a pacifist. I am a pacifist that is in the war of open source versus proprietary. In my opinion, the debate over licensing and software development processes is only mildly interesting as it is the quality of the end product that matters to me most. I walk the fine line of being an advocate for open source and a defender of proprietary software. Admittedly I've confused a lot of people that have chosen to take sides in this war. However, there is always room for reasonable civil discussions of any topic when new data and new perspective is given. This is perhaps why within the past week I enjoyed reading a commissioned study conducted by Forrester Consulting on behalf of Acquia that shows the value of open source without necessarily attacking the value of proprietary software.
The independent study conducted by Forrester is titled “Is It Time To Consider Open Source WCM For Digital Experience?”. Given that the study is being promoted by Acquia, an open source Drupal company, it shouldn't be surprising to you that this paper highlights the benefits of open source web content management systems (WCM). However, the author of the paper does this in way that that doesn't also dismiss the value of proprietary systems. This paper is an invitation with business reasons given for IT shops that for one reason or another remain proprietary to start considering using open source solutions. That soft sell in my opinion will win over more customers than the doomsday ideologies we often hear from both open source and proprietary proponents.
Two years ago I began a process to consider how best to evolve CMSReport.com beyond where it is today. I've known for some time that I needed to take some risks, get out of my comfort zone, and perhaps change how I maintain and run the site. Given the opportunity and in the spirit of taking risks I've decided to no longer run CMS Report on Drupal. That's right, after running this site on Drupal for more than six years on Drupal I've decided to use another content management system.
For those that don't want to be left hanging, I mention the CMS I've chosen to run the upgraded site on toward the end of this article. In a separate article I'll get into the specifics for why I decided on this other CMS and discuss the strengths and weaknesses of both information systems.
My primary objective with this post isn't to talk about another CMS, but instead to focus on Drupal and reflect on how much I owe a debt of gratitude to the Drupal community. I also want to make it clear that my decision to use another CMS is not a reflection of my opinions regarding Drupal. On the contrary, I have a number of past and future projects where Drupal remains the solution for my content management needs.
Last weekend, digital agency water&stone, released their 2011 Open Source CMS Market Share Report. I consider this report one of the few non-bias and detailed surveys that come across my desk each year. The report isn't perfect, but the report does help give a good snapshot on the state of who's who in the world of open source content management systems.
You are most definitely going to want to take a look at the details in the report. The findings in this year’s report were based on a survey of more than 2,500 CMS users and additional research into a wide variety of measures of market share and brand strength. I'm still combing through the survey and taking note of the interesting individual nuggets of information that can be found in the results of the survey.
Not surprisingly, the report confirms the ranking position of open source's three most dominate Web content management systems in the market. The press release itself summarizes the results this way:
PHP-based systems WordPress, Joomla! and Drupal continue to dominate the web content management space. But, while the Big Three remain unchanged from last year, the Report concludes that WordPress retains a clear lead in the face of decreasing competition from Joomla!.
The decreasing competition from Joomla! can be seen most noticeably in the decrease of installations reported by the survey respondents in 2011 compared to 2010. The survey does note that this dramatic drop is likely due to the Joomla! community aggressively promoting the survey last year. This year, the promotion efforts were not coordinated and less influential. I only point this out because this is an example of where the report isn't "perfect" via inconsistencies in the yearly survey sample introducing a margin of error in the trend comparisons.