Migrate docs to mdBook.

Author: wmedrano

.github/workflows/site.yml

@@ -37,17 +37,15 @@ jobs:
       - name: Setup Pages
         id: pages
         uses: actions/configure-pages@v5
-      - name: Build with Jekyll
-        run: |
-          bundle install
-          bundle exec jekyll build --baseurl "${{ steps.pages.outputs.base_path }}"
+      - name: Install mdBook
+        run: cargo install mdbook
+      - name: Build with mdBook
+        run: ~/.cargo/bin/mdbook build
         working-directory: ./docs
-        env:
-          JEKYLL_ENV: production
       - name: Upload artifact
         uses: actions/upload-pages-artifact@v3
         with:
-          path: ./docs/_site
+          path: ./docs/book
   deploy-site:
     environment:
       name: github-pages

docs/.gitignore

@@ -1,5 +1 @@
-_site
-.sass-cache
-.jekyll-cache
-.jekyll-metadata
-vendor
+book

docs/404.html

@@ -0,0 +1,5 @@
+[book]
+authors = []
+language = "en"
+src = "src"
+title = "JACK"

docs/Gemfile

@@ -0,0 +1,8 @@
+# Summary
+
+- [Quickstart](./quickstart.md)
+- [Features](./features.md)
+- [Logging](./logging.md)
+- [Contrib](./contrib/index.md)
+  - [Closure Callbacks](./contrib/closure_callbacks.md)
+

docs/Gemfile.lock

@@ -1,19 +1,14 @@
----
-layout: page
-title: Closure Callbacks
-parent: Contrib
-permalink: /closure-callbacks
-nav_order: 1
----
-
 # Closure Callbacks
 
 Closure callbacks allow you to define functionality inline.
 
 ## Process Closure
 
-The typical use case for a process closure involves creating a closure that
-contains captures the required state and then activating it.
+Audio and midi processing can be defined through closures. This involves:
+
+1. Creating a closure that captures the appropriate state (including JACK ports)
+   and
+1. Activating it within a client.
 
 ```rust
 // 1. Create the client.

docs/_config.yml

@@ -1,10 +1,3 @@
----
-layout: page
-title: Contrib
-permalink: /contrib
-nav_order: 3
----
-
 # Contrib
 
 `jack::contrib` contains convenient but optional utilities.