The Similarities between the WordPress and Drupal Communities

Before I began using Drupal I was a longtime WordPress user. I still use WordPress to power my personal websites (including this one). I love both of these open source projects and often get asked which one to use and the answer is still the same it was back in 2007. It depends on what your site is for. For most people who just need a blog or a very simple website I still often recommend WordPress. But if you need a website that requires deep permission levels, commerce, sophisticated caching, and more complex functionality, I recommend Drupal. This is just a high level recommendation and by gleaning more into a sites’ requirements it becomes easier to recommend one or the other.

The evolution of WordPress and Drupal have gone in somewhat similar directions. They both started as open source projects. The founders of both of these projects have created for profit company’s based on their open source software. Matt Mullenweg of WordPress created Automattic and Dries Buytaert founded Acquia. Both companies have also created free hosted versions, as well as fully managed business service versions of their software. Automattic created WordPress.com and Acquia created DrupalGardens. Both projects also host “Cons” and or “Camps” throughout the year were users gather together to share information and help further their respective projects. I just wanted to point out some of these similarities between both of these companies and how their for profit arms have also been instrumental in helping insure the health of their projects. Both Automattic and Acquia also do a great job of contributing back to their open source communities.

Acquia’s Mission and Roadmap Towards Improving Drupal

So back to DrupalCon. I went into this year’s DrupalCon focused on the ways that I can extend the platform to help enable people to more easily create and publish content across our websites. The areas that specifically have been challenging are setting up simple wysiwyg interfaces both for page creation and media asset management, publishing workflows for multiple members on a team, and the ability to publish content between staging and production environments. Our current methods for these have pain points and I was on a mission to find ways to improve them and look to what the future of Drupal had in store to address these issues. Beyond my needs in these areas, I also feel that they are obstacles for other people who are potential users of Drupal.

The first keynote at DrupalCon by Dries spent time focusing on weaknesses in Drupal and specifically 3 things the community needs to focus on what he referred to as “A rudimentary authoring experience”. In a nutshell this referred to to several elements that require work to improve the usability of Drupal for content creators and site publishers. Some other key takeaways from the talk are that Symfony will be used for the framework in Drupal 8 and mobile needs to be addressed much better. This seems to already be in motion as there was no shortage of talks on responsive web design at DrupalCon. Dries’ keynote was the beginning of a pattern I saw emerge from many Acquia employees that spoke on panels at DrupalCon.  They continued to echo and elaborate on Dries’ thoughts about what they need to work on to ensure the successful future of Drupal.

Click the slides below taken from the keynote

Acquia Employee Talks at Drupalcon

The first talk I saw along this theme was with Angie Byron and Chris Strahl titled “Five things we need to create an awesome experience for content creators” which focused on the following issues:

• Authoring and editing for multiple (mobile) devices
• Media management and content repositories
• Content staging and publish / subscribe models
• Page layouts and authoring tools

The talk covered how they had done research around usability among competing CMS platforms from a content creator standpoint. They showed how many of these features are handled on 4 competing systems including Squiz, Plone, CQ5, and Squarespace(v6 beta). They demo’d each of these 4 competing systems and showed where they excel over Drupal with the features and ease of site content creation and editing. In the end they plead their case to the development community to look at these systems and find ways to implement many of the usability improvements within Drupal in the near future as they ready Drupal 8 for release next year.

Another talk I attended was with Kieran Lal & Barry Jaspan. The approach of their talk was from a startup perspective on how Acquia was born and they provided many insights. They discussed the challenges encountered along with the multiple pivots from the original Acquia business model concept. They began by providing simple Drupal hosting solutions and evolved over time into a much more robust managed hosting platform for Drupal. What I liked about this talk is how Acquia has been nimble in learning what the needs of the customer base they’re trying to attract and how they’ve shifted their business model to accommodate them. Many nuggets of wisdom here for startup entrepreneurs can be gleaned from their talk. Acquia now has a very impressive list of clients that they can service much better.

