Restructure docs for new website

[ashleynilo]

Related Issue(s)	F Prime Website Refresh
Has Unit Tests (y/n)	n
Documentation Included (y/n)	n (documentation is in the internal JPL repo with custom pages)

---

Change Description

• Major restructure of the website information architecture based on the diataxis method and to make room for new, informational pages on F Prime. The key categories now are
  • Home
  • Overview
  • Getting Started
  • Documentation
    • Tutorials
    • User Manual
    • How To
    • Reference
  • Support
  • Events
• Added new markdown files that include a link to the custom HTML templates and a link to that page on the website for the user to view. Custom pages are not viewable via the public F Prime GitHub repository
• Added new high-level overview pages for each documentation topic (Tutorials, User Manual, How To, and Reference)
• Removed _data and _includes folders and the files inside them since MkDocs have its own built-in navigation and table of contents
• Removed _config.yml since MkDocs has its own config file
• Updated headings of ALL files so that there’s only one H1 as the title of the page, adjusting the remaining headings as needed so that headings aren’t skipped
• Renamed some folders and pages to only use all lowercase and hyphens
  Updated links throughout all of the pages to match the new information architecture
• Using improved GitHub-style notes (e.g. > [!NOTE]) for pretty display
• Minor grammar/typo changes

Rationale

Refreshed the F Prime Website to use the MkDocs documentation framework with the Material for MkDocs theme. Along with the new framework the site will now be fully accessible via https://fprime.jpl.nasa.gov/. Many items in the fprime/docs folder have been restructured to fit the MkDocs framework and is also based on the diataxis method with research from the JPL Human Systems Integration group.

Testing/Review Recommendations

Major changes are mainly within the new structure of the files. Please check for any broken links or any content/files that may have been unintentionally removed or set to a certain heading hierarchy.

Future Work

None at the moment.

[thomas-bc]

Closing for now as we are still in dev process so this is triggering CI too often. Will reopen when we're ready for review

[thomas-bc]

TODO:

• Lock docs/auto-documentation branch to make sure no changes are going in
• [ ]

[LeStarch]

Website looks nice, content was approved by release authority, and @thomas-bc says we are ready.

[thomas-bc]

🎉
🚀