Add: package versionioning, pypi / conda publishing & code format pre-commit pages (Reviews Welcome!)

index.md

@@ -109,6 +109,13 @@ We assume that you are here because you are:
 
 Well, friend, you've come to the right place!
 
+:::{figure-md} fig-target
+
+<img src="/images/python-flying-xkcd.png" alt="xkcd comic showing a stick figure on the ground and one in the air. The one on the ground is saying. `You're flying! how?`  The person in the air replies  `Python!` Below is a 3 rectangle comic with the following text in each box. box 1 - I learned it last night. Everything is so simple. Hello world is just print hello world. box 2 - the person on the ground says - come join us programming is fun again. it's a whole new world. But how are you flying? box 3 - the person flying says - i just typed import antigravity. I also sampled everything in the medicine cabinet. But i think this is the python. the person on the ground is saying - that's it?" width="400px">
+
+Many love to use Python because it is a clean language to learn. It also is incredibly flexible allowing it to be used across numerous domains. Source: xkcd comics.
+:::
+
 ## What you will find in this guidebook
 
 This guidebook contains:
@@ -125,3 +132,63 @@ Good meets the requirements. Going beyond the minimum can make package maintenan
 
 This guide is now a work in progress. If you have ideas of things you'd like
 to see here, [we invite you to open an issue on GitHub that details any changes or additions that you'd like to see.](https://github.com/pyOpenSci/python-package-guide/issues).
+
+```{toctree}
+:hidden:
+:caption: Documentation
+
+Documentation Overview <documentation/index>
+Write User Documentation <documentation/write-user-documentation/intro>
+Core GitHub Repository Files <documentation/repository-files/intro>
+Documentation Tools & Hosting  <documentation/hosting-tools/intro>
+```
+
+```{toctree}
+:hidden:
+:caption: Package structure & code style
+
+Manage Package Versions <package-structure-code/python-package-versions>
+Publish Package PyPI Conda <package-structure-code/publish-python-package-pypi-conda>
+Code Style & Format <package-structure-code/code-style-linting-format>
+Intro <python-packaging/intro>
+
+```
+
+```{toctree}
+:hidden:
+:caption: CI and Testing
+
+Intro <ci-and-testing/intro>
+```
+
+<!--
+COMMENTED OUT TEXT TO BE MOVED
+
+
+# TODO LINK TO CI BUILDS FOR Documentation>
+Maybe we can curate a list of CI builds that people can use??? or is that moving too close to a cookie cutter situation
+
+The text below is being moved to the packaging infrastructure section which
+doesn't exist YET... but will soon .
+pyOpenSci packages must:
+
+- Contain full documentation for any user-facing functions.
+- Have a test suite that covers the major functionality of the package.
+- Use continuous integration.
+- Use an OSI approved software license.
+
+
+## Other recommendations
+### Python version support
+You should always be explicit about which versions of Python your package supports.
+Keeping compatibility with old Python versions can be difficult as functionality changes.
+A good rule of thumb is that the package should support, at least,
+the latest three Python versions (e.g., 3.8, 3.7, 3.6).
+
+### Code Style
+pyOpenSci encourages authors to consult [PEP 8](https://www.python.org/dev/peps/pep-0008/) for information on how to style your code.
+
+### Linting
+An automatic linter (e.g. flake8) can help ensure your code is clean and free of syntax errors. These can be integrated with your CI.
+
+-->