-
Notifications
You must be signed in to change notification settings - Fork 55
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
Creating quick start guide as part of overall docs improvements #249
Conversation
…hange later once reorganization is complete
@hCraker I included that one comment above for something I saw immediately, but I'd really like to be able to check out the rendered RTD pages. Could you merge the docs branch in to this branch to pull over the fix? |
docs/getting_started/overview.rst
Outdated
GeoCAT-comp's open-source nature allows for more community engagement than a traditional software development workflow | ||
does. As advances are made in the realm of geoscience, new tools will be needed to analyze new datasets. We are dedicated | ||
to addressing user needs and encourage users to submit feature requests and contributions to our GitHub as well as | ||
participate in discussions. See our `support <support>`_ page for info on how to submit bug reports and requests and how to get involved. |
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.
participate in discussions. See our `support <support>`_ page for info on how to submit bug reports and requests and how to get involved. | |
participate in discussions. See our `support <support>`_ page for info on how to submit bug report, feature requests, and how to get involved. |
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.
You're right this needs rewording. How does this sound?
See our
support <support>
_ page for info on how to submit bug reports, request new
features, and get involved.
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.
Yeah, that sounds better!
@@ -65,3 +66,4 @@ extra: | |||
- erogluorhan # O. Eroglu https://github.com/erogluorhan | |||
- anissa111 # A. Zacharias https://github.com/anissa111 | |||
- michaelavs # M. Sizemore https://github.com/michaelavs | |||
- hcraker # H. Craker https://github.com/hcraker |
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.
We're going to be removing this file here soon, you should add this change to the feedstock repo instead!
docs/getting_started/examples.rst
Outdated
Usage Examples | ||
============== | ||
|
||
Short Tutorial | ||
-------------- |
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 don't think we need both headers if we're going to drop the second subhead. Maybe we could do something like:
Usage Examples | |
============== | |
Short Tutorial | |
-------------- | |
Quick Start Examples | |
-------------------- | |
For more comprehensive examples, go check out :ref:`examples` |
Disclaimer: I have no idea if that linkage will actually work
docs/getting_started/examples.rst
Outdated
|
||
Short Tutorial | ||
-------------- | ||
Calculate saturation vapor pressure from :code:`Numpy` Data:: |
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.
Calculate saturation vapor pressure from :code:`Numpy` Data:: | |
Calculate saturation vapor pressure from ``numpy`` data:: |
Thankfully, we don't have to do the full code directive to get this notation anymore
docs/getting_started/overview.rst
Outdated
GeoCAT-comp's open-source nature allows for more community engagement than a traditional software development workflow | ||
does. As advances are made in the realm of geoscience, new tools will be needed to analyze new datasets. We are dedicated | ||
to addressing user needs and encourage users to submit feature requests and contributions to our GitHub as well as | ||
participate in discussions. See our `support <support>`_ page for info on how to submit bug reports and requests and how to get involved. |
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.
This link here actually doesn't work. I think you might want to do something like :ref:support
Edit: Sorry, I can't get the formatting right on the comment. I'm talking about this: https://sublime-and-sphinx-guide.readthedocs.io/en/latest/references.html
docs/getting_started/overview.rst
Outdated
they are based upon is wrapped in Python in the GeoCAT-f2py (Fortran 2 Python) package. GeoCAT-f2py is imported by | ||
GeoCAT-comp and included in the GeoCAT-comp namespace. Simply, this means that GeoCAT-f2py functions can be called | ||
through GeoCAT-comp, so there is no need for users to import GeoCAT-f2py directly in their scripts. Information about | ||
GeoCAT-f2py can be found on the `package's homepage <https://geocat-f2py.readthedocs.io/en/>`_. |
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.
Ahh, my bad, apparently RTD doesn't like that link. Let's do:
GeoCAT-f2py can be found on the `package's homepage <https://geocat-f2py.readthedocs.io/en/>`_. | |
GeoCAT-f2py can be found on the `package's homepage <https://geocat-f2py.readthedocs.io/>`_. |
docs/getting_started/overview.rst
Outdated
functions in pure Python. With so many tools being used under the hood, GeoCAT-comp users have access to geoscience | ||
specific computational tools without needing extensive working knowledge of `Pangeo <https://pangeo.io/>`_ stack. | ||
|
||
There are syntactical benefits to using the Pangeo stack, once of which is indexing by label. NCL requires the |
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.
typo: "one of which"
Co-authored-by: Anissa Zacharias <[email protected]>
Closes #240
Part of prep for October tutorial #239
Addresses part of overall doc improvements #245