Fix contributor's guide links

.github/PULL_REQUEST_TEMPLATE.md

@@ -32,6 +32,8 @@ apply to this PR, comment it out or delete it. -->
 Thank you so much for your PR!  To help us review your contribution, please
 consider the following points:
 
+- A contributor's guide is available at https://geocat-viz.readthedocs.io/en/latest/contrib.html
+
 - Fork this repository and open the PR from your fork. Do not directly work on
   the NCAR/geocat-viz repository.
 

CONTRIBUTING.md

@@ -1,56 +1,2 @@
-Please first refer to [GeoCAT Contributor's Guide](https://geocat.ucar.edu/pages/contributing.html) for overall
-contribution guidelines (such as detailed description of GeoCAT structure, forking, repository cloning,
-branching, etc.). Once you determine that a function should be contributed under this repo, please refer to the
-following contribution guidelines:
+The contributor's guide for GeoCAT-viz can be found in our [online documentation](https://geocat-viz.readthedocs.io/en/latest/contrib.html).
 
-
-# Adding new utility functions to the Geocat-viz repo
-
-1. Please check the followings to ensure that the functionality you are about to work on has not been ported yet:
-
-    - Functions implemented in `$GEOCAT_VIZ/src/geocat/viz/util/util.py`,
-
-    - The list of [GeoCAT-viz Issues](https://github.com/NCAR/GeoCAT-viz/issues) and
-    [GeoCAT-examples Issues](https://github.com/NCAR/GeoCAT-examples/issues) to see if any of
-    the existing to-do items are something you might be interested in working on,
-
-        - If so, please comment (or self-assign the issue if you have permissions to do so) indicating that
-        you intend to work on it.
-
-        - Otherwise, you may create and self-assign an issue under
-        [GeoCAT-viz Issues](https://github.com/NCAR/GeoCAT-viz/issues)
-        that describes need for the functionality you are planning to contribute.
-
-2. Define a new function and implement it under the `$GEOCAT_VIZ/src/geocat/viz/util/util.py`.
-
-# Adding new plotting utility functionality to the Geocat-viz repo
-
-1. Please check the followings to ensure that the functionality you are about to work on has not been ported yet:
-
-    - Functions implemented in `$GEOCAT_VIZ/src/geocat/viz/`
-
-    - The list of [GeoCAT-viz Issues](https://github.com/NCAR/GeoCAT-viz/issues) and
-    [GeoCAT-examples Issues](https://github.com/NCAR/GeoCAT-examples/issues) to see if any of
-    the existing to-do items are something you might be interested in working on,
-
-        - If so, please comment (or self-assign the issue if you have permissions to do so) indicating that
-        you intend to work on it.
-
-        - Otherwise, you may create and self-assign an issue under
-        [GeoCAT-viz Issues](https://github.com/NCAR/GeoCAT-viz/issues)
-        that describes need for the functionality you are planning to contribute.
-
-2. Determine which module is the best home for your new function.
-
-    - If necessary, create a new `.py` module under `$GEOCAT_VIZ/src/geocat/viz/`.
-
-    - Implement your plotting function inside the chosen module, making
-    use of the pre-defined parent classes if appropriate
-
-3. Add new modules to the namespace by adding it to `$GEOCAT_VIZ/src/geocat/viz/__init__.py`
-
-# Adding functionality to the User API Documentation
-
-1. Add your new function to `GEOCAT_VIZ/docs/user_api/index.rst`.
-
-2. Ensure that the function docstring has examples linking to relevant GeoCAT-Examples scripts.

docs/index.rst

@@ -89,7 +89,7 @@ plotting packages.
    :caption: For Developers
 
    Release Notes <release-notes.rst>
-   Contributor's Guide <https://github.com/NCAR/geocat-viz/blob/main/CONTRIBUTING.md>
+   Contributor's Guide <contrib.rst>
    Roadmap <https://geocat.ucar.edu/pages/roadmap.html>
 
 .. toctree::