Create dropdown menus for Appendix A

[lisagoodrich]

Replace italics below with details for this issue.

Describe the Task

Sphinx Design for Dropdown menus is a new way of creating dropdown menus. These menus are searchable using ctrl - f or the search function in READTHEDOCS. The old version (sphinx-panels) wasn't searchable. In order to maintain consistency and for ease of documentation viewing, change the questions and answers in Appendix A to dropdown menus.

In order to be able to link to the questions, they will need to stay as sections. Every dropdown menu should be labeled "Answer". The answer documentation will be in the dropdown menu. The question will be viewable as a section header.

Please note that changes have already been made to the config.py and the requirements.rst file. sphinx_design with an underscore needed to be added to the config.py file. And sphinx-design with a dash needed to be added to the requirements.rst file. If this is going to be done on other METplus products, this may need to be added to work.

Time Estimate

Estimate the amount of work required here.
1 to 2 days of work.

Sub-Issues

Consider breaking the task down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.
There is no hard deadline for this

Funding Source

2792541

Define the Metadata

None

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Repository and/or Organization level Project(s) or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next official version or Future Versions

Define Related Issue(s)

Consider the impact to the other METplus components. NO IMPACT

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issues
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[lisagoodrich]

This was not part of the task but once I changed the indentation to accommodate the dropdown menus, this threw off the line spacing. Some lines went over the 79 characters per line. I made sure the new spacing is under 79 characters per line. Exceptions to this include, code blocks, web addresses or headers.

[lisagoodrich]

Work has been completed.