Justin Emond's blog

To ensure a launch process goes smoothly I like to create three checklists. A pre-launch checklist covers everything you need to do a few days before launch to ensure everything is prepared. A launch checklist outlines the actual process the launch team will go through during the launch window itself. And a post-launch checklist details a variety of tasks you can’t really do until the site is live, and you do a few days after launch.

We recently had the pleasure of working with a client at the University of Southern California -- which happens to be both the greatest university in the world and my alma mater -- to evaluate how best to integrate a Drupal site with USC’s Shibboleth installation.

We take security very seriously at Urban Insight. A focus on security is an important part of everything we do, from development to day-to-day work flow. But security isn’t just about correctly configuring firewalls and ensuring you have the latest service pack installed. It’s also about having a secure work flow around the office.

Here are some quick tips that we use around our office to ensure we all start work with a secure base:

Tip 1: Use a master password in your browser

There are a variety of ways to integrate video into a Drupal site. There are free but branded options like YouTube or Blip.tv, self-hosted options using the FlashVideo module, and higher-end video platforms like Viddler and Kaltura.

As any Drupal developer will tell you a fresh Drupal install requires a lot of modules and configuration refinements to provide the kind of core functionality that is commonly needed on almost any project. While there are some great lists of starter modules online I wanted to focus on the refinements needed specifically for creating a human-friendly rich text editor for the body field.

Here is my checklist for setting up the body field editing experience: