After years of development and competition, open source content management systems (CMS) have proliferated and are very powerful tools for building, deploying and managing web sites, blogs and more. You're probably familiar with some of the big names in this arena, including Drupal (which Ostatic is based on) and Joomla.
As we noted in this post, selecting a CMS to build around can be a complicated process, since the publishing tools provided are hardly the only issue. The good news is that free, sophisticated guides for evaluating CMS systems have flourished. There are even good options for trying open CMS systems online before you choose one. Here, in this newly updated post, you'll find some very good resources.
he first thing to pursue as you evaluate CMS systems to deploy, including the many free, good platforms, is an overview of what is available. CMSMatrix.org is a great site for plotting out side-by-side comparisons of what CMS systems have to offer. In fact, it lets you compare the features in over 1200 content management system products. Definitely take a look. This site also has a good overview of the options.
Content management systems are boring until you have to use one. You can install a little Drupal or WordPress, pick up some Squarespace, or just dump to Medium, the graveyard for posts about protein shakes and VC funding. But what if you could roll your own CMS? And what if you made it really cool?
That’s what Cory LaViska did. LaViska is the founder of SurrealCMS and has been making it easy to edit stuff on the web for nine years. Rather than build and sell an acceptable CMS, however, he took all of his best ideas and made a far better CMS. And he made it open source and called it Postleaf.
The biggest mistake is bigger than Drupal: They don't consider it at all. This isn't a platform thing, it's a problem that is endemic to the web. Big companies get dragged into accessibility via legal threats. Small companies don't even think about it. Just the act of raising accessibility as an issue, and asking your team to keep it in mind throughout the design and development process is a big deal. You have to start somewhere.
I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3.
A veteran of the web publishing and sports media industries, Jeff Diecks leads professional services and client delivery at Mediacurrent and is an active member of the Drupal community. Jeff also organizes events for his local Louisiana Drupal Users Group and Drupalcamp New Orleans.
I was able to catch up with Jeff ahead of DrupalCon New Orleans 2016, where he'll share insights on site building tools to solve common university needs.
Back in the day, I was working at a large nonprofit in the "webmaster's office" of the marketing department and was churning out custom PHP/MySQL forms like nobody's business. I finally got weary of that and starting hunting around the web for a better way. I found Drupal 6 and starting diving in on my own. Years later, after a career shift and a move, I discovered the Portland Drupal User Group and landed a job as a full-time Drupal developer. I continued to regularly attend the meetups in Portland, which I found to be a great source of community, friendships, and professional development. Eventually, I landed a job with Lullabot as a trainer creating content for Drupalize.Me. Now, I'm managing the Drupalize.Me content pipeline, creating Drupal 8 content, and am very much involved in the Portland Drupal community. I'm this year's coordinator, finding and scheduling speakers.
Today, one in 40 global websites are now run on Drupal and almost 40,000 people around the world actively contribute to it, making it one of the largest open-source communities.
Max Bronsema is the chief architect and director of web communication technologies for Western Washington University (WWU) in Bellingham, Washington. Previously, he was the lead Drupal architect at the university, leading a small student team developing innovative Drupal solutions for the public-facing sites at WWU.
Can we save the open web? Dries Buytaert, creator of Drupal, talked to a group during SxSW Interactive about how he began the content management service (CMS) Drupal in his dorm room in 2001. Today, Drupal powers 1 out of 30 websites in the world. Technology has changed a lot from 2001 to 2016. Back in 2001, only 7% of the population had Internet access, there were only 20 million websites, and text messaging was just introduced. So, when we talk about the open web what we're talking about is people having choice and transparency in their options.
Nearly five years ago, my team at GeorgiaGov Interactive began a journey to migrate our enterprise web platform (hosting over 50 state agency websites at the time) away from a self-hosted model with a proprietary content management system to Drupal 7 and a cloud hosted environment. We were the first state to make such a bold shift, but we weren't the last.
Boston-based open source company Acquia has announced that it will provide US$500,000 to the community around the content management system Drupal, in order to help in the development of modules that add additional functionality.
Drupal is free software developed originally by Belgian Dries Buytaert (seen above) and released under the GNU General Public Licence. The Acquia move has been prompted by the rapid take-up of version 8 of Drupal and the funding will go towards modules for this version.