Planned edits to Documentation

[mzuranski]

• Incorporate Ubuntu install instructions (GEMPAK & Ubuntu 20.04 #57 (comment)). Note the version number, if nothing else update the version but can I make that dynamic somehow? 🤔
• Make notes regarding IMCBAR Frequency value ignored for certain Nexrad products #76 on the IMCBAR page

Is there anything else worth doing before having Unidata redirect their docs page to here?

[akrherz]

Ideally, we would want a github action that built the docs from the GEMPAK main branch and pushed them to the gh-pages branch automagically.

I don't think we need to wait for anything before having Unidata add their redirect.

[mzuranski]

Ideally, we would want a github action that built the docs from the GEMPAK main branch and pushed them to the gh-pages branch automagically.

I'm not sure how to conjure that magic up. Is there a reason people shouldn't edit the gh-pages branch directly?

I don't think we need to wait for anything before having Unidata add their redirect.

Awesome, I'll let them know. 👍

[akrherz]

I'm not sure how to conjure that magic up. Is there a reason people shouldn't edit the gh-pages branch directly?

Within the GEMPAK source tree, check out the docs folder and all the generation scripts there. The docs are meant to be built from the source tree and then committed to the gh-pages branch via CI. Reviewing the generation now, there is some work to be done to get there :)