-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix broken link to met-data documentation #3378
Conversation
dlebauer
commented
Sep 11, 2024
•
edited
Loading
edited
- fix broken link
- Updated pecan_standards section to standardize heading level, e.g. 'input standards' and 'output standards' are now at the same level, and will show up in TOC on left. Previously the entire page had the title "Time Standards" which was confusing
modules/data.atmosphere/README.md
Outdated
@@ -32,7 +32,7 @@ The PEcAn.data.atmosphere package is 'standalone'. | |||
|
|||
## PEcAn variable names | |||
|
|||
See https://pecanproject.github.io/pecan-documentation/latest/met-data.html | |||
For the most updated list, see https://pecanproject.github.io/pecan-documentation/develop/time-standard.html#input-standards |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think links in most other docs point to the main branch (confusingly latest
on github.io and main
on github.com). Is it important for this one to be the develop version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I assumed latest == develop. Happy to change, but it seems that main can be years out of date and in practice it seems most people use develop. Probably more trouble than it is worth to parameterize this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed, I'm not 100% if I understand correctly, but only master
and develop
and other branch names in the URL point to an existing page in the documentation.
Updated so that indents are consistent, e.g. 'input standards' and 'output standards' are at the same level, and will show up in TOC on left
Co-authored-by: David LeBauer <[email protected]>