Lullabot Ideas
We know stuff. We empower you to know stuff too.
Reprint of "Power to the people: a new approach to Drupal"
Blog by Jeff RobbinsOctober 13, 2008 - 12:24pm
This is a reprint of a blog post that Jeff Eaton put up on his blog. It seems to sum up many of our interests and intentions with our new venture. We wanted to be sure that no one missed it, so we're reposting it here. -j.r.
Late Friday afternoon, the first news broke about a project that I've been working on for the last couple of months. Internally, the Lullabot folks have been calling it "Project Codename," because we like recursively cheeky names. The goal is pretty ambitious: build a dirt-simple hosted service that lets people with great ideas leverage the power of Drupal.
For the past couple of months, a lot of cool things have already come out of the project for the Drupal community, though we haven't been able to say much about what was going on behind the curtain. SimpleViews, my new task-oriented front-end for the Views module, is one example. Rather than constructing content listings bit by bit, it lets site-builders make a few simple choices and get quick results. Nate Haug has been building similar tools for the CCK module; Angie Byron has been working with user experience experts to streamline Drupal's administrative interface; and Jeff Robbins has been hard at work on some amazing tools that allow site builders to customize a site's layout and CSS skins with point-and-click, drag-and-drop simplicity. Subtler stuff, like John VanDyk's recent improvements to the Views Bulk Operations module, have grown out of the tools we're building for simple, customizable administration panels.
All of these things are really exciting, but they share a deeper connection that's at the heart of our project. Getting a new Drupal site is pretty easy now -- Bryght's turnkey hosting, Acquia's new support network, and one-click installs on a host of ISPs make the initial hurdle a lot less daunting. What comes after that -- turning a great idea into a fully implemented web site -- is still tough. Drupal is all about combining lots of small pieces into an awesome package. Views, CCK, custom field types, Organic groups, UberCart and eCommerce, Rules... harnessing that power requires learning a lot! The toughest part isn't the technical stuff (how to sort a Views or how to add a field to CCK) but the conceptual aspects of what these things mean, how they work together, and how the abstract pieces can be combined to achieve the goals a site builder is working towards.
Over the past year or two (especially while working on our upcoming O'Reilly book, Using Drupal) it's become more obvious to me that making Drupal accessible to non-gearheads requires a new approach. Rather than dumping all of those tools in front of people, and sweating bullets to make each one a bit simpler, we can build new kinds of tools on top of them, bridging the gap between hardcore developers and idea-oriented folks who just want to build a great site.
Some of these things are part of Drupal's core push towards better, tighter user experience. Others are specific to our project -- carefully calculated decisions to hide Drupal's more advanced capabilities from users who won't need them. Still others require new tools like SimpleViews, tools that provide users with concrete task-driven ways of achieving goals without revealing the underlying complexity of Drupal's building blocks.
The folks we've been working with on this project are awesome: genius folks like Karen McGrane, Josh Rubin, Jenny Ng, and others from Bond Art + Science have brought tons of experience and talent to the table. They designed the New York Times web site and they're passionate about bringing Drupal's power to more people. Ed Sussman, who was at the helm of FastCompany.com's conversion to Drupal, has just joined the team as CEO: his understanding of the tech industry and his excitement about the project is awesome.
That's what Project Codename is about: leveraging the power of the tools we've built as a community, putting choices that make sense in the hands of creative users, and giving them a simple hosted platform to run it on. In a lot of ways, it goes back to How Drupal Will Save The World, Jeff Robbins' opus on the platform's potential. It's a lot of work, but the payoff for the Drupal community is really exciting. In the coming weeks and months, it'll be great to see how the stuff we're building can be fed back into the community, too.

Comments
crazy
if it's half as bad as ed's version of fast company.com, everyone who's been planning this should head asap to the lifeboats. thank god he's gone.
I really like the idea of
I really like the idea of simpleview and the whole concept of project codename gets me excited - I look forwards to checking out the results.
More layers not the solution
I think introducing more layers is not the road to simplicity. Much of my Drupal churn time (I am a developer) is understanding what's going on under the covers. I don't want more covers.
If you're targeting business owners, know that other approaches to CMS In a Box have had difficulty getting traction, because it's still too big a hurdle to get going.
Perhaps designers are a middle-of-the-road customer for you. Just who is your customer, anyway?
"More Layers" versus "The Right Layers"
I agree wholeheartedly that stacking lots of layers on top of each other isn't a sustainable solution. As the saying goes, any problem can be solved by more abstraction, except for too much abstraction...
The biggest challenge that we face is refactoring critical components of Drupal so that the developer-oriented UI conventions it currently uses can be replaced with targeted, task-specific end-user oriented systems. SimpleViews, for example, doesn't sit on top of the current Views UI: it sits next to it, and manipulates the Views API directly even if the full Views UI doesn't exist.
Right now, there are only a few places in Drupal where this kind of separation exists and can be effectively leveraged. The rest of the system -- the places where we have to work around tightly coupled UI, CRUD, API, and workflows -- are some of the most challenging when sites require heavy customization. Refactoring those things so that they can be effectively 'swapped out' in favor of the UX needed for a given project is the big challenge I think we (the members of the Drupal community) need to tackle.