Nick/contributing tutorial (#367)

* Internal: Try new link checker

* Internal: Add codespell and fix typos.

* Internal: See if codespell precommit finds config.

* Internal: Found config. Now enable reading it

* MATLAB: Add initial support for more matlab support.

* DEV: Updating contributing doc for more details on adding a tutorial

Closes #366

Author: ntjohnson1

CONTRIBUTING.md

@@ -76,6 +76,28 @@ current or filing a new [issue](https://github.com/sandialabs/pyttb/issues).
    ```
    2. Clear notebook outputs if run locally see `nbstripout` in our [pre-commit configuration](.pre-commit-config.yaml)
 
+### Adding tutorials
+
+1. Follow general setup from above
+   1. Checkout a branch to make your changes
+   1. Install from source with dev and doc dependencies
+   1. Verify you can build the existing docs with sphinx
+
+1. Create a new Jupyter notebook in [./docs/source/tutorial](./docs/source/tutorial)
+   1. Our current convention is to prefix the filename with the type of tutorial and all lower case
+
+1. Add a reference to your notebook in [./docs/source/tutorials.rst](./docs/source/tutorials.rst)
+
+1. Rebuild the docs, review locally, and iterate on changes until ready for review
+
+#### Tutorial References
+Generally, inspecting existing documentation or tutorials should provide a reasonable starting point for capabilities,
+but the following links may be useful if that's not sufficient.
+
+1. We use [sphinx](https://www.sphinx-doc.org/) to automatically build our docs and may be useful for `.rst` issues
+
+1. We use [myst-nb](https://myst-nb.readthedocs.io/) to render our notebooks to documentation
+
 ## GitHub Workflow
 
 ### Proposing Changes