feat: converting documentation to mkdocs

Author: gvwilson

.gitignore

@@ -13,6 +13,8 @@ tests/test_orca/images/linux/failed/
 
 doc/python/raw.githubusercontent.com/
 
+docs/
+
 # Don't ignore dataset files
 !*.csv.gz
 !*.geojson.gz

CONTRIBUTING.md

@@ -8,7 +8,7 @@ then explains the technical aspects of preparing your contribution.
 
 ## Code of Conduct
 
-Please note that all contributos are required to abide by our [Code of Conduct](CODE_OF_CONDUCT.md).
+Please note that all contributos are required to abide by our Code of Conduct.
 
 ## Different Ways to Contribute
 
@@ -38,7 +38,7 @@ it is important to understand the structure of the code and the repository.
     These are organized in subdirectories according to what they test:
     see the "Setup" section below for more details.
 
--   Documentation is found in `doc/`, and its structure is described in [its README file](doc/README.md).
+-   Documentation is found in `doc/`, and its structure is described in its README file.
     The documentation is a great place to start contributing,
     since you can add or modify examples without setting up a full environment.
 

mkdocs.yml

@@ -0,0 +1,21 @@
+site_name: "Plotly.py Docs"
+docs_dir: pages
+site_dir: docs
+nav:
+- Home: index.md
+- Project:
+  - license.md
+  - conduct.md
+  - contributing.md
+
+theme:
+  name: "material"
+
+markdown_extensions:
+- def_list
+- markdown_include.include:
+    base_path: docs
+- footnotes
+
+exclude_docs: >
+  *~

pages/conduct.md

@@ -0,0 +1 @@
+{!../CODE_OF_CONDUCT.md!}

pages/contributing.md

@@ -0,0 +1 @@
+{!../CONTRIBUTING.md!}

pages/index.md

@@ -0,0 +1 @@
+{!../README.md!}

pages/license.md

@@ -0,0 +1 @@
+{!../LICENSE.txt!}

pyproject.toml

@@ -50,7 +50,11 @@ dev_core = [
 dev_build = [
     "plotly[dev_core]",
     "build",
-    "jupyter"
+    "jupyter",
+    "markdown-include",
+    "mkdocs",
+    "mkdocs-material",
+    "mkdocstrings[python]"
 ]
 dev_optional = [
     "plotly[dev_build]",