Then I went to see Jay Batson do a talk that was similar with regards to the first one by Angie and Chris except it was done more as a first person view from the eyes of a site publisher. You can learn more about the profile of the “advanced content creator” role he describes here. He explains how the term “Web Engagement Management” is starting to trump CMS and is now being used to describe the overall feature-set associated with the users that fill these content production roles. These features are now essential to people who continually create and manage the content for websites. More and more it’s the marketing department that owns the responsibility of websites and are now the decision makers for web platforms. This is a switch from years ago when IT would own that decision making process. So the critical motive behind all of this is to make sure that the marketing and site content departments needs are met by Drupal moving forward.

The sum of all of these talks by Acquia left me very impressed. They are uncovering the major issues potential clients are stating as they try to sell Drupal and formulating a plan to solve them. By rallying the community around these issues, I feel that they are focused and have a plan to continue being competitive and mature based on the needs of today’s site publishers.

Other DrupalCon Highlights

The “How to build a scalable platform for today’s publishers” talk by Dick Olsson was another stellar talk I found to be extremely helpful with my goals of learning about better methods for content and site publishing. Dick provided a case study and recipe for the modules and methods he’s been using to build out sites for Al Jazeera. He needs to accommodate massive traffic and the ability to publish content quickly in a very intricate caching environment. You can watch his talk regarding those issues, but my focus was more on how he uses Workbench, Deploy, and Panels modules  to effectively manage content workflow and publishing. It was a good talk that showed how these tools can all be used in conjunction very well. I also saw a talk on Panels showing some great new usability features coming soon.

I attended several of the BoF (Birds of a Feather) talks along the content publisher theme and got a lot out of the “Support the Content Creators” talk that was run by Melissa Anderson. Lots of great discussion and sharing of tools and practices which were captured in a great notes doc by Kat.

I love watching case studies from the ground up where an agency covers every step of a web development project with a client. The folks at Treehouse Agency are excellent at telling these stories. I really enjoyed how they provided the under the hood details of their approach and tools used to rebuild the Zagat.com website. They also did a talk on their work to relaunch Energy.gov on Drupal which I didn’t see at DrupalCon but was able to see a more in depth Drupal implementation of the Energy.gov project at BadCamp last year. Here’s the slide deck from that presentation.

Well there you have it. I see nothing but clear blue skies ahead for Drupal.

Here’s a quote:

For every feature that we could add to WordPress, there is a plugin for it. Wouldn’t it be interesting to look at the usage of these and guage where should we go with it.

They also state that there are 4.96 average plugins per blog. The most a user has installed is 1290; 526 of those are active.

The post goes on to list the top 10 plugins…sans links. But I have taken the time to make your journey to them a little easier by providing them in my list below. Also, no information was provided as to the basis for how this list was calculated.

Top 10 plugins
1. Akismet
2. All in One SEO Pack
3. Google XML Sitemaps
4. NextGEN Gallery
5. WordPress.com Stats
6. WP-DB-Backup
7. WP-Cache
8. WP Automatic Upgrade
9. WP-Polls
10. CformsII

Bored on a Saturday night and laughing about my bank telling me about my Google check bouncing, I decided to blog about it and go to bed. I awake the next day get my coffee and make my way to the computer. I run a Firefox extension called Adsense Notifier which syncs up to my adsense account and displays impressions, click-thru rate and earnings in my status bar. When looking at it this morning I realized that I had already served about four times the number of impressions I usually serve in a day. I immediately had a feeling that a high traffic site must have linked to me. So I went to my home page and sure enough I was down. I immediately went into live chat with my great hosting company Bluehost. The admin on duty was taking a look and suggested I grab several logs from my server to try and debug the issue as well. He pointed me to a directory were there was a folder titled “cpu_exceeded_logs” and another one called “mysql_slow_queries”. There were only a few logs on some scattered days, and the logs averaged under 100k, but there was one generated on this day that was 1.32Mb…oh oh.

