Sean Buscay

I removed all the stuff we didn't need.

What's the difference between Drupal 6 & Drupal 7 ?

Did you mean drush sql-drop or drush sql-dump ?

The user name and password are admin and admin.

My latest screencast: How to use Drupal 7's built-in Ajax Framework

In this short screencast I'll show you how to use Drupal 7's built-in Ajax Framework to dynamically update web page content with new data from the server; all without a page reload.

You can view the screencast here: https://vimeo.com/39479686 And get the code from github here:

Here's a simple code snippet that allows the use of global tokens (via the token module) in the footer message variable:

function phptemplate_preprocess_page(&$vars) { if (module_exists('token')) { $vars['footer_message'] = token_replace($vars['footer_message']); } }

Simply place this in your your theme's template.php file or your module's .module file, replacing 'phptemplate' for the theme/module name. Be sure to rebuild the theme registry after doing so.

This comes in handy when displaying the current year in a copyright string (i.e. "©2010 My Company") so that it never gets stale. With the above code in place, edit the 'Footer message' in your 'Site Information' admin screen, substituting the [site-date-yyyy] token for the current year

(i.e. "©[site-date-yyyy] My Company").

I just put a printf compatible format string into the footer message, for example:

© 2000-%d My Company Inc.

And then in the template use:

<?php print '<p class="copyright">' . sprintf($footer_message, date('Y')) . '</p>' . $footer; ?>

by: mschiff February 12th, 2010 @ 7:14pm

My wife is known by myself and friends as someone who's excellent at managing projects.

Her ability to start from nothing but a goal and produce real results with many moving parts always impresses me.

Her secret is that she approaches projects with the perspective and skills she developed in theatre while producing and directing stage plays in college and later managing a cast of a hundred in professional theatre.

I wanted to learn more about her process so I asked her to describe to me how to produce and direct a stage play.

The following is what this web developer learned from the stage play director, and how to apply to her methods to any good development process.

Directing a Stage Play (In Brief)

Read the script over four or five times

Before anything, become very familiar with the script until you know it inside and out.

Start at act one - scene one

Work through the script and make notes on what's needed to produce each scene.

Research parts of the script as needed, such as time period or subject matter.

Define elements such as blocking, set design, ect.

Rehearse early

After casting, begin rehearsals early.

Start with a sit down to do read-throughs and discuss the characters.

Later progress to the stage.

Refine elements of each scene over time.

Provide notes to actors on specific changes or areas for improvement.

Meet separately with other departments/crew

Schedule miscellaneous meetings and discussions with set designers, sound, costume design, and any other parties that support the overall production.

Communicate the vision for the play and get their feedback on ways to make it happen.

Rehearse often

Continue to progress through rehearsals.

Improve and tweak scenes over time.

Add and try out other layers such as blocking, sound, and lighting as ready.

Move to dress rehearsals.

Finally complete several walk-throughs (fully acting out the play, but without an audience) until the play is ready for opening night.

Develop Web Sites Like a Stage Play

Here's what producing a stage play has to teach us about how to successfully manage a web development project.

Read the script over four or five times

Functional Specifications and Technical Specifications are the web developer's scripts.

Read the scripts over four or five times until you know them inside and out. Have all lead team members do the same.

Start at act one - scene one

This seems so basic, but it's key for large projects that involve designing major systems.

It's hard to know where to begin. Start at act one - scene one.

Begin researching and mapping out what's needed to meet each section's specifications.

In other words, break it up into manageable chunks.

Lay in and improve functionality over time.

Rehearse early

Have a sit down with your development team and all the actors involved in development.

Discuss the big picture and purpose of the project.

Review individual roles and how the team should act together to produce the final site.

View each functional area of the site as a scene to be improved and enhanced over time.

Send individual notes to developers and team members to suggest changes, improvement, or simply to provide direction for next steps.

Meet separately with other departments/crew

Schedule and manage all those other meetings that need to take place with other departments.

Meet with server admins, marketing, designers, and who ever else has a stake in the project.

Share the vision, and get their feedback / buy-in on how to make it all happen.

Rehearse often

Rehearse often. Yes, the iterative agile approach.

Add on functionality and complexity over time. As designs become available layer them into the 'scene'.

Let all people involved in the project attend rehearsals, ie. daily stand ups and build calls. However, the Scrum Master (as the director) runs the meetings.

Eventually move to client demos and client acceptance testing, as a play would move to dress rehearsals.

Complete several run-throughs, including testing on the servers, QA testing, and load testing.

Put this in your .gitconfig

[url "http://git.drupal.org/project/"] insteadOf = "mod:"

And now you can clone a drupal project like this:

$ git clone mod:views Cloning into views...