When I first heard Michelle Misner describe her success implementing a new Drupal website at the NY Public Library at the September Not-for-Profit Webmaster Roundtable Meeting, I thought it would be great to share her experience with others in our nonprofit community. So Michelle and I presented a webinar yesterday for Nten where she reviewed the project management process, and I asked questions on how things went.
In addition to the tips I provided in my earlier blog post, here’s some additional takeaways from yesterday’s session:
- Do a content audit before starting a website redesign; you probably have more content than you think; allow plenty of time for migration into the new CMS
- Picking the product is easy compared to instilling a culture within your organization so everyone assumes responsibility for online content – if only the communications department has updated web pages in the past, this will be a major shift
- Training is a continual process – not just when you roll out the new system; Drupal has a steep learning curve, so make sure you allow the time for internal staff to learn the software, especially the person(s) who will be managing the site
- Make sure you coordinate what’s on your website with other communication channels, e.g. social media, and use an editorial calendar to plan content updates on all platforms
- Plan who will be responsible for content updates and then trust your staff to post them; not every piece of content needs to be reviewed before going live, but some parts of your website may need to be more closely monitored than others. (Drupal does not have a built-in way to notify approvers that content is awaiting review.)