Going through the log it basically listed get requests with execution times. Most entries were 2-3 hundreths of a second…but then I came across a plugin which after executing was followed by a 5 seconds of cpu time for the sql query to run. I use WordPress to power my site and was able to get to my admin screen, and de-activate the plugin. I had also previously been familiar with a plugin called WP-Cache to increase performance in WordPress by caching pages and limiting database queries which I thought would be nice to need some day. Well today was that day. So I installed it, and watched as it started caching my site. Shortly after that my site was back up. Now it was time to figure out where all the traffic was coming from.

A quick view of my traffic showed that Digg was a huge referrer with a title that described a post I made the night before. I have to admit I had a few butterflies knowing that someone must have submitted it and it was gaining popularity. It had around 250 diggs. I didn’t know Notyavgkat who was the submitter and was curious as to how he found my post. So I started to read the comments and refreshed the page every few minutes. 270 diggs…290 diggs. I then message a few friends telling them about it. Wow…congrats…good job…the responses were coming in.

Apparently my site was down for quite a bit so there were a few comments that took a deserving shot at me.

• MrBlack08 wrote “the check you wrote for hosting must have bounced too. 33 diggs and its down.”
• erkshirefarms wrote “Looks like your server bounced too…”
• Matdevdug wrote “Yeah, good to see you went with the expensive hosting option. . . . .”

Then there were some funny comments about Google

• lenin wrote “Google checks is still in Beta mode. Anything in beta mode is prone to some errors.”
• flaq564 wrote “Looks like Google needs a payday loan.”
• and my favorite russvirante wrote “Oops, we spent all our money on doubleclick”

And finally… thetaoofbill wrote “Why do I get the feeling this story was made up to try to get that next adsense check bigger?”

I then went over to Google reader and saw the post appear in my Digg feed. But shortly after I saw the original submitter leave a comment stating “it appears this got buried after just 345 diggs…..wtf…is google behind this ?”. I wasn’t too familiar with the how’s and why’s of a post getting buried but I decided to do a little research. Digg offers this vague explanation:

Submissions can also be removed by users with the “Bury Story” feature within Digg. Once a story receives enough “buries,” it is automatically removed from the Digg Upcoming or Popular sections. The number of reports required to bury is based on a sliding scale that takes several factors into consideration (such as number of Diggs, reports, time of day, topic submitted to, etc.). Buried stories can still be found the profiles of users who have Dugg the story; you can also find them by doing a search.

It appears that there is a bury brigade in existence which isn’t surprising since I’ve read several stories about a small group that seems to have control of what makes the front page. I did however start using Duggtrends which offers a page dedicated to buried stories which makes for interesting reading to see which stories are being “censored”.

Spotplex is a site that was created with the goal of a true democratic system which so many people feel is a huge flaw in Digg’s system. TechCrunch and several other sites have provided their views. I became a member and have enjoyed using their site. It was interesting to see how my site’s rank rose on their system. Especially for a story with Google as a tag.

WordPress gets a bad rap on Digg when sites using it make it to the front page so I was happy to see a story titled “WordPress Performance: Why My Site Is So Much Faster Than Yours“. It’s a great post from Elliott Back, whom I’ve mentioned before as the author of a Lifestream plugin for WordPress, that discusses tweaks you can made to your server setup, php, mysql, and apache settings cache to improve performance using caching. It was nice to see all the haters commenting on how this WordPress site was surely going down now that the post made the front page. But it looks like it never did.

I also frequent the beautifully designed site by Nick La and have used his Glossy Blue WordPress theme. He too hit the Digg front page a few days ago with the release of his iTheme WordPress theme. He felt the pain as well and posted a good story on the aftermath with resources.

Lastly, in an ironic twist of fate I actually did pretty well with Adsense on the day I got Dugg, actually earning just enough to cover the returned check fee from my bank. Go figure.