The document provides an update on the status and plans for building a new ReliefWeb site. It discusses Development Seed's focus over the summer on concepting, strategy, technical architecture, design, and preparing for Drupal 7. It notes some tasks are 70% complete while Drupal 7 is delayed until late October. The process for building the site will be agile, with an initial light build in September, content migration in October, additional development in November, and reviews/launch aimed for December. ReliefWeb's involvement includes design confirmation, migration planning, hosting plans, architecture review, content migration, site review/training, and QA/launch. Risks include launching before Christmas and support plans.

1. ReliefWeb & Development Seed:
Building Status, Design, and Planning
Thursday, September 2nd

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!

6. Development Seed’s Summer Focus:
• Design Goals
• Focus on the content
• Light = FAST!
• Clean

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

8. What is NOT done:
• Drupal 7

9. Drupal 7
• It is late.

11. Yes.... that really says October 27th

12. ... and we think that date is optimistic

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,

16. Design: this is not another website

17. Design process: going agile

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

20. Design: this is not another website

26. My ReliefWeb

27. Keeping it simple to help
users know where to go

28. River of fresh updates

29. Where events are happening

30. Hilight key emergencies

31. Hilight other key content on ReliefWeb

33. format for LOTS of updates

34. Visualization tools

35. filter in context
in-context power filtering

38. Real time mapping of reports

39. Show key emergencies +
make it easy to find countries

41. Better integration of jobs

42. add context to countries

43. feature key reports

44. trying to better integrate
emergencies w/ countries

45. integration with
data.worldbank.org

46. river of updates

47. which can be visualized

48. and filtered by everything!

50. Building reliefweb.int

51. How do you normally build a web site?

52. Plan
Build
Migrate
Review
Adjust
Launch

53. You’ll be waiting for us

54. Light build + early migration
to move up
reviews + launch

55. Plan
Build
Migrate
Review
Adjust
Launch

56. Plan
Light build
Build
Migrate
Review
Adjust
Launch

57. Plan
Light build
Migrate | Build
Review
Adjust
Launch

58. Plan
Light build
Migrate | Build
Review
Adjust
Launch

59. Step I
DS builds light shell site
(won’t need all of Drupal 7)
Delivery: 3rd week of September

60. Step 2
RW migrates content
(DS helps)
Delivery: End of October

61. Step 3
DS builds out site
(parallel to migration)
Delivery: First week of November

62. Step 4
RW reviews
Delivery: mid November

63. Step 5
DS delivers adjustments
Delivery: First week of December

64. Step 6
Final QA and launch
Expected launch date: mid December

65. Plan
Light build
Migrate | Build
Review
Adjust
Launch

66. The Process

67. Agile = Working Code, Fast

68. Why Agile?
✓ Prioritize Launch Date
✓ Ensure Top Quality on What Is Delivered
✓ Collaborate to Manage Scope & Risk

69. Result: Very Tight Site Delivered ASAP

70. Fixed Elements
• Content Migration (including Jobs)
• Core Site Functionality
• New Design
• Drupal 7
• Stable Launch in December
• THEN Additional Phase 1 Scope

71. Gathering Feedback

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

73. What is Phase 2?

74. Phase 2
• New Aggregation Solution
• Community Features
• ReliefWeb “Apps”
• TBD?

75. Result: Very Tight Site Delivered ASAP

76. ReliefWeb’s Involvement

77. ReliefWeb Tasks
September:
• Confirm Design (early Sept.)
• Confirm Migration Plans (early Sept.)
• Confirm Hosting Plans (mid Sept.)
• Confirm Overall Architecture (late Sept.)
Outcome: Solid Plan by End of September

78. ReliefWeb Tasks
October:
• Do Basic Migration into Drupal (early Oct.)
Outcome: Content in Drupal by end of October

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

80. ReliefWeb Tasks
December:
• QA Final Site (early Dec.)
• Launch Site (mid Dec.)
Outcome: New ReliefWeb Live in December

81. Risks
• Launching Before Christmas
• Support Plans