Skip to content

Better documentation #377

@daniel-slaugh

Description

@daniel-slaugh

A couple things to work on for documentation this month.

  • @horsburgh mentioned in a meeting he'd like certain parts of the documentation to be easier to find. Follow up and make a plan based on his recommendations.
  • We need to decide if we're versioning the documentation per release or not. If so, work out the process of letting the user pick their hydroserver version number on the documentation website and update content accordingly.
  • Update images to reflect current state of websites
  • It would be nice to more tightly couple the code to documentation that references our tools. Research methods other teams use keep their docs updated and true to code.

Metadata

Metadata

Assignees

Labels

docsImprovements or additions to documentation

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions