2. Agenda
• Concepting & Strategy Update (Eric G.)
• Build Progress Update (Eric G.)
• Drupal 7 Update (Eric G.)
• Lunch
• Design Review (Eric G.)
• Build Plans (Alex B.)
• Taxonomy/Content Update (Mark M.)
• Project Management Overview (Ian C.)
• Planning for Launch & Support (Eric G.)
• Q&A (All)
3. Development Seed’s Summer Focus:
• Concepting + strategy
• Technical architecture
• Design
• Prepping for Drupal 7
4. Development Seed’s Summer Focus:
• Concepting + strategy focusing on making it:
• Easier to add content to the site
• Easier to find content + jobs on the site
• Easier to see all types of content the site
offers
• Balancing expanding audience w/ building
for power users
5. Development Seed’s Summer Focus:
• Technical Architecture
• Going Drupal 6 vs. Drupal 7
• Key modules needed
• Importing content
• Integration with the jobs site
• Making everything wicked FAST!
7. What is done:
• Concepting and strategy
• Technical architecture ~70% (need to
present plan in official writeup still)
• Designs ~ underway
• Key module refactoring
• Drupal 7 technical base prep
13. What does a Drupal 7 slow down mean?
• Drupal 7 is _still_ the right choice.
• We are actively building on Drupal 7 for
you, in its pre release state.
• This is messing with our timing badly
• ... and costing us a lot more.
14. Drupal 7
• Under development for 3 years
• Primary base for the next 2 years AKA you
will have access to the latest new tools by
being on the latest platform
• Reducing total costs of ownership by
reducing an upgrade cycle.
• More attractive for developers to work on.
15. Timing and cost plans:
• Development Seed is burdening almost all of
the Drupal 7 costs on this project.
• This is long term strategic investment for the
larger international development space.
• We are adjusting our build plans to try to
stay on target. (Alex will speak to this)
• We need to slip delivery till December 3rd,
18. Agile Design
• There are still mockups.
• mockups ensure:
• style/theme
• general layout
• information architecture
• The designs need to be flexible though.
19. How to make design flexible
• Go with the grain of the software
• Reducing total costs of ownership via
upgrades.
• Taking advantage of built in workflows.
• Experimenting and playing.
• Things will need to change
70. Fixed Elements
• Content Migration (including Jobs)
• Core Site Functionality
• New Design
• Drupal 7
• Stable Launch in December
• THEN Additional Phase 1 Scope
72. Feedback Process
• All Ideas Welcomed & Captured Online
• Overall Backlog Triaged with Mark McCarthy
• Priority Ideas Moved to Phase 1 Backlog
• Remaining Ideas Saved for Phase 2
79. ReliefWeb Tasks
November:
• Review Content in New Site (mid Nov.)
• Training on Using New Site (mid Nov.)
Outcome: Migration Done by end of November