Drupal

New challenges

Today I resigned from Palantir, a company I’ve called home for almost six years. I’ve done a lot of exciting work at Palantir, but it’s time for new challenges. I don’t even know what those new challenges are yet — I don’t have a job offer and I’m not starting my own company. (I will be trying to finish my book on Sass and Compass in between now and what happens next, so watch for that.)

Making Drupal 8 Mobilicious

The time to shape our future is now

At Drupalcon Munich, one of the awesome things was seeing so many people show an interest in helping out with Drupal 8’s Mobile Initiative. On the Friday after Drupalcon’s session, at that Code Sprint, there were four tables full of people helping out with JavaScript issues, Drupal’s administrative screens, responsive images, and HTML5. And, as Dries’ recent blog post shows, now is the perfect time for you to help out with the Drupal 8 Mobile Initiative.

PHP with Homebrew

Tapping a new feature

Homebrew is pretty damn sweet if you are a developer on Mac OS X. It’s the package manager that doesn’t suck.

But the developers that run Homebrew aren’t PHP developers. And their official policy of not providing a formula (homebrew’s name for a “package”) for software already included in Mac OS X means that PHP wasn’t going to be available in Homebrew.

Rethinking Drupal’s Theme/Render Layer

Drupal 7 and the Arrays of Doom

This Friday through Sunday, I’m going to San Francisco to attend a sprint to “rebuild the theme layer” in Drupal 8. This is the next exciting step in a journey I started nearly 3 years ago.

I’ll hope you’ll join me at the sprints as we combat Drupal 7 and the Arrays of Doom!


A Drupalcon 2012 film: Drupal 7 and the Arrays of Doom
Modified slightly from a tweet by @SGreenwellUT

Scene 1. [Day break. Our themer is hunched over his keyboard writing awesome themes in Drupal 6, but he’s troubled.]

A cautionary tale for the Drupal community

Don’t get cocky, kid.

Kevinjohn Gallagher recently wrote “WordPress has left the building”, expressing his colleagues’ and clients’ frustration at trying to use WordPress when CMS capabilities are required. His 15 points of pain for developing usable sites with WordPress are an interesting list for Drupal developers as well. We have good solutions (that are still improving!) for many of the items on that list. Yet, we still share a few of those pain points with WordPress.

Unfortunately, Kevinjohn has been getting attacked by many of the WordPress community. While many WP fans have been writing “How WordPress took the CMS crown, his piece about his agency dropping WordPress as its go-to website solution as provoked vitriol. Over at the WP Tavern, he writes:

[…] there are more posts on WordPress community sites discussing my CV and dyslexia than the actual content of my post.
Sadly in the last 7 days I’ve had 3 ddos attacks, 14 threats (4 “credible”) against myself or my family, multiple requests to have me removed from speaking at WordPress events

Pages

Subscribe to RSS - Drupal