📝 Overhaul the documentation (#41)

* 📝 Outlined new documentation structure

* 👷 Auto deploy the documentation

* 📝 Add an API reference

* 💚 Fix CI

* 📝 Added example usage to all default theme components

* 📝 Removed start and end date arguments

* 📝 Transfer content into website

* 📝 Added a toc to the reference

* 💚 Fixed the ci

* 📝 Removed the old documentation

* 🙈 Deleted the rendered reference

* 📝 Added the developer documentation

* 📝 Fixed missing heading

* 💚 Fix the CI

* 📝 Fix broken comment

* 📝 Added basic component creation documentation

* 📝 wrote more of the introductory docs

* ⬆️ Upgrade flake

* 📝 Started the improved basic usage guide

* 📝 Finished usage guide

* 🩹 Deleted redundant file

* 📝 add syntax highlighting for typst code blocks

* 💚 Fix ci

* 💚 Fix ci

* 💚 Fix ci

* 💚 Fix ci

* 📝 Started rewrite of the developer docs

* 📝 Finished developer documentation

* 📝 finished up some things

* ✏️ Fixed typos

* 📝 Updated the contributing.md

* 📝 fix installation links

* 📝 fix approach being spelled wrong

---------

Co-authored-by: BestUsernameEver <isaiah.blanc0220@gmail.com>
Co-authored-by: BestUsernameEver <115376692+BestUsernamEver@users.noreply.github.com>

Author: BattleCh1cken

.github/CONTRIBUTING.md

@@ -29,7 +29,9 @@ All types of contributions are encouraged and valued. See the [Table of Contents
 
 ## I Have a Question
 
-> If you want to ask a question, we assume that you have read the available [Documentation](../docs.pdf).
+<!-- FIXME: replace with real url -->
+
+> If you want to ask a question, we assume that you have read the available [Documentation]().
 
 Before you ask a question, it is best to search for existing [Issues](https://github.com/BattleCh1cken/notebookinator.git/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
 
@@ -41,21 +43,6 @@ If you then still feel the need to ask a question and need clarification, we rec
 
 We will then take care of the issue as soon as possible.
 
-<!--
-You might want to create a separate issue tag for questions and include it in this description. People should then tag their issues accordingly.
-
-Depending on how large the project is, you may want to outsource the questioning, e.g. to Stack Overflow or Gitter. You may add additional contact and information possibilities:
-- IRC
-- Slack
-- Gitter
-- Stack Overflow tag
-- Blog
-- FAQ
-- Roadmap
-- E-Mail List
-- Forum
--->
-
 ## I Want To Contribute
 
 > ### Legal Notice <!-- omit in toc -->
@@ -153,16 +140,34 @@ You can then [commit](#commit-messages) your changes to your fork. Once you are
 
 ### Improving The Documentation
 
-We use [Tidy](https://github.com/Mc-Zen/tidy/tree/main) to generate our documentation. This means that most of our documentation is written directly in the code as comments.
+We use a combination of [mdBook](https://github.com/rust-lang/mdBook) and [Tidy](https://github.com/Mc-Zen/tidy/tree/main) to generate our documentation.
 
-You can improve the documentation in the following places:
+All of the documentation can be found inside of the [`docs/`](../docs) directory.
 
+- The guides located in [`docs/src/`](../docs/src)
 - The comments directly in the code
-- The documentation in [`docs.typ`](../docs.typ)
-- The template for the docs at [`docs-template.typ`](../docs-template.typ)
 - The [README](../README.md)
 - The [contributing guide](./CONTRIBUTING.md)(this file)
 
+You can preview your changes locally with the mdbook cli. The first thing you'll need to do is install all of the dependences.
+
+```bash
+cargo install --git https://github.com/typst/typst --locked typst-cli
+cargo install mdbook
+cargo install mdbook-admonish
+cargo install --git https://github.com/fenjalien/mdbook-typst-doc.git
+```
+
+Once everything has installed, render the documentation with these commands:
+
+```bash
+typst compile docs/src/reference.typ --root ./
+cd docs
+mdbook serve
+```
+
+You can then view your notebook by visiting <localhost:8000>.
+
 Once you've made your changes, submit your changes as a pull request, as described above.
 
 ## Style Guides

.github/workflows/ci.yml

@@ -23,6 +23,5 @@ jobs:
       - name: Run checks
         run: |
           just install
-          just docs
           just gallery
           # TODO: run unit tests here

.github/workflows/docs.yml

@@ -0,0 +1,56 @@
+name: GH Pages Deploy
+
+on:
+  push:
+    branches: [main]
+    paths-ignore:
+      - "docs/**"
+
+  pull_request:
+    branches: [main]
+    paths-ignore:
+      - "docs/**"
+
+jobs:
+  build-deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v2
+
+      - name: Install Typst
+        uses: yusancky/setup-typst@v3
+        id: setup-typst
+
+      - name: Install Mdbook
+        uses: extractions/setup-crate@v1
+        with:
+          owner: rust-lang
+          name: mdBook
+
+      - name: Install Mdbook admonish
+        uses: extractions/setup-crate@v1
+        with:
+          owner: tommilligan
+          name: mdbook-admonish
+
+      - name: Install Mdbook typst doc
+        uses: baptiste0928/cargo-install@v3
+        with:
+          crate: mdbook-typst-doc
+          git: https://github.com/fenjalien/mdbook-typst-doc
+          tag: 0.1.2
+
+      - name: Build
+        run: |
+          typst compile docs/src/reference.typ --root ./
+          cd docs
+          mdbook build
+
+      - name: Deploy to GitHub Pages
+        if: ${{ github.event_name != 'pull_request' }}
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          publish_dir: book

.gitignore

@@ -12,3 +12,6 @@ gallery/*.png
 !gallery/linear-03.png
 !gallery/linear-04.png
 !gallery/linear-05.png
+
+docs/book
+docs/src/reference.pdf