MkDocs for Material (#545)

* Create mkdocs.yaml

* Create mkdocs.yml

* Update mkdocs.yml

* Update mkdocs.yml

* Update mkdocs.yml

* Update mkdocs.yml

* Update mkdocs.yml

* Update README.md

* Update coding_conventions.md

* Update documentation_guidelines.md

* Update testing.md

* Update heroku.md

* Update hetzner_ubuntu.md

* Update google_search.md

* Update introduction.md

* Update make_your_own.md

* Update stable_diffusion.md

* Update wolfram.md

* Update proxy.md

* Update user_auth_system.md

* Update bing_jailbreak_info.md

* Update breaking_changes.md

* Update multilingual_information.md

* Update project_origin.md

* Update tech_stack.md

* Update apis_and_tokens.md

* Update docker_install.md

* Update linux_install.md

* Update mac_install.md

* Update windows_install.md

* Update mkdocs.yml

* Update mkdocs.yml

* Update documentation_guidelines.md

* Add files via upload

* Create temp.txt

* Add files via upload

* Delete logo.png

* Create index.md

* Update mkdocs.yml

* Update mkdocs.yml

* Delete temp.txt

* Update README.md

* Update README.md

---------

Co-authored-by: Danny Avila <110412045+danny-avila@users.noreply.github.com>

docs/contributions/documentation_guidelines.md

@@ -4,11 +4,6 @@
  - For new features, create new documentation and place it in the appropriate folder(s)
  	- If the feature adds new functionality, it should be added to the feature section of the main Readme 
  - When you create a new document, do not forget to add it to the table of content
- - Add a shortcut that point back to the [README.MD](../../README.md) in the bottom of new documents (look at other docs for example)
  - Use `#` / `##` / `###` for the different section of the doc
  - Do not add unrelated information to an existing document, create a new one if needed
  - For incremental updates, you need to update the main **README.MD**
-
----
-
-## [Go Back to ReadMe](../../README.md)