Create pull-down in User Guide configuration file

[bikegeek]

Replace italics below with details for this issue.

Describe the Task

Users are overwhelmed with what the settings in the configuration file do. The configuration files are long and adding additional content following the config files makes it inconvenient for users to navigate the User's Guide. Providing pull down menus corresponding to salient settings in the config file will make navigation easier for users.

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.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

Define the source of funding and account keys here or state NONE.

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

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

Define Related Issue(s)

Consider the impact to the other METplus components.

• 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.
• Add any new Python packages to the METplus Components Python Requirements table.
• 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]

@bikegeek I've got a couple questions about this.

1. Do you want me to add dropdown menus for ALL of the documentation in the METplotpy User's Guide? https://metplotpy.readthedocs.io/en/latest/Users_Guide/histogram.html
2. Or is it just for the longer chapters?
3. It says to consider the implications to the other MET products. I'm not sure what this means. Am I supposed to do dropdown menus for all the different MET products?
   Let me know if it's easier to have a conversation about this instead.

[bikegeek]

@lisa Goodrich ***@***.***> I need to fill in more details for this. This will impact only the METplotpy documentation, but I first need to provide you with content to populate the pull-down menus. Based on user feedback, we need to provide more detailed documentation for the config files. I can get you some content some time next week. We will need to do this for *all* the plot types supported by METplotpy, so this will be an extensive amount of work. --------------- Minna Win Pronouns: she/her National Center for Atmospheric Research Research Applications Lab Developmental Testbed Center Phone: 303-497-8423 Fax: 303-497-8401 ---------------

…

On Wed, Sep 27, 2023 at 3:56 PM lisagoodrich ***@***.***> wrote: @bikegeek <https://github.com/bikegeek> I've got a couple questions about this. 1. Do you want me to add dropdown menus for ALL of the documentation in the METplotpy User's Guide? https://metplotpy.readthedocs.io/en/latest/Users_Guide/histogram.html 2. Or is it just for the longer chapters? 3. It says to consider the implications to the other MET products. I'm not sure what this means. Am I supposed to do dropdown menus for all the different MET products? Let me know if it's easier to have a conversation about this instead. — Reply to this email directly, view it on GitHub <#390 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4UJHUCYQSCKPHEMK26TW3X4SOKNANCNFSM6AAAAAA5ICBVFY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lisagoodrich]

Hi @bikegeek,

@TaraJensen has given the okay for me to start working on things. I thought this might be an easy place to start. Do you have time to discuss this with me or should I move onto another task?

[bikegeek]

Can you move to another task? This would fit in to the RC1 work, since it is documentation work and I won't be able to tackle any documentation tasks until after the beta6 release.

…

On Thu, Aug 1, 2024 at 2:46 PM lisagoodrich ***@***.***> wrote: Hi @bikegeek <https://github.com/bikegeek>, @TaraJensen <https://github.com/TaraJensen> has given the okay for me to start working on things. I thought this might be an easy place to start. Do you have time to discuss this with me or should I move onto another task? — Reply to this email directly, view it on GitHub <#390 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4UJHWKENPVYEBNPJ3JZILZPKNDDAVCNFSM6AAAAABL3JTZZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRTHE2TIMRSGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[lisagoodrich]

No problem. Thanks for letting me know.