initial drift manager conflict and cleanups to get jdiff drift managed

Author: jeffkala

.cookiecutter.json

@@ -14,9 +14,6 @@
         "project_with_config_settings": "no",
         "generate_docs": "yes",
         "version": "1.0.1",
-<<<<<<< HEAD
-        "original_publish_year": "2022"
-=======
         "original_publish_year": "2022",
         "_drift_manager": {
             "template": "https://github.com/networktocode-llc/cookiecutter-ntc.git",
@@ -29,6 +26,5 @@
             "baked_commit_ref": "bc931311336d391d878202dba239389783ee9f09",
             "drift_managed_branch": "develop"
         }
->>>>>>> 75750bd (Cookie updated targeting develop by NetworkToCode Cookie Drift Manager Tool)
     }
 }

README.md

@@ -1,17 +1,7 @@
 # Jdiff
 
-<!--
-Developer Note - Remove Me!
-
-The README will have certain links/images broken until the PR is merged into `develop`. Update the GitHub links with whichever branch you're using (main etc.) if different.
-
-The logo of the project is a placeholder (docs/images/icon-jdiff.png) - please replace it with your app icon, making sure it's at least 200x200px and has a transparent background!
-
-To avoid extra work and temporary links, make sure that publishing docs (or merging a PR) is done at the same time as setting up the docs site on RTD, then test everything.
--->
-
 <p align="center">
-  <img src="https://raw.githubusercontent.com/networktocode/jdiff/develop/docs/images/icon-Jdiff.png" class="logo" height="200px">
+  <img src="https://raw.githubusercontent.com/networktocode/jdiff/develop/docs/images/jdiff_logo.png" class="logo" height="200px">
   <br>
   <a href="https://github.com/networktocode/jdiff/actions"><img src="https://github.com/networktocode/jdiff/actions/workflows/ci.yml/badge.svg?branch=main"></a>
   <a href="https://jdiff.readthedocs.io/en/latest/"><img src="https://readthedocs.org/projects/jdiff/badge/"></a>
@@ -22,23 +12,23 @@ To avoid extra work and temporary links, make sure that publishing docs (or merg
 
 ## Overview
 
-> Developer Note: Add a long (2-3 paragraphs) description of what the library does, what problems it solves, etc.
+`jdiff` is a lightweight Python library allowing you to examine structured data. `jdiff` provides an interface to intelligently compare JSON data objects and test for the presence (or absence) of keys. You can also examine and compare corresponding key-values.
 
 ## Documentation
 
 Full documentation for this library can be found over on the [Jdiff Docs](https://jdiff.readthedocs.io/) website:
 
-- [User Guide](https://jdiff.readthedocs.io/user/app_overview/) - Overview, Using the Library, Getting Started.
-- [Administrator Guide](https://jdiff.readthedocs.io/admin/install/) - How to Install, Configure, Upgrade, or Uninstall the Library.
-- [Developer Guide](https://jdiff.readthedocs.io/dev/contributing/) - Extending the Library, Code Reference, Contribution Guide.
-- [Release Notes / Changelog](https://jdiff.readthedocs.io/admin/release_notes/).
-- [Frequently Asked Questions](https://jdiff.readthedocs.io/user/faq/).
+- [User Guide](https://jdiff.readthedocs.io/en/latest/user/lib_overview/) - Overview, Using the library, Getting Started.
+- [Administrator Guide](https://jdiff.readthedocs.io/en/latest/admin/install/) - How to Install, Configure, Upgrade, or Uninstall the library.
+- [Developer Guide](https://jdiff.readthedocs.io/en/latest/dev/contributing/) - Extending the library, Code Reference, Contribution Guide.
+- [Release Notes / Changelog](https://jdiff.readthedocs.io/en/latest/admin/release_notes/).
+- [Frequently Asked Questions](https://jdiff.readthedocs.io/en/latest/user/faq/).
 
 ### Contributing to the Documentation
 
 You can find all the Markdown source for the App documentation under the [`docs`](https://github.com/networktocode/jdiff/tree/develop/docs) folder in this repository. For simple edits, a Markdown capable editor is sufficient: clone the repository and edit away.
 
-If you need to view the fully-generated documentation site, you can build it with [MkDocs](https://www.mkdocs.org/). A container hosting the documentation can be started using the `invoke` commands (details in the [Development Environment Guide](https://jdiff/dev/dev_environment/#docker-development-environment)) on [http://localhost:8001](http://localhost:8001). Using this container, as your changes to the documentation are saved, they will be automatically rebuilt and any pages currently being viewed will be reloaded in your browser.
+If you need to view the fully-generated documentation site, you can build it with [MkDocs](https://www.mkdocs.org/). A container hosting the documentation can be started using the `invoke` commands (details in the [Development Environment Guide](https://jdiff.readthedocs.io/en/latest/dev/dev_environment/#docker-development-environment)) on [http://localhost:8001](http://localhost:8001). Using this container, as your changes to the documentation are saved, they will be automatically rebuilt and any pages currently being viewed will be reloaded in your browser.
 
 Any PRs with fixes or improvements are very welcome!
 

changes/+dne.documentation

@@ -0,0 +1 @@
+Fixed the section headers for portions of the documentation.

changes/+main.housekeeping

@@ -0,0 +1 @@
+Fix GitHub release failing in CI pipeline.

changes/.gitignore

@@ -0,0 +1 @@
+Added documentation on the release checklist and process for the library.

changes/.gitkeep

@@ -0,0 +1 @@
+Fix GitHub release failing in CI pipeline.

changes/133.fixed

@@ -0,0 +1 @@
+Fix invoke volume path.