drupal

DrupalCon 2014 Call for Sessions!

It's that time again! DrupalCon is right around the corner and it's time to submit your talk. The theme this year is Drupal 8 and that means that we'll be covering things like Symphony, Twig, and the other new components that make up Drupal 8. Do you have a talk about how to use the new templating system? Want to share how OOP works in Drupal 8? Submit your session now! See you in Austin!

The call for content ends March 7th at 11:59PM Austin local time (UTC -6).

Reliably Monitoring MySQL Replication

Replication is a wonderful thing for your clients. Having a 'hot spare' of their database(s) for redundancy, or being able to off-load read operations from the main database to increase performance, giving your client peace-of-mind about their data and application. I won't go into setting up MySQL Replication; there are more than a few guides on that already out there (here's the official documentation).

The Show Must Go On (or Hosting the 2013 Emmys on AWS)

When preparing for a big event, it is our job to make sure the general public sees exactly what is expected, and with the help of Amazon Web Service (AWS) we did! All planning comes with a few standard issue assessments/steps: Identify need, identify options, and begin to build!

Why More People Select WordPress than Drupal to Build Websites

First off, Drupal has had a great year and a great quarter. According to builtwith.com Drupal is second among all Content Management Systems at 13.75% of the top 10K websites and has added ~250K new website this quarter. That said, the number one CMS (WordPress) is at 42% of the market and according to the same source has added 5MM (yes, 5 million) websites this quarter. Here's the graph:

pie chart of CMS usage

What I Learned Today: Drupal Behat Scenario Cleanup

I've been doing a lot more Behat testing recently. As my tests have gotten more complex, I've discovered that it was only a matter of "luck" that my earlier tests were properly cleaning up after themselves. What I mean, is that during my tests I fill out and submit a node form, checking that I successfully created it and that the appropriate users can see it. After each scenario you want to clean up any data that was created so you can run the test again and get the same result.

Interested? Let's talk.