Revamping Zapdos Website

[csdechant]

Reason

This PR focuses on improving the UI/UX for the Zapdos website by:

• Making edits to the front page and navigation bar
• Adding documentation pages on the models utilized in Zapdos
• Adding tutorial pages
• Adding verification and validation pages

Design

This PR will make the following changes to the website:

• Edits to the navigation bar, which includes:
  • Having "Publications" be its own tab
  • Moving "Contributing Guidelines" and "Code Standards" into a new tab called "Contributing"
  • Adding a "Plasma Models" and "Verification & Validation" link to the Documentation tab
  • Removing MOOSE and libMesh Doxygen links from the Documentation tab, and adding a new link to the MOOSE Framework Development page
  • Removing "Tutorial Slides" and "CRANE Examples" links and replacing it with a "Example and Tutorials" link under the "Getting Started" tab.
• Edits to the front page, which includes:
  • Change the subtitle from "An open source MOOSE Framework application for the simulation of plasmas" to "An open-source application for plasma simulations"
  • Adding a short description, with links to the new "Plasma Models" page and the MOOSE landing page
  • Replacing "Multi-scale" and "Multi-platform" sub-topics to "Verification & Validation" and "Collaborative Community"
  • Reform the descriptions for each sub-topic from sentence format to bullet point format, with extra links
  • Add INL and University of Illinois - Urbana Champaign logos
• A new page with a overview of the models utilized in Zapdos
• A new overview page for the Zapdos tutorials and sub-pages for each tutorial
• A new overview page for the V&V and sub-pages for each case

Impact

The additions to the website will decrease the cost-of-entry for new Zapdos users, and make it easier to add new case examples to the website in the future.

[moosebuild]

Job Documentation, step Sync to remote on 45e627c wanted to post the following:

View the site here

This comment will be updated on new commits.

[cticenhour]

One off-hand comment since I glanced through the changeset. Can we just use the logo stored in MOOSE (in framework/doc I think) instead of taking up space in Zapdos?

[csdechant]

Are you talking about the logo on the front page of the MOOSE website? We can use that, I just thought the blue logo with the text below "INL" fit better with the other logos, instead of the black logo with the text beside "INL".

[cticenhour]

There should be another version of this blue logo in one of the media directories. Look for it in large media as well. I might be misremembering where it is located. Multiple configurations on the INL logo are stored.

[csdechant]

I found it. For future reference, it is located in moose/python/chigger/logos/inl_blue.png