< Back to the Table of Contents

NASA Web Modernization Phase 1: Final Deliverables and Presentations

Project Folder: Final Presentations and Deliverables

General:

●      Final Presentation Opening - Opening final presentation slides with key takeaways.

●      Executive Summary - This presentation is a very succinct set of recommendations distilled from the 4 month research and discovery effort. Designed to be shared outside the Web Modernization team.

●      Roadmap & Next Steps - This presentation illustrates a high-level roadmap of the User Experience strategy and a more detailed view of immediate recommended next steps.

●      Design Aspiration - This presentation is a recommendation of what NASA could do to design a consistent, modern, and awe-inspiring experience to attract, engage and inspire a broad and diverse audience.

Research:

●      Research Final Presentation - This deck was presented to the NASA team and includes integrated insights from both streams of research. For more detailed information and full insight reports, click on one of the links below.

●      Full interview insights report - This report outlines the key findings from our one-on-one interviews with NASA’s public audience. This report includes descriptions of the four segments, or “schools of thought,” common themes across all groups, and detailed insights about needs, motivations, and expectations around science and news content.

●      Full survey insights report - This report outlines the findings from our survey of the general public. This report also includes deep dives on specific groups, including K-12 teachers and students, women, those with disabilities or accessibility challenges, and those uninterested in science and space topics.

Content Strategy:

●      Content Strategy Final Presentation - This document outlines a recommended Content Strategy for NASA.gov, as informed by Blink primary quantitative and qualitative research. Section one covers the NASA brand story and value proposition. Section two outlines content prioritization to support the brand story. Sections three and four take a more tactical perspective of both content structure and messaging approach to optimize the NASA.gov brand experience.

●      Content Strategy Appendix - This document contains additional detail to support the primary, final presentation, and it follows the same structure mentioned above.

Accessibility:

●      Accessibility Final Presentation - Insights specific to each of the sections including Research, Content Strategy, IA, and SEO. Plus an Overview section on Accessibility.

●      Accessibility Detailed Report - An extended discussion of accessibility for Information Architecture, Content Strategy, and recommendations for Next Steps. Plus a specification of validation and features related to accessibility when considering a content management system.

●      Accessibility Site Quick Check - This is a summary of a very brief review of the accessibility of the 40 sites used in Phase 1. It identifies the seven main issues that were identified across all the sites.

●      Accessibility Audit 2020 – This is a table reviewing the 40 sites in Phase 1, outlining potential accessibility issues across the site.

Information Architecture:

●      Final IA Presentation - This presentation summarizes the IA work and includes (as an appendix) findings from navigation tree testing.

●      Final IA Deliverable - These files, viewable in a web browser, present the IA work, including site audit results, top-level IA, top-level menu framework, and wireframes illustrating an example navigational experience for Mars.

○      Final IA Deliverable (posted on the Axure cloud service): Password = exoplanets-are-cool

○      Final IA Deliverable (HTML files) -

■      Chrome Viewing Instructions:

●      Download the zip file and open the folder “NASA Web Modernization IA”.

●      Search for the file “index.html”.

●      Double-click and it should open in your native web browser. If you are using Chrome, the browser will prompt you to download the “Axure RP Extension for Chrome”. Follow the instructions on the page to install the extension, and proceed to open the “index.html”. The first page should be the “Table of Contents”.

■      Safari Viewing Instructions:

●      In Safari, to view Axure files locally, it is necessary to choose “Disable local file restrictions” under the “Develop” menu. I don’t know if this is the case in other browsers as Safari tends to be more locked down. If you don’t see the “Develop” menu go into Preferences > Advanced and check the box for “Show Develop menu in menu bar” at the bottom of the dialog.

○      Native Axure File - the final IA deliverable was created in Axure, a design prototyping tool. The application Axure 9 is required to view and edit this file.

SEO:

●      SEO Final Presentation - This report includes our SEO approach and recommendations.

●      NASA Web Consolidation Data Dashboard - This dashboard is housed in Google Data Studio and is accessible to anyone with the link. The first page explains the scoring methodology. Subsequent tabs are grouped by entity. Data has been scrubbed for accuracy but you will note that many URLs are missing Google Analytics data due to issues with the configuration of the GA profile. Because of this, we developed an average relative value score which is explained on the first page. We used AI to identify the entities so you may see instances where “Mars” was identified within the word “Marshall” and other minor quirks. This data should be used as a basis for understanding SEO value but is not exhaustive.

●      Mars Entity Mapping Exercise - This spreadsheet contains an example entity mapping exercise for Mars which includes identification of a primary entity, content type, and location within the proposed Information Architecture, as well as the content action (consolidate, migrate, redirect). We used this exercise to determine level-of-effort for the greater overall project as well as in identifying content types for consideration.

●      NASA Technical Requirements Documentation - This document contains user stories for the CMS and technical site requirements. We have written them as user stories so that the development partner has an understanding of the intended usage and behavior and can implement the requirements in whichever fashion makes sense for their code base.