Add developer guide (#6)

* begin incorporating contributing

* add style guide, dev guide

* fix indendtation

Author: akaszynski

doc/source/coding_style/best_practices.rst

@@ -0,0 +1,4 @@
+.. _style-guide-enforcement:
+
+Style Guide Enforcement
+=======================

doc/source/coding_style/flake8.rst

@@ -0,0 +1,28 @@
+.. _coding_style:
+
+Coding Style
+************
+
+The PyAnsys libraries are expected to follow `PEP8`_ will
+attempt to be consistent in style and formatting with the "big three"
+data science libraries: `NumPy`_, `SciPy`_, and `pandas`_.
+
+.. _NumPy: https://numpy.org/
+.. _SciPy: https://www.scipy.org/
+.. _pandas: https://pandas.pydata.org/
+.. _PEP8: https://www.python.org/dev/peps/pep-0008/
+
+
+TODO:
+
+* Describe flake8 standards (in subpage), include example ``.flake8``
+  with minimum standards.
+* Include anythin we've written from other documentation either in
+  this page or other pages.
+
+.. toctree::
+   :hidden:
+   :maxdepth: 3
+
+   flake8
+   best_practices

doc/source/coding_style/index.rst

@@ -1,7 +1,7 @@
 .. _api_documentation:
 
-API Documentation
-#################
+Documentation Style
+###################
 Good documentation drives library adoption and usage and is the
 foundation for a good developer experience.  Even with the best
 interfaces and the most functional product, no one will adopt the API