Problems encountered and solved in rebuilding the weta.org website, moving from Drupal 5 site to Drupal 7. Presented at Drupal Day at the 2014 Nonprofit Technology Conference.

1. Drupal 5 to Drupal 7: WETA.org
Makes the Leap
Jess Snyder, Web Systems Manager, WETA
@jesseves

2. Background
• WETA: Flagship public broadcasting station
for Washington, DC
• Launched weta.org on Drupal 5 in 2008
• Re-launched on Drupal 7 in November 2013

3. Problems to Solve
• Landing pages
• Radio playlists
• Community calendar
• Content migration

4. Landing Pages
Or: Blocks That Aren’t Blocks

5. Landing Pages
• Frequent content updates
• Re-use content on multiple pages
• Modular design

9. Feature Blocks
• Panels + “Feature Block” content type
• Multiple view modes via Display Suite
• Individually placed or scheduled via Views
and Node Reference

10. Playlists
Or: Sometimes Views Isn’t Enough

11. Playlists
• Crazy, crazy rules about how playlists
display
• hook_views_query_alter()

12. Community Calendar
Or: Explaining Date Repeat to Grandma

13. Community Calendar
• Module recipe: Date + Views, not Calendar
• Date handling: repeating vs. multiple dates
• Conditional Fields + Rules + Computed Field

16. Content Migration
Or: Step 1: Install Migrate. Step 3. Profit!!

17. Content Migration
• Three options
1. Giant Copy/Paste Party!!!
2. Feeds
3. Migrate
• Migrate + Migrate UI + Migrate D2D

18. Questions?