Difference between revisions of "Staff-Projects/2019-Website-Launch"

From OWASP
Jump to: navigation, search
Line 94: Line 94:
  
 
* www-community
 
* www-community
* www-event-2019GlobalAppSecDC
+
* www-event-2019-GlobalAppSecDC
* www-event-2020AppSecDaysCalifornia
+
* www-event-2020-AppSecDaysCalifornia
 
* www-chapter-losangeles
 
* www-chapter-losangeles
 
* www-chapter-amsterdam
 
* www-chapter-amsterdam

Revision as of 09:26, 21 October 2019

Overview

Before August 1st, the Foundation will launch a new website designed to engage visitors and professionally convey the value of our collective work. Rather than just re-skinning our current wiki or placing a simplified landing page in front of our site, we plan to migrate to an entirely new platform.

The project will be called Website-Git and 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 July 1. Once Website-Git is launched, the wiki will be archived through 2020 for historical purposes.

Upon the completion of this project, OWASP.org will be hosted in Github. The architecture will place a repository for each logical entity of the foundation in one organizational account. For instance, there would be a repo for each chapter, project, event, and several other organizational entities. This design will increase source control and allow us to connect visitors with the content that is of interest to them.

User Journeys

  1. Discover and connect with a local chapter
  2. Learn, engage, and contribute to an OWASP project
  3. Decide to attend an OWASP sponsored event
  4. Learn more about the Foundation
  5. Become an individual member of OWASP
  6. Become a corporate member of OWASP
  7. Either as a corporation or individual, donate money to OWASP
  8. Review the policies, financial, and governance design/practices of the Foundation
  9. Decide to host a project with OWASP
  10. Subscribe to emails from the Foundation

Goals

  1. Launch Website-Git on or before August 1, 2019
  2. Ensure top 500 pages are migrated before July 30, 2019
  3. Redirect for inbound search traffic ready at launch
  4. Boost visitor engagement with chapters, projects, and membership
  5. Static Mediawiki instance launched August 2, 2019
  6. Retire full Mediawiki instance before June 1, 2020

Milestones

  • 2019-06-01, Proof of concept complete validating Requirements (below)
  • 2019-06-03, Site Map designed
  • 2019-06-15, Draft wireframe Complete https://www.owasp.org/images/5/5d/Owasp_wireframes.pdf
  • 2019-06-10, Template Selected and design underway for non-supported pages
  • 2019-06-24, Staff Projects migrated and in production
  • 2019-07-01, Validate Google Analytics instance running
  • 2019-07-01, Events pages migrated and in production
  • 2019-07-08, Draft template installed on site
  • 2019-07-08, Policy pages migrated and in production
  • 2019-07-10, Determine site-wide Search tool/solution [Harold]
  • 2019-07-10, Research A/B content tool
  • 2019-07-15, Corporate pages migrated (not production)
  • 2019-07-15, v2 Template installed
  • 2019-07-22, Chapter pages migrated (not production)
  • 2019-07-22, Project pages migrated (not production)
  • 2019-07-29, Redirect system in place and ready for launch
  • 2019-07-30, Validate in-bound search redirect working on events/policy pages
  • 2019-08-01, Website Launch [Harold]
  • 2019-08-02, Update Corporate/Chapter/Project pages with divs
  • 2019-08-02, Validate search redirect working site-wide
  • 2019-08-15, Validate Meetup Connector

Leadership

Requirements

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

Required Templates

  • Home page
  • Chapter
  • Project
  • Event
  • Entity Meta (landing page for chapters or projects or events)
  • Documentation Page
  • Article (blog)

Repo Naming Convention

Top level

  • www-site-theme - master json for menus, templates, common assets, header, footer
  • www-site - main pages, not topic-specific
  • www-board - board meetings
  • www-corporate - board & staff, about us, careers, finance, governance (By-Laws), About Membership
  • www-staff - staff projects
  • www-policies - overview, membership, sponsorship, finance, donations, handbooks, guidelines
  • www-community
  • www-event-2019-GlobalAppSecDC
  • www-event-2020-AppSecDaysCalifornia
  • www-chapter-losangeles
  • www-chapter-amsterdam
  • www-chapter-au-melbourne
  • www-chapter-ap/sa/af
  • www-project-zap
  • www-project-topten
  • www-committee-wia
  • www-committee-projects