Staff-Projects/2019-Website-Launch

= Overview =

Before June 7, the Foundation will launch a new website designed to engage visitors and professionally convey the value of our collective work. Rather than just reskinning our current wiki or placing a simplified landing page in front of our site, we plan to migrate to an entirely new platform. Website 2.0 must better connect with our developer audience and be valuable when visited on a variety of devices. It must be possible for elements of our site to be managed by our communities or through automation and any platform change must retain these attributes as well as ensuring continuity of analytics, permissions design, and redirect of inbound links. A proof of concept will be complete by April 1. Once Website 2.0 is launched, the wiki will be maintained through 2020 for historical purposes.

= Goals =


 * 1) Launch Website 2.0 on or before June 7, 2019
 * 2) Ensure top 500 pages are migrated before May 15, 2019
 * 3) Redirect for inbound search traffic ready at launch
 * 4) Retire Mediawiki instance before June 1, 2020

= Milestones =
 * 2019-03-11, Proof of concept complete validating Requirements (below)
 * 2019-03-18, Site Map designed
 * 2019-03-22, Template Selected and design underway for non-supported pages
 * 2019-03-27, Validate Google Analytics instance running
 * 2019-03-29, Staff Projects migrated and in production
 * 2019-04-05, Events pages migrated and in production
 * 2019-04-12, Policy pages migrated and in production
 * 2019-04-19, Corporate pages migrated (not production)
 * 2019-04-26, Validate Meetup Connector
 * 2019-04-26, Validate search redirect working on events/policy pages
 * 2019-05-10, Chapter pages migrated (not production)
 * 2019-05-17, Project pages migrated (not production)
 * 2019-05-24, Redirect system in place and ready for launch
 * 2019-06-04, Website Launch [Name of Owner]
 * 2019-06-04, Update Corporate/Chapter/Project pages with divs
 * 2019-06-04, Validate search redirect working site-wide

= Leadership =


 * Mike McCamon, Project Lead, email [mailto:mike.mccamon@owasp.com?subject=Website%20Project mike.mccamon@owasp.com]
 * Harold Blankenship, email [mailto:harold.blankenship@owasp.com]

= Requirements =
 * https
 * Custom domain - owasp.org
 * Continued use of Google Analytics or similar functionality
 * Maintain inbound search love with redirect at launch
 * Credential management
 * Committees - only an org email
 * Control who is repo owner
 * Inherited navigation for information hierarchy
 * Cannot have advertisements unless controlled by OWASP
 * Restrict cross-domain scripting (except Analytics)
 * Google crawlers successfully use rendered content of page
 * Ability to embed YouTube videos
 * Move to a SaaS provider and no longer host ourselves
 * Free or close to free
 * Nice to have: Decorate rendered certain pages with WATCH/STAR repo tools
 * Nice to have: Search content in site
 * Nice to have: ability to duplicate Meetup widget functionality (pull in Meetup JSON and render "future meetings")