renaming api_docs to reference

Author: isabelizimm

docs/source/api_doc/vetiver.pin_read_write.rst

@@ -60,10 +60,12 @@
     "use_repository_button": True,
     "use_issues_button": True,
     "use_edit_page_button": True,
+    "home_page_in_toc": True
 
 }
 
 html_logo = "../figures/logo.png"
+html_favicon = "../figures/logo.png"
 
 
 # Add any paths that contain custom static files (such as style sheets) here,

docs/source/conf.py

@@ -1,28 +1,27 @@
-.. vetiver documentation master file, created by
-   sphinx-quickstart on Thu Mar  3 14:13:21 2022.
-   You can adapt this file completely to your liking, but it should at least
-   contain the root `toctree` directive.
-
-vetiver
+vetiver 🏺
 ===================================
 The goal of vetiver is to provide fluent tooling to version, share, deploy, and monitor a trained model. Functions handle both recording and checking the model’s input data prototype, and predicting from a remote API endpoint. 
 You can use vetiver with:
 
-- scikit-learn
-- pytorch
+- `scikit-learn <https://scikit-learn.org/stable/>`_
+- `pytorch <https://pytorch.org/>`_
+
+This website documents the public API of Vetiver (for Python). See the `main Vetiver website <https://juliasilge.github.io/vetiver.dev/>`_ for
+a more holistic introduction to the API. The left-hand sidebar lists the full public
+API, and the sections below (linked to the right-hand sidebar) break it into similar groups, based on task.
 
 .. toctree::
    :maxdepth: 2
    :caption: Contents:
 
-
 Version
 ==================
 
 .. currentmodule:: vetiver
 
 .. autosummary::
-   :toctree: api_doc/
+   :toctree: reference/
+   :caption: Version
 
    ~VetiverModel
    ~pin_read_write.vetiver_pin_read
@@ -34,24 +33,14 @@ Deploy
 .. currentmodule:: vetiver
 
 .. autosummary::
-   :toctree: api_doc/
-
-   ~VetiverModel
-
-Deploy
-==================
-
-.. currentmodule:: vetiver
-
-.. autosummary::
-   :toctree: api_doc/
-
-   ~VetiverModel
+   :toctree: reference/
+   :caption: Deploy
 
    ~VetiverAPI
    ~VetiverAPI.run
    ~VetiverAPI.vetiver_post
    ~vetiver_endpoint
+   ~predict
    ~load_pkgs
    ~vetiver_write_app
-   ~vetiver_write_docker
+   ~vetiver_write_docker