Anatomy of a Drupal Project

The Fuse project management team has been meeting lately with the purpose of refining our project execution process. Now, we had a fairly good general process in place for executing a standard web project, but we found we were shoe-horning Drupal projects into this process. Drupal, as some of you may know, has it's own unique set of development requirements and since 75% of our projects are Drupal based these days, we wanted to optimize that process for Drupal.

We've come up with a what I think is a good start on refining our process for Drupal projects and would like to share this document with the Drupal Community.  We view this as a work in progress and welcome your feedback.  What are we doing that you aren't?  Are we missing something that you include in your process?  We'd love to hear from our fellow Drupalists.

Have a look: Anatomy of a Drupal Project

We've also been refining our Drupal development and deployment workflow which we will be touching on in an upcoming post.

greg / President
Born upon the rocky shores of Nova Scotia, Greg was at first connected to the world through the Atlantic Ocean. Being that it is very cold, he moved west, and plugged into the Internet instead. Over the past five years, Greg...

Post a new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <p>
  • Lines and paragraphs break automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>, <pre>, <c>, <cpp>, <css>, <drupal5>, <drupal6>, <java>, <javascript>, <php>, <python>, <ruby>. The supported tag styles are: <foo>, [foo].
  • Insert Google Map macro.
  • Each email address will be obfuscated in a human readable fashion or (if JavaScript is enabled) replaced with a spamproof clickable link.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.