What WordPress & Drupal Developers Need to Know about SEO

Why should web developers care about SEO? It might seem like the very essence of “not my job.” Developers build the site. Content creators fill the site with content. The quality of the content, plus the content creators’ amplification efforts is where SEO lives. Right? The fact is, though, web developers can do a great deal to increase a site’s search engine visibility. Which means that if we view SEO as someone else’s job, we’re holding content creators—and website performance—back. There are three stages of SEO:

The Path of Lower Risk: Using Git, FTP, and WordPress

Pantheon often touts version control, namely Git, as one of the tools of successful developers. However, for the many developers out there currently not using Git, I am going to go out on a limb: you probably know about it, have tried it, and are doing just fine without it, thank you very much. Your customers are happy, sites are chugging along, and the last thing you need is a cryptic command-line tool to add complexity and slow your flow.

WordPress Site Networks vs Pantheon Upstreams

With the release of Pantheon Upstreams, I’ve been asked a few times to clarify the story vis-a-vis multisite from the WordPress perspective. Unlike Drupal, where I think there’s a clear and easy choice, WordPress has a first-class core feature for operating sites in a multisite configuration called Site Networks.

[VIDEO] Bringing Drupal Site Updates with Composer to the Masses

Last month in Vienna, people from all over the world came together to learn, share and collaborate at DrupalCon Europe. One of the interesting topics of conversation this year was the question of how to make Composer approachable for a wider base of users. The first stable release of Drupal 8 was nearly two years ago; in that time, it has become easier to use Composer with Drupal from the command line.