docs: update index.rst; add reference page on making python packages

Author: aleaf

docs/source/index.rst

@@ -26,4 +26,5 @@ We encourage students to explore these materials for their own study or to reach
    Additional links <SOME_HELPFUL_LINKS.md>
    Contributing <contributing>
    Glossary of jargon <glossary_of_jargon>
-   Scientific coding best practices <best_practices>
+   Making a Python package <packaging>
+   Scientific programming best practices <best_practices>

docs/source/packaging.md

@@ -0,0 +1,29 @@
+# Packaging: the next level
+
+* Is your hard drive littered with miscellaneous scripts and
+Jupyter Notebooks that do similar things?
+* Are you copying and pasting the same code repeatedly?
+* Are you struggling to keep track of different versions of that
+code, or where you made the last change?
+* Are you sharing code over email or chat?
+
+**If you answered yes to a few of these, you may need a package!**
+
+With a package we can:
+* Collaborate on code in one place
+* Share, install and import any version into any script
+* Have confidence with automated tests; even as things change
+* Create and share nice looking documentation
+
+Making a package needn’t be difficult, nor does it
+require “finished” code or formal publication. You can write
+packages for yourself or your internal colleagues! With
+cookiecutter templates, you can be up and running with a single
+code file in minutes and develop the package as you work on
+your project! 
+
+**Packaging Resources**
+
+[Scientific Python Library Development Guide](https://learn.scientific-python.org/development/)
+
+[Bootstrap a Scientific Python Library](https://nsls-ii.github.io/scientific-python-cookiecutter/)