Transition MET user's guide from lyx to sphinx.

[JohnHalleyGotway]

Describe the Task

Follow the same workflow for transitioning METplus and METviewer UGs to sphinx

Time Estimate

Estimate the amount of work required here.
Issues should represent approximately 1 to 3 days of work.

Sub-Issues

Consider breaking the task down into sub-issues.

• Try using pandoc to see if any files can be automatically converted.
• Create gh-pages branch
• Create docs subdirectory
• Create some template files to get Lisa started
• Move basic content over to Sphinx by Monday and merge into develop
• Incorporate recent changes from the transition Google doc and merge into develop.
• Add references and titles to the MET Documentation
• Publish the user's guide using gh-pages.

Relevant Deadlines

5/3 if possible but if not 5/20 (met-9.1-beta2)

Funding Source

2702691 - Dan (30hrs), Julie (60hrs), Lisa(60hrs)

Define the Metadata

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

• Review projects and select relevant Repository and Organization ones
• Select milestone

Define Related Issue(s)

Consider the impact to the other METplus components.

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

Task Checklist

See the METplus Workflow for details.

• Complete the issue definition above.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the task and verify your changes.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop, listing the <Issue Number> in the title.
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.

[lisagoodrich]

Moved basic content over to Sphinx by Monday and merged into develop (DONE 4/21/20 Lisa Goodrich)

[jprestop]

This work is complete.