MAPEX-80 Starting to fill in methodology docs and boilerplate text

[mehaase]

• Created a new "about" page with high level overview of the project
• Create draft pages for use cases and methodology (using existing text -- this will need to be updated)
• Update placeholder text on home page
• Added MITRE Engenuity favicon
• Make sure that nav menu item titles match their corresponding page titles
• Sort the items in the navbar
  • Put ATT&CK Matrix at the top of ATT&CK menu
  • Sort mappings alphabetically (with external mappings home at the top)
• Update links in footer
• Change default ATT&CK matrix version to 10.1
• Cached downloaded ATT&CK STIX bundles to increase build time

[github-actions[bot]]

This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-80-methodology/

[github-actions[bot]]

This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-80-methodology/

[github-actions[bot]]

This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-80-methodology/

[github-actions[bot]]

This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-80-methodology/

[rossj-en]

Allison makes a number of good points above. Concur enthusiastically with matching the visual elements from other areas of the site, and adding links to the header and footer for user ease of access.

Due to the amount of text it is helpful having the methodology on a separate page. As far as page formatting, it would be helpful to have a document tree or table of contents that lists and links the section headers. Overall the font is a little small for the amount of text displayed. The content could benefit from some graphics and diagrams as well.

For the main About page I like the "left text" "right links" design on the Framework landing pages (example VERIS). We could have the Build a Threat-Informed Defense Mindset title and content on the left, with links for each "section" and the separate Methodology page on the right.

Having the use cases on a separate page buries that information. I would eliminate the Use Cases page, folding the Use Cases > Target Audience section into About > Who Should Use Mappings Explorer and also folding the Use Cases > Usage into About > What is Mappings Explorer For. Finally, would move the Use Cases > User Stories to the bottom of the main About page. This would preserve/integrate all of the Use Cases content to one page, aligned with the overall website style and design, without making the About page too lengthy.

[mehaase]

@allisonrobbins I rebased and made the changes that we discussed. I opened up another jira ticket to finalize the language, and as we discussed we'll add a ticket for you to do a final pass on the layout. So barring any major issues, let's close out this issue.

[github-actions[bot]]

This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-80-methodology/

[allisonrobbins]

@mehaase This looks good to me!