diff --git a/Deepnote/algoesup.py b/Deepnote/algoesup.py
index d092e5a..b7c9c49 100644
--- a/Deepnote/algoesup.py
+++ b/Deepnote/algoesup.py
@@ -20,10 +20,11 @@
 def test(function: Callable, test_table: list) -> None:
     """Test the function with the test_table. Report failed tests.
 
-    Preconditions: each element of test_table is a list or tuple with
-        - a string (the test case name)
-        - one or more values (the inputs to the function)
-        - the expected output value
+    **Preconditions**: each element of test_table is a list or tuple with
+
+    - a string (the test case name)
+    - one or more values (the inputs to the function)
+    - the expected output value
     """
     print(f"Testing {function.__name__}:")
     for test_case in test_table:
@@ -234,7 +235,7 @@ def show_ruff_json(checker: str, output: str, filename: str) -> None:
             msg = error["message"]
             if error["fix"]:
                 msg += f". Suggested fix: {error['fix']['message']}"
-            md.append(f"- {line}: \[[{code}]({url})\] {msg}")
+            md.append(rf"- {line}: \[[{code}]({url})\] {msg}")
         display_markdown("\n".join(md), raw=True)
 
 
@@ -249,7 +250,7 @@ def show_pytype_errors(checker: str, output: str, filename: str) -> None:
             msg = m.group(2)
             code = m.group(3)
             md.append(
-                f"- {line}:{msg}\[[{code}](https://google.github.io/pytype/errors.html#{code})\]"
+                rf"- {line}:{msg}\[[{code}](https://google.github.io/pytype/errors.html#{code})\]"
             )
     if len(md) > 1:
         display_markdown("\n".join(md), raw=True)
diff --git a/README.md b/README.md
index 5cfb31a..530f8d6 100644
--- a/README.md
+++ b/README.md
@@ -33,13 +33,10 @@ python3.10 -m venv venv
 pip install --upgrade pip
 pip install -r requirements.txt
 ```
-To preview locally the documentation that will be in GitHub Pages, follow
-[this guidance](https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll).
-The Jekyll installation instructions include how to install Ruby.
-Bundler is usually automatically installed during the Ruby installation.
+To preview locally the documentation that will be in GitHub Pages, enter `mkdocs serve`.
 
-GitHub recommends to regularly do `bundle update github-pages` to ensure that
-the local site preview looks like on GitHub Pages.
+The documentation must be written in strict Markdown: 
+blank line before a new list; break lines with two spaces; indent with 4 spaces.
 
 After accepting a commit to folder `Deepnote/`, the owners will upload the
 updated files to the Deepnote project linked above.
diff --git a/docs/Gemfile b/docs/Gemfile
deleted file mode 100644
index f1f4742..0000000
--- a/docs/Gemfile
+++ /dev/null
@@ -1,10 +0,0 @@
-# Copied from https://github.com/just-the-docs/just-the-docs-template/blob/main/Gemfile
-
-source "https://rubygems.org"
-
-gem "jekyll", "~> 4.3.3" # installed by `gem jekyll`
-# gem "webrick"        # required when using Ruby >= 3 and Jekyll <= 4.2.2
-
-# gem "just-the-docs", "0.7.0" # pinned to the current release
-gem "just-the-docs"        # always download the latest release
-gem "json", "~> 2.7"
diff --git a/docs/Gemfile.lock b/docs/Gemfile.lock
deleted file mode 100644
index 6ce42e6..0000000
--- a/docs/Gemfile.lock
+++ /dev/null
@@ -1,103 +0,0 @@
-GEM
-  remote: https://rubygems.org/
-  specs:
-    addressable (2.8.6)
-      public_suffix (>= 2.0.2, < 6.0)
-    colorator (1.1.0)
-    concurrent-ruby (1.2.3)
-    em-websocket (0.5.3)
-      eventmachine (>= 0.12.9)
-      http_parser.rb (~> 0)
-    eventmachine (1.2.7)
-    ffi (1.16.3)
-    forwardable-extended (2.6.0)
-    google-protobuf (3.25.2)
-    google-protobuf (3.25.2-aarch64-linux)
-    google-protobuf (3.25.2-arm64-darwin)
-    google-protobuf (3.25.2-x86-linux)
-    google-protobuf (3.25.2-x86_64-darwin)
-    google-protobuf (3.25.2-x86_64-linux)
-    http_parser.rb (0.8.0)
-    i18n (1.14.1)
-      concurrent-ruby (~> 1.0)
-    jekyll (4.3.3)
-      addressable (~> 2.4)
-      colorator (~> 1.0)
-      em-websocket (~> 0.5)
-      i18n (~> 1.0)
-      jekyll-sass-converter (>= 2.0, < 4.0)
-      jekyll-watch (~> 2.0)
-      kramdown (~> 2.3, >= 2.3.1)
-      kramdown-parser-gfm (~> 1.0)
-      liquid (~> 4.0)
-      mercenary (>= 0.3.6, < 0.5)
-      pathutil (~> 0.9)
-      rouge (>= 3.0, < 5.0)
-      safe_yaml (~> 1.0)
-      terminal-table (>= 1.8, < 4.0)
-      webrick (~> 1.7)
-    jekyll-include-cache (0.2.1)
-      jekyll (>= 3.7, < 5.0)
-    jekyll-sass-converter (3.0.0)
-      sass-embedded (~> 1.54)
-    jekyll-seo-tag (2.8.0)
-      jekyll (>= 3.8, < 5.0)
-    jekyll-watch (2.2.1)
-      listen (~> 3.0)
-    json (2.7.1)
-    just-the-docs (0.7.0)
-      jekyll (>= 3.8.5)
-      jekyll-include-cache
-      jekyll-seo-tag (>= 2.0)
-      rake (>= 12.3.1)
-    kramdown (2.4.0)
-      rexml
-    kramdown-parser-gfm (1.1.0)
-      kramdown (~> 2.0)
-    liquid (4.0.4)
-    listen (3.8.0)
-      rb-fsevent (~> 0.10, >= 0.10.3)
-      rb-inotify (~> 0.9, >= 0.9.10)
-    mercenary (0.4.0)
-    pathutil (0.16.2)
-      forwardable-extended (~> 2.6)
-    public_suffix (5.0.4)
-    rake (13.1.0)
-    rb-fsevent (0.11.2)
-    rb-inotify (0.10.1)
-      ffi (~> 1.0)
-    rexml (3.2.6)
-    rouge (4.2.0)
-    safe_yaml (1.0.5)
-    sass-embedded (1.69.5-aarch64-linux-gnu)
-      google-protobuf (~> 3.23)
-    sass-embedded (1.69.5-arm-linux-gnueabihf)
-      google-protobuf (~> 3.23)
-    sass-embedded (1.69.5-arm64-darwin)
-      google-protobuf (~> 3.23)
-    sass-embedded (1.69.5-x86-linux-gnu)
-      google-protobuf (~> 3.23)
-    sass-embedded (1.69.5-x86_64-darwin)
-      google-protobuf (~> 3.23)
-    sass-embedded (1.69.5-x86_64-linux-gnu)
-      google-protobuf (~> 3.23)
-    terminal-table (3.0.2)
-      unicode-display_width (>= 1.1.1, < 3)
-    unicode-display_width (2.5.0)
-    webrick (1.8.1)
-
-PLATFORMS
-  aarch64-linux
-  arm-linux
-  arm64-darwin
-  x86-linux
-  x86_64-darwin
-  x86_64-linux
-
-DEPENDENCIES
-  jekyll (~> 4.3.3)
-  json (~> 2.7)
-  just-the-docs
-
-BUNDLED WITH
-   2.5.4
diff --git a/docs/_config.yml b/docs/_config.yml
deleted file mode 100644
index b3aefe7..0000000
--- a/docs/_config.yml
+++ /dev/null
@@ -1,39 +0,0 @@
-title: Algorithmic Essays
-description:
-theme: just-the-docs
-url: https://dsa-ou.github.io/algoesup/
-
-nav_external_links:
-  - title: GitHub repository
-    url: https://github.com/dsa-ou/algoesup
-    opens_in_new_tab: true
-  - title: Deepnote project
-    url: https://deepnote.com/workspace/lpsae-cc66-cd5cf5e4-ca6e-49d8-b6ee-dbbf202143d3/project/Algorithmic-Essays-acd23b74-5d63-4ef4-a991-3b8a049ddf6b
-    opens_in_new_tab: true
-
-callouts:
-  highlight-yellow:
-    color: yellow
-  important:
-    title: Important
-    color: blue
-  note:
-    title: Note
-    color: green
-  warning:
-    title: Warning
-    color: red
-  highlight-purple:
-    color: purple
-
-callouts_opacity: 0.06
-
-enable_copy_code_button: true
-
-# New configuration option, defined in _layouts/default.html:
-# open external sites in new browser tabs, to not lose guidance context.
-all_external_links_new_tab: true
-
-# Color scheme currently only supports "dark", "light"/nil (default), or a custom scheme that you define
-# algoesup color scheme defined in _sass/color_schemes/algoesup.scss
-color_scheme: algoesup
\ No newline at end of file
diff --git a/docs/_data/nav.yml b/docs/_data/nav.yml
deleted file mode 100644
index 673357b..0000000
--- a/docs/_data/nav.yml
+++ /dev/null
@@ -1,98 +0,0 @@
-- title: "Home"
-  url: "/"
-
-- title: "Getting started"
-  url: getting-started
-
-- title: "Example essays"
-  url: example-essays
-  children:
-
-- title: "Deepnote"
-  url: deepnote
-  children:
-  - title: "How-to guides"
-    url: deepnote-how-to
-    children:
-    - title: "Account operations"
-      url: deepnote-how-to#account-operations
-    - title: "Workspace operations"
-      url: deepnote-how-to#workspace-operations
-    - title: "Project operations"
-      url: deepnote-how-to#project-operations
-    - title: "Notebook operations"
-      url: deepnote-how-to#notebook-operations
-
-  - title: "Background"
-    url: deepnote-background
-    children:
-    - title: "Organisation"
-      url: deepnote-background#organisation
-    - title: "Deepnote vs Classic Notebook"
-      url: deepnote-background#deepnote-vs-classic-notebook
-    - title: "Collaboration"
-      url: deepnote-background#collaboration
-    - title: "Limitations"
-      url: deepnote-background#limitations
-
-  - title: "Reference"
-    url: deepnote-reference
-    children:
-    - title: "Workspace interface"
-      url: deepnote-reference#workspace-interface
-    - title: "Project interface"
-      url: deepnote-reference#project-interface
-    - title: "Notebooks"
-      url: deepnote-reference#notebooks
-    - title: "Access levels"
-      url: deepnote-reference#access-levels
-    - title: "Cells"
-      url: deepnote-reference#cells
-    - title: "Terminal"
-      url: deepnote-reference#terminal
-    - title: "Environment"
-      url: deepnote-reference#environment
-    - title: "Real-time collaboration"
-      url: deepnote-reference#real-time-collaboration
-    - title: "Asynchronous collaboration"
-      url: deepnote-reference#asynchronous-collaboration
-    - title: "Command palette"
-      url: deepnote-reference#command-palette
-    - title: "Members"
-      url: deepnote-reference#members
-    - title: "Markdown cheat sheet"
-      url: deepnote-reference#markdown-cheat-sheet
-    - title: "Keyboard shortcuts"
-      url: deepnote-reference#keyboard-shortcuts
-
-- title: "Writing guide"
-  url: writing
-  children:
-    - title: "Problem"
-      url: writing#problem
-    - title: "Text"
-      url: writing#text
-    - title: "Structure"
-      url: writing#structure
-    - title: "Algorithms"
-      url: writing#algorithms
-    - title: "Code"
-      url: writing#code
-    - title: "Performance analysis"
-      url: writing#performance-analysis
-    - title: "Final check"
-      url: writing#final-check
-    - title: "Further reading"
-      url: writing#further-reading
-
-- title: "Feedback guide"
-  url: feedback
-  children:
-    - title: "Asking for feedback"
-      url: feedback#asking-for-feedback
-    - title: "Giving feedback"
-      url: feedback#giving-feedback
-    - title: "Acting on feedback"
-      url: feedback#acting-on-feedback
-    - title: "Crediting feedback"
-      url: feedback#crediting-feedback
diff --git a/docs/_includes/components/site_nav.html b/docs/_includes/components/site_nav.html
deleted file mode 100644
index cea72e2..0000000
--- a/docs/_includes/components/site_nav.html
+++ /dev/null
@@ -1,57 +0,0 @@
-<nav aria-label="Main" id="site-nav" class="site-nav">
-  <!-- Custom Navigation from nav.yml -->
-  <ul class="nav-list">
-    {% for item in site.data.nav %}
-      <li class="nav-list-item{% if item.children %} has-children{% endif %}">
-        {% if item.children %}
-          <button class="nav-list-expander btn-reset" aria-label="Toggle {{ item.title }}">
-            <svg viewBox="0 0 24 24" aria-hidden="true"><use xlink:href="#svg-arrow-right"></use></svg>
-          </button>
-        {% endif %}
-        <a href="{{ item.url | relative_url }}" class="nav-list-link">{{ item.title }}</a>
-        {% if item.children %}
-          <ul class="nav-list">
-            {% for subitem in item.children %}
-              <li class="nav-list-item{% if subitem.children %} has-children{% endif %}">
-                {% if subitem.children %}
-                  <button class="nav-list-expander btn-reset" aria-label="Toggle {{ subitem.title }}">
-                    <svg viewBox="0 0 24 24" aria-hidden="true"><use xlink:href="#svg-arrow-right"></use></svg>
-                  </button>
-                {% endif %}
-                <a href="{{ subitem.url | relative_url }}" class="nav-list-link">{{ subitem.title }}</a>
-                {% if subitem.children %}
-                  <ul class="nav-list">
-                    {% for subsubitem in subitem.children %}
-                      <li class="nav-list-item">
-                        <a href="{{ subsubitem.url | relative_url }}" class="nav-list-link">{{ subsubitem.title }}</a>
-                      </li>
-                    {% endfor %}
-                  </ul>
-                {% endif %}
-              </li>
-            {% endfor %}
-          </ul>
-        {% endif %}
-      </li>
-    {% endfor %}
-  </ul>
-  <!-- End Custom Navigation -->
-
-  <!-- External Links-->
-  {%- if site.nav_external_links -%}
-  <ul class="nav-list">
-    {%- for node in site.nav_external_links -%}
-      <li class="nav-list-item external">
-        <a href="{{ node.url | absolute_url }}" class="nav-list-link external"
-          {% if node.opens_in_new_tab or node.opens_in_new_tab == nil and site.nav_external_links_new_tab %}
-            target="_blank" rel="noopener noreferrer"
-          {% endif %}
-        >
-          {{ node.title }}
-          {% unless node.hide_icon %}<svg viewBox="0 0 24 24" aria-labelledby="svg-external-link-title"><use xlink:href="#svg-external-link"></use></svg>{% endunless %}
-        </a>
-      </li>
-    {%- endfor -%}
-  </ul>
-  {%- endif -%}
-</nav>
\ No newline at end of file
diff --git a/docs/_layouts/default.html b/docs/_layouts/default.html
deleted file mode 100644
index 10179a9..0000000
--- a/docs/_layouts/default.html
+++ /dev/null
@@ -1,57 +0,0 @@
----
-layout: table_wrappers
----
-
-<!DOCTYPE html>
-
-<html lang="{{ site.lang | default: 'en-US' }}">
-{% include head.html %}
-<body>
-  <a class="skip-to-main" href="#main-content">Skip to main content</a>
-  {% include icons/icons.html %}
-  {% include components/sidebar.html %}
-  <div class="main" id="top">
-    {% include components/header.html %}
-    <div class="main-content-wrap">
-      {% include components/breadcrumbs.html %}
-      <div id="main-content" class="main-content">
-        <main>
-          {% if site.heading_anchors != false %}
-            {% include vendor/anchor_headings.html html=content beforeHeading="true" anchorBody="<svg viewBox=\"0 0 16 16\" aria-hidden=\"true\"><use xlink:href=\"#svg-link\"></use></svg>" anchorClass="anchor-heading" anchorAttrs="aria-labelledby=\"%html_id%\"" %}
-          {% else %}
-            {{ content }}
-          {% endif %}
-
-          {% if page.has_children == true and page.has_toc != false %}
-            {% include components/children_nav.html %}
-          {% endif %}
-        </main>
-        {% include components/footer.html %}
-      </div>
-    </div>
-    {% if site.search_enabled != false %}
-      {% include components/search_footer.html %}
-    {% endif %}
-  </div>
-
-  {% if site.mermaid %}
-    {% include components/mermaid.html %}
-  {% endif %}
-
-  {% if site.all_external_links_new_tab %}
-    <script>
-      document.addEventListener("DOMContentLoaded", function() {
-          const links = document.querySelectorAll("a[href^='http://'], a[href^='https://']");
-          for (let link of links) {
-              if (!link.href.includes(location.hostname)) {
-                  link.setAttribute('target', '_blank');
-                  link.setAttribute('rel', 'noopener noreferrer'); 
-              }
-          }
-      });
-    </script>
-  {% endif %}
-</body>
-
-</body>
-</html>
\ No newline at end of file
diff --git a/docs/_sass/color_schemes/algoesup.scss b/docs/_sass/color_schemes/algoesup.scss
deleted file mode 100644
index 9dc7c76..0000000
--- a/docs/_sass/color_schemes/algoesup.scss
+++ /dev/null
@@ -1,4 +0,0 @@
-
-$body-text-color: $grey-dk-200;
-$link-color: $blue-100;
-@import "../_sass/rouge_schemes/colorful"; // Syntax highlighting scheme
\ No newline at end of file
diff --git a/docs/_sass/rouge_schemes/colorful.scss b/docs/_sass/rouge_schemes/colorful.scss
deleted file mode 100644
index 1080396..0000000
--- a/docs/_sass/rouge_schemes/colorful.scss
+++ /dev/null
@@ -1,163 +0,0 @@
-.highlight .c, .highlight .ch, .highlight .cd, .highlight .cm, .highlight .cpf, .highlight .c1 {
-  color: darken(#888, 15%);
-}
-.highlight .cp {
-  color: #579;
-}
-.highlight .cs {
-  color: #cc0000;
-  font-weight: bold;
-}
-.highlight .k, .highlight .kc, .highlight .kd, .highlight .kn, .highlight .kr, .highlight .kv, .highlight .kp {
-  color: #080;
-  font-weight: bold;
-}
-.highlight .o {
-  color: #aa23ff;
-}
-.highlight .ow {
-  color: #080;
-  font-weight: bold;
-}
-.highlight .nb, .highlight .bp {
-  color: #007020;
-}
-.highlight .nf { 
-  color: #00C;
-}
-.highlight .fm { 
-  color: #080;
-}
-.highlight .nc {
-  color: #B06;
-  font-weight: bold;
-}
-.highlight .nn {
-  color: #0e84b5;
-  font-weight: bold;
-}
-.highlight .ne {
-  color: #F00;
-  font-weight: bold;
-}
-.highlight .nv, .highlight .vm {
-  color: #963;
-}
-.highlight .vi {
-  color: #33B;
-}
-.highlight .vc {
-  color: #369;
-}
-.highlight .vg {
-  color: #d70;
-  font-weight: bold;
-}
-.highlight .no {
-  color: #036;
-  font-weight: bold;
-}
-.highlight .nl {
-  color: #970;
-  font-weight: bold;
-}
-.highlight .ni {
-  color: #800;
-  font-weight: bold;
-}
-.highlight .na {
-  color: #00C;
-}
-.highlight .nt {
-  color: #070;
-}
-.highlight .nd {
-  color: #555;
-  font-weight: bold;
-}
-.highlight .s, .highlight .sb, .highlight .dl, .highlight .s2, .highlight .sh, .highlight .s1 {
-  color: #ba2220;
-}
-.highlight .sa {
-  color: #080;
-  font-weight: bold;
-}
-.highlight .sc {
-  color: #04D;
-}
-.highlight .sd {
-  color: #D42;
-}
-.highlight .si {
-  background-color: #eee;
-}
-.highlight .se {
-  color: #666;
-  font-weight: bold;
-}
-.highlight .sr {
-  color: #000;
-  background-color: #fff0ff;
-}
-.highlight .ss {
-  color: #A60;
-}
-.highlight .sx {
-  color: #D20;
-}
-.highlight .m, .highlight .mb, .highlight .mx {
-  color: #60E;
-  font-weight: bold;
-}
-.highlight .mi, .highlight .il {
-  color: #00A000;
-}
-.highlight .mf {
-  color: #60E;
-  font-weight: bold;
-}
-.highlight .mh {
-  color: #058;
-  font-weight: bold;
-}
-.highlight .mo {
-  color: #40E;
-  font-weight: bold;
-}
-.highlight .gh {
-  color: #000080;
-  font-weight: bold;
-}
-.highlight .gu {
-  color: #800080;
-  font-weight: bold;
-}
-.highlight .gd {
-  color: #A00000;
-}
-.highlight .gi {
-  color: #00A000;
-}
-.highlight .gr {
-  color: #FF0000;
-}
-.highlight .ge {
-  font-style: italic;
-}
-.highlight .gs {
-  font-weight: bold;
-}
-.highlight .gp {
-  color: #c65d09;
-  font-weight: bold;
-}
-.highlight .go {
-  color: #888;
-}
-.highlight .gt {
-  color: #04D;
-}
-.highlight .err {
-  color: #F00;
-  background-color: #FAA;
-}
diff --git a/docs/deepnote-background.md b/docs/deepnote-background.md
index 128a763..c10ca68 100644
--- a/docs/deepnote-background.md
+++ b/docs/deepnote-background.md
@@ -1,19 +1,4 @@
----
-layout: default
-title: Background
-parent: Deepnote
----
 # Background
-{: .no_toc}
-
-<details open markdown="block">
-  <summary>
-    Table of contents
-  </summary>
-  {: .h4 }
-- TOC
-{:toc}
-</details>
 
 ## Organisation
 
@@ -88,7 +73,7 @@ save space; threads can be reopened if needed. Any open threads are displayed in
 comments panel on the right-hand side of a project.
 
 Comments are one of the ways to give and receive feedback on your essays.
-See the [feedback guide]({{site.baseurl}}/feedback) for more details.
+See the [feedback guide](feedback.md) for more details.
 
 ## Limitations
 
@@ -111,7 +96,7 @@ text, which appears to slow down performance, potentially due to the autocomplet
 functionality.
 
 As a final point, the way Deepnote stores notebooks within the environment must be mentioned.
-You can of course [upload a notebook]({{site.baseurl}}/deepnote-how-to#upload-a-notebook-or-file) to the system and access it like
+You can of course [upload a notebook](deepnote-how-to.md#upload-a-notebook-or-file) to the system and access it like
 any other file, but if you want to run the notebook, it must be moved to the **NOTEBOOKS**
 section. This then becomes a problem if you wish to access the notebook file again, say using
 the terminal. When a notebook is moved to this section it effectively takes the notebook out of
diff --git a/docs/deepnote-how-to.md b/docs/deepnote-how-to.md
index cfde956..b512202 100644
--- a/docs/deepnote-how-to.md
+++ b/docs/deepnote-how-to.md
@@ -1,24 +1,9 @@
----
-layout: default
-title: Deepnote How to guides
-parent: Deepnote
----
 # Deepnote how-to guides
-{: .no_toc}
-
-<details open markdown="block">
-  <summary>
-    Table of contents
-  </summary>
-  {: .h4 }
-- TOC
-{:toc}
-</details>
 
 ## Account operations
 
 ### Sign up for Deepnote
-This is explained in our [Getting Started]({{site.baseurl}}/getting-started#create-a-deepnote-account) guide.
+This is explained in our [Getting Started](getting-started.md#create-a-deepnote-account) guide.
 
 ### Log in
 If you have logged out, to log back in you need to verify your email again:
@@ -29,6 +14,7 @@ If you have logged out, to log back in you need to verify your email again:
 
 ## Workspace operations
 Before any of the following operations, you must change from project view to workspace view:
+
 1. Click on your workspace name in the top left corner of the screen.
 2. From the drop-down menu, select **Back to workspace**.
 
@@ -67,10 +53,11 @@ If your notebook contains other types of cells besides Markdown and code,
 the downloaded `.ipynb` file won't be rendered correctly on other Jupyter platforms.
 
 ### Duplicate our project
-This is explained in our [Getting Started]({{site.baseurl}}/getting-started#duplicate-our-project) guide.
+This is explained in our [Getting Started](getting-started.md#duplicate-our-project) guide.
 
 ### Share your project
 The following assumes you have [enabled sharing](#enable-sharing) for your workspace.
+
 1. Click the **Share** button in the top right corner of the screen.
 2. To the right of **Anyone with a link to this project**, click on the drop-down menu and select **Comment**.
 3. Click the highlighted blue **link to this project**, to copy the link.
@@ -85,6 +72,7 @@ The simplest way is to drag the notebook or file from your desktop to
 the **Notebooks** or **Files** section in the side panel.
 
 Alternatively, to upload a file:
+
 1. Click on the + icon next to the **Files** heading in the left panel.
 2. Select **Upload file** from the drop-down menu.
 3. In the file browser, navigate to the file you want to upload, then click **Open**.
@@ -92,6 +80,7 @@ Alternatively, to upload a file:
 ## Notebook operations
 
 To perform an action on a cell, do *one* of the following:
+
 - Click on the cell to select it: the outline becomes blue. Press the action's keyboard shortcut.
 - Hover over the cell. A pop-up menu appears in the top right corner of the cell.
   Click on the action's icon or click the three dots to get a menu of actions.
@@ -100,55 +89,61 @@ To perform an action on a cell, do *one* of the following:
 Running a cell executes the code or formats the Markdown text.
 
 To run one cell, do *one* of the following:
+
 - Press Ctrl + Enter (Mac: Cmd + Enter) if the cell is [selected](#notebook-operations).
 - Click the triangle icon in the top right corner of the cell.
 
 To run all cells, click **Run notebook** in the top right corner of the notebook.
 
-{: .note}
-The first time you run code, it will take some time, because
-Deepnote must first start a server with the necessary software.
+!!! note
+    The first time you run code, it will take some time, because
+    Deepnote must first start a server with the necessary software.
 
 ### Add a cell
 To insert a cell between two existing cells:
+
 1. Hover the mouse between the two cells.
 2. Click on the line that appears between both cells and do *one* of the following:
-   - To insert a code cell, press `c` followed by Enter.
-   - To insert a Markdown cell, press `m` followed by Enter.
+    - To insert a code cell, press `c` followed by Enter.
+    - To insert a Markdown cell, press `m` followed by Enter.
 
 To append a cell, scroll down to the end of the notebook and do *one* of the following:
+
 - To add a code cell, click on the **Code** button.
 - To add a Markdown cell, click on the **Text** button and select **Markdown**.
 
 ### Delete a cell
 Do *one* of the following:
+
 - Press Ctrl + Shift + Backspace (Mac: Cmd + Shift + Backspace) if the cell is [selected](#notebook-operations).
 - Click the bin icon in the top right corner of the cell.
 
 ### Comment on a cell
 Do *one* of the following:
+
 - Press Ctrl + Alt + C (Mac: Cmd + Alt + C) if the cell is [selected](#notebook-operations).
 - Click the speech bubble icon in the top right corner of the cell.
 
 After typing your comment, press the upwards blue arrow to finish.
 
-{: .warning}
-You must be logged into your account to comment on notebooks shared with you.
-If you're not logged in, your comments are marked as 'anonymous user' and
-the essay's author won't see them.
+!!! warning
+    You must be logged into your account to comment on notebooks shared with you.
+    If you're not logged in, your comments are marked as 'anonymous user' and
+    the essay's author won't see them.
 
 ### Format a code cell
 This 'pretty prints' the code. Do *one* of the following:
+
 - Press Alt + Shift + F if the cell is [selected](#notebook-operations).
 - Click the three dots in the top right corner of the cell and
   select **Format code** from the drop-down menu.
   (To avoid scrolling all the way down, type `f` in the search box of the menu.)
 
-{: .note}
-Formatting takes 1-2 seconds and adds an empty line (which you may delete)
-to the end of the cell.
+!!! note
+    Formatting takes 1-2 seconds and adds an empty line (which you may delete)
+    to the end of the cell.
 
-{: .warning}
-If you get a message 'parsing failed',
-then the code cell is not valid Python and can't be automatically formatted.
-This may happen if the cell has IPython commands starting with `%`.
\ No newline at end of file
+!!! warning
+    If you get a message 'parsing failed',
+    then the code cell is not valid Python and can't be automatically formatted.
+    This may happen if the cell has IPython commands starting with `%`.
\ No newline at end of file
diff --git a/docs/deepnote-reference.md b/docs/deepnote-reference.md
index 62447d9..fac3a86 100644
--- a/docs/deepnote-reference.md
+++ b/docs/deepnote-reference.md
@@ -1,19 +1,4 @@
----
-layout: default
-title: Reference
-parent: Deepnote
----
 # Reference
-{: .no_toc}
-
-<details open markdown="block">
-  <summary>
-    Table of contents
-  </summary>
-  {: .h4 }
-- TOC
-{:toc}
-</details>
 
 ## Workspace interface
 
@@ -21,6 +6,7 @@ The [workspaces](https://deepnote.com/docs/workspaces) interface provides an ove
 projects in your Workspace. On the left-hand side panel you will find a navigation menu
 allowing you to quickly navigate to different sections of your workspace. Starting from the
 top, the sections are:
+
 - **Integrations** - This section allows you to set up and manage connections to data sources.
   This is mostly used for data science work.
   <!-- various integrations . An integration in the context of Deepnote refers to a
@@ -39,13 +25,14 @@ top, the sections are:
 
 A [project](https://deepnote.com/docs/projects)'s interface has similarities to the interface
 for your workspace. Starting from the top, the sections on the left-hand side panel are:
+
  - **NOTEBOOKS** - This section is where your notebooks live. If you want to
    actively work on your notebooks they must be added to this location.
  - **INTEGRATIONS** - This section allows
    you to use an integration defined for the workspace. Integrations are mainly used in data science.
  - **FILES** - Each project in Deepnote has an integrated file system which you
    can view and access in this section. You can create and
-   [upload files]({{site.baseurl}}/deepnote-how-to#upload-a-notebook-or-file)
+   [upload files](deepnote-how-to.md#upload-a-notebook-or-file)
    and folders here.
  - **TERMINALS** - Deepnote allows you to launch terminals from this section by
    clicking on the "+" icon. As you would expect you can access the local file
@@ -66,7 +53,7 @@ for your workspace. Starting from the top, the sections on the left-hand side pa
 Notebooks in Deepnote have the same core functionality as Jupyter Notebooks:
 they combine executable code and text in the same document.
 
-See [Deepnote vs Classic Notebook]({{site.baseurl}}/deepnote-background#deepnote-vs-classic-notebook)
+See [Deepnote vs Classic Notebook](deepnote-background.md#deepnote-vs-classic-notebook)
 for some differences between the two.
 
 ## Access levels
@@ -75,6 +62,7 @@ Access levels are the range of permissions or capabilities assigned to a user in
 differ between the contexts of workspaces and projects.
 
 The access levels for projects are:
+
 - **App User**: Can use published app, but cannot view the project source code.
 - **View**: Can inspect the project, but cannot view or post comments nor execute or edit files.
 - **Comment**: Can post and view comments in addition to inspecting the project.
@@ -101,7 +89,7 @@ manage workspace members.
 Cells (called 'blocks' in Deepnote) are the divisions within each notebook.
 They are a distinct area where code or text can
 be added depending on the type of the cell.
-See our [how-to guide]({{site.baseurl}}/deepnote-how-to#notebook-operations) for working with cells.
+See our [how-to guide](deepnote-how-to.md#notebook-operations) for working with cells.
 
 ## Terminal
 
diff --git a/docs/deepnote.md b/docs/deepnote.md
index 0967a5a..3f3f9f6 100644
--- a/docs/deepnote.md
+++ b/docs/deepnote.md
@@ -1,10 +1,3 @@
----
-layout: default
-title: Deepnote
-has_children: true
-nav_order: 4
-has_toc: false
----
 # Deepnote
 
 Deepnote is the cloud based Jupyter notebook platform we recommend for writing your essays.
@@ -14,8 +7,8 @@ The platform was chosen
 due to its simple interface, customisable environment, and features for collaborative
 working.
 
-{: .warning}
-This Deepnote guide is limited in scope to the writing, sharing and critiquing of algorithmic essays. There are many features of the platform not covered here. See the [official documentation](https://deepnote.com/docs) for more extensive coverage.
+!!! warning
+    This Deepnote guide is limited in scope to the writing, sharing and critiquing of algorithmic essays. There are many features of the platform not covered here. See the [official documentation](https://deepnote.com/docs) for more extensive coverage.
 
 You may find it helpful to watch the following introduction video.
 
@@ -25,12 +18,13 @@ encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></ifr
 <br>
 
 This guide has three parts:
-- The [How-to]({{site.baseurl}}/deepnote-how-to) guide provides step by step instructions on how to complete specific tasks
+
+- The [How-to](deepnote-how-to.md) guide provides step by step instructions on how to complete specific tasks
 in Deepnote.
-- The [Background]({{site.baseurl}}/deepnote-background) section discusses and explains aspects of Deepnote in a longer form and
+- The [Background](deepnote-background.md) section discusses and explains aspects of Deepnote in a longer form and
 sometimes broader context.
-- The [Reference]({{site.baseurl}}/deepnote-reference) section is for quickly looking up information about key aspects of
+- The [Reference](deepnote-reference.md) section is for quickly looking up information about key aspects of
 Deepnote.
 
-{: .note}
-Use the side panel to navigate the Deepnote guidance.
+!!! note
+    Use the side panel to navigate the Deepnote guidance.
diff --git a/Deepnote/example-1-to-n.ipynb b/docs/essays/example-1-to-n.ipynb
similarity index 100%
rename from Deepnote/example-1-to-n.ipynb
rename to docs/essays/example-1-to-n.ipynb
diff --git a/Deepnote/example-jewels.ipynb b/docs/essays/example-jewels.ipynb
similarity index 100%
rename from Deepnote/example-jewels.ipynb
rename to docs/essays/example-jewels.ipynb
diff --git a/Deepnote/example-two-sum-2.ipynb b/docs/essays/example-two-sum-2.ipynb
similarity index 100%
rename from Deepnote/example-two-sum-2.ipynb
rename to docs/essays/example-two-sum-2.ipynb
diff --git a/Deepnote/example-two-sum-3.ipynb b/docs/essays/example-two-sum-3.ipynb
similarity index 100%
rename from Deepnote/example-two-sum-3.ipynb
rename to docs/essays/example-two-sum-3.ipynb
diff --git a/Deepnote/template-data-structures.ipynb b/docs/essays/template-data-structures.ipynb
similarity index 100%
rename from Deepnote/template-data-structures.ipynb
rename to docs/essays/template-data-structures.ipynb
diff --git a/Deepnote/template-intro-programming.ipynb b/docs/essays/template-intro-programming.ipynb
similarity index 100%
rename from Deepnote/template-intro-programming.ipynb
rename to docs/essays/template-intro-programming.ipynb
diff --git a/docs/example-essays.md b/docs/example-essays.md
index a55d65e..806dd35 100644
--- a/docs/example-essays.md
+++ b/docs/example-essays.md
@@ -1,8 +1,3 @@
----
-layout: default
-title: Example essays
-nav_order: 3
----
 # Example essays
 
 These examples illustrate different ways of structuring essays and different writing styles.
@@ -11,16 +6,9 @@ These examples illustrate different ways of structuring essays and different wri
 Some essays have a template that highlights the essay's structure and
 the purpose of each section.
 Clicking on a button below will open a *read-only* version of the essay or template.
-They are rendered on-demand in your web browser, which may take a few seconds.
 
-If you get a "404 File not found" error when reading on nbviewer,
-it means we have updated the file and it's not yet ready for display.
-Try again in a few hours or read it on GitHub.
-You can also read all examples and templates on DeepNote
-(click the link in the navigation panel on the left).
-
-Once you have created a Deepnote account and copied our essay project,
-as explained in [Getting started]({{site.baseurl}}/getting-started),
+Once you have created a Deepnote account and copied our project,
+as explained in [Getting started](getting-started.md),
 you will have access to *editable* versions of the examples and templates, so that
 you can use them as starting points for your essays.
 
@@ -31,11 +19,8 @@ The essay shows two ways of calculating 1 + 2 + ... + *n* and compares their run
 The essay follows a simple structure, in which each approach is outlined, implemented
 and tested before moving on to the next one.
 
-[Essay (nbviewer)](https://nbviewer.org/github/dsa-ou/algoesup/blob/main/Deepnote/example-1-to-n.ipynb){: .btn .btn-blue .mr-2 }
-[Essay (GitHub)](https://github.com/dsa-ou/algoesup/blob/main/Deepnote/example-1-to-n.ipynb){: .btn .btn-blue }
-
-[Template (nbviewer)](https://nbviewer.org/github/dsa-ou/algoesup/blob/main/Deepnote/template-intro-programming.ipynb){: .btn .btn-blue .mr-2}
-[Template (GitHub)](https://github.com/dsa-ou/algoesup/blob/main/Deepnote/template-intro-programming.ipynb){: .btn .btn-blue}
+[Essay](essays/example-1-to-n.ipynb){.md-button}
+[Template](essays/template-intro-programming.ipynb){.md-button .md-button--primary}
 
 ## Jewels and Stones
 
@@ -47,11 +32,8 @@ The complexity of the three algorithms is analysed and compared to their run-tim
 This essay follows a slightly different structure, in which each approach is outlined and
 its complexity analysed, before deciding which approaches are worth implementing.
 
-[Essay (nbviewer)](https://nbviewer.org/github/dsa-ou/algoesup/blob/main/Deepnote/example-jewels.ipynb){: .btn .btn-blue .mr-2 }
-[Essay (GitHub)](https://github.com/dsa-ou/algoesup/blob/main/Deepnote/example-jewels.ipynb){: .btn .btn-blue }
-
-[Template (nbviewer)](https://nbviewer.org/github/dsa-ou/algoesup/blob/main/Deepnote/template-data-structures.ipynb){: .btn .btn-blue .mr-2}
-[Template (GitHub)](https://github.com/dsa-ou/algoesup/blob/main/Deepnote/template-data-structures.ipynb){: .btn .btn-blue}
+[Essay](essays/example-jewels.ipynb){.md-button}
+[Template](essays/template-data-structures.ipynb){.md-button .md-button--primary}
 
 ## Two Sum (two approaches)
 
@@ -59,12 +41,10 @@ This classic problem asks to find two numbers in a list that add up exactly to a
 This essay solves the problem in two ways, with brute-force search (nested loops)
 and a map (Python dictionary).
 
-[Essay (nbviewer)](https://nbviewer.org/github/dsa-ou/algoesup/blob/main/Deepnote/example-two-sum-2.ipynb){: .btn .btn-blue .mr-2}
-[Essay (GitHub)](https://github.com/dsa-ou/algoesup/blob/main/Deepnote/example-two-sum-2.ipynb){: .btn .btn-blue }
+[Essay](essays/example-two-sum-2.ipynb){.md-button}
 
 ## Two Sum (three approaches)
 This is an extended version of the previous essay.
 It adds a third approach, that sorts the list of numbers.
 
-[Essay (nbviewer)](https://nbviewer.org/github/dsa-ou/algoesup/blob/main/Deepnote/example-two-sum-3.ipynb){: .btn .btn-blue .mr-2}
-[Essay (GitHub)](https://github.com/dsa-ou/algoesup/blob/main/Deepnote/example-two-sum-3.ipynb){: .btn .btn-blue }
+[Essay ](essays/example-two-sum-3.ipynb){.md-button}
diff --git a/docs/feedback.md b/docs/feedback.md
index 61a7e33..2d37385 100644
--- a/docs/feedback.md
+++ b/docs/feedback.md
@@ -1,26 +1,9 @@
----
-layout: default
-title: Feedback guide
-nav_order: 6
----
-
-
 # Feedback guide
-{: .no_toc}
 
 Giving feedback on each other's essays is an important part of developing
 professional skills with algorithmic essays.
 {: .fs-6 .fw-300}
 
-<details open markdown="block">
-  <summary>
-    Table of contents
-  </summary>
-  {: .h4}
-- TOC
-{:toc}
-</details>
-
 Receiving feedback helps improve your essay,
 while giving feedback helps develop your communication skills.
 Moreover, reading other people's essays is a great way to learn more about Python,
@@ -62,7 +45,7 @@ but before investing the time in implementing and testing them. Your request cou
 > I'm looking for feedback on the above algorithms.
 > Are they clear? Have I missed other approaches to solving this problem?
 
-Once your notebook is ready for feedback, you need to [share it]({{site.baseurl}}/deepnote-how-to#share-your-project)
+Once your notebook is ready for feedback, you need to [share it](deepnote-how-to.md#share-your-project)
 so that others can comment on it.
 You may invite comments from anyone or only from one or two 'essay buddies':
 they comment on your essay and you comment on theirs.
@@ -74,11 +57,12 @@ because the author is waiting for it to progress the essay to the next draft.
 Feedback should be specific and constructive. Generic comments like "This is confusing" or
 "I don't understand this" aren't helpful for the author.
 State what you're finding hard to grasp, like:
+
 - "What is 'it' referring to in the second sentence?"
 - "The term '...' in the last sentence hasn't been defined. Does it mean the same as '...'?"
 - "What is variable '...' used for in the algorithm? Should it initially be the empty list?"
 
-Before [adding a comment]({{site.baseurl}}/deepnote-how-to#comment-on-a-cell) to a notebook cell, read the existing comments,
+Before [adding a comment](deepnote-how-to.md#comment-on-a-cell) to a notebook cell, read the existing comments,
 to avoid repeating the same points others have made.
 
 Comments that aren't about a specific text paragraph or code cell,
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 0b6df8b..de5a11f 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -1,19 +1,9 @@
----
-layout: default
-title: Getting started
-nav_order: 2
----
-
 # Getting started
-{: .no_toc}
 
 Follow these steps to start writing essays within a few minutes,
 without any software installation or configuration.
 {: .fs-6 .fw-300}
 
-1. TOC
-{:toc}
-
 ## Create a Deepnote account
 
 1. Open the Deepnote [sign-up page](https://deepnote.com/sign-up).
@@ -22,19 +12,18 @@ without any software installation or configuration.
 3. Check the CAPTCHA box and click **Continue with email**.
 4. Check your email for a sign-in link from Deepnote and click it.
 
-{: .important}
-There are no passwords for Deepnote when signing up by email.
-If you explicitly log out of your Deepnote account,
-see our guide for [how to log in]({{site.baseurl}}/deepnote-how-to#log-in).
+    !!! note
+        There are no passwords for Deepnote when signing up by email.
+        If you explicitly log out of your Deepnote account,
+        see our guide for [how to log in](deepnote-how-to.md#log-in).
 
-{:style="counter-reset:none"}
-1. In Deepnote, answer the introductory questions, which may depend on
+5. In Deepnote, answer the introductory questions, which may depend on
    the type of email you used to sign up.
-   - If you're asked **what you are working on**, type **Writing essays** and click **Continue**.
-   - If you're asked to name your **workspace**, which is where you will store your projects,
-     give it a unique and descriptive name, e.g. "_Your Name_'s projects".
-   - If you're asked to **invite your teammates**, click **Continue**.
-   - If you're asked for your **data sources**, click **Take me to Deepnote**.
+    - If you're asked **what you are working on**, type **Writing essays** and click **Continue**.
+    - If you're asked to name your **workspace**, which is where you will store your projects,
+      give it a unique and descriptive name, e.g. "_Your Name_'s projects".
+    - If you're asked to **invite your teammates**, click **Continue**.
+    - If you're asked for your **data sources**, click **Take me to Deepnote**.
 
 You should now be looking at an empty notebook that is part of
 the **Welcome to Deepnote** project within your workspace.
@@ -53,17 +42,16 @@ The project has all necessary software pre-installed.
 3. Choose the name of your workspace from the drop-down menu.
 4. Click **Duplicate project** to finish the process.
 
-{: .important}
-Do _not_ check the box to make your project private:
-that would prevent sharing your essays later with others.
+    !!! note
+        Do _not_ check the box to make your project private:
+        that would prevent sharing your essays later with others.
 
-After a few moments, you will see the project in your workspace,
-with the name **Algorithmic Essays - Duplicate** at the top of the screen.
+    After a few moments, you will see the project in your workspace,
+    with the name **Algorithmic Essays - Duplicate** at the top of the screen.
 
-{:style="counter-reset:none"}
-1. Click on the three dots in the top right corner.
-2. Select **Rename project** from the drop-down menu.
-3. In the text box that appears, type a name for your project, e.g. "_Your Name_'s essays".
+5. Click on the three dots in the top right corner.
+6. Select **Rename project** from the drop-down menu.
+7. In the text box that appears, type a name for your project, e.g. "_Your Name_'s essays".
 
 You should now see some notebooks in the left panel.
 
@@ -81,9 +69,9 @@ To write an essay, copy one of the templates and edit that copy.
 This creates a new notebook, with the name of the template followed by '-2', and opens it.
 You can now start editing your copy of the template.
 (Once you decided your essay's topic, you can
-[rename the notebook]({{site.baseurl}}/deepnote-how-to#rename-duplicate-download-or-delete-a-notebook-or-file).)
+[rename the notebook](deepnote-how-to.md#rename-duplicate-download-or-delete-a-notebook-or-file).)
 
 If you're familiar with the classic Jupyter interface, we recommend you first
-read about the [differences]({{site.baseurl}}/deepnote-background#deepnote-vs-classic-notebook) with Deepnote.
+read about the [differences](deepnote-background.md#deepnote-vs-classic-notebook) with Deepnote.
 
-For a video introduction to notebooks and Deepnote, see our [Deepnote guide]({{site.baseurl}}/deepnote).
+For a video introduction to notebooks and Deepnote, see our [Deepnote guide](deepnote.md).
diff --git a/docs/index.md b/docs/index.md
index 0fd6a72..e0d2843 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -1,8 +1,3 @@
----
-title: Home
-layout: default
-nav_order: 1
----
 
 # Algorithmic Essays
 
@@ -12,7 +7,8 @@ These documents provide guidance to help you write, critique, and share algorith
 We define **algorithmic essays** as short reports, with code, that
 explain and compare alternative approaches to solving a computational problem.
 
-If you're a student, writing algorithmic essays benefits you in various ways.
+If you're a student, writing algorithmic essays benefits you in various ways:
+
 - You reinforce your learning by explaining concepts to others and
   by exploring alternative solutions to the same problem.
 - You develop professional skills like problem-solving, reviewing code,
@@ -25,20 +21,21 @@ If you're an educator, you can copy our resources from the
 [GitHub repository](https://github.com/dsa-ou/algoesup) and
 adapt them to your course, due to our permissive licence (see below).
 
-{: .note}
-We provide some [example essays]({{site.baseurl}}/example-essays) to illustrate what they are.
+!!! example
+    We provide some [example essays](example-essays.md) to illustrate what they are.
 
 While many approaches to writing algorithmic essays are possible, we recommend
 using **Jupyter notebooks**, the most widely used medium for mixing text and executable code,
 and **Deepnote**, a cloud-based environment for Jupyter notebooks.
 We have no commercial affiliation with Deepnote. We chose it for these reasons:
+
 - free academic account
 - no software installation necessary
 - you can share your essays publicly (or just with a few people) to easily
   - receive and give feedback
   - work collaboratively on the same essay.
 
-[Get started]({{site.baseurl}}/getting-started){: .btn .btn-green}
+[Get started](getting-started.md){ .md-button .md-button--primary}
 
 ## Acknowledgements
 
diff --git a/docs/library.md b/docs/library.md
new file mode 100644
index 0000000..fd5b6be
--- /dev/null
+++ b/docs/library.md
@@ -0,0 +1,40 @@
+# Library
+
+The `algoesup` library provides support for testing, timing and linting code.
+
+## Testing
+
+This function can be used with any Python program.
+
+The library requires `matplotlib` and `ipython`. 
+
+::: algoesup
+    options:
+      heading_level: 3
+      show_root_toc_entry: false
+      members:
+      - test
+
+## Timing
+
+::: algoesup
+    options:
+      heading_level: 3
+      show_root_toc_entry: false
+      members:
+      - time_functions
+      - time_cases
+      - time_functions_int
+
+## Linting
+
+These are to lint within a Jupyter notebook, cell by cell.
+
+::: algoesup
+    options:
+      heading_level: 3
+      show_root_toc_entry: false
+      members:
+      - allowed
+      - pytype
+      - ruff
\ No newline at end of file
diff --git a/docs/stylesheets/extra.css b/docs/stylesheets/extra.css
new file mode 100644
index 0000000..36e909e
--- /dev/null
+++ b/docs/stylesheets/extra.css
@@ -0,0 +1,198 @@
+.md-typeset .admonition,
+.md-typeset details {
+  border-width: 0;
+  border-left-width: 4px;
+}
+
+/* 
+The customisation of code blocks is explained in
+https://squidfunk.github.io/mkdocs-material/reference/code-blocks/#custom-syntax-theme.
+*/
+
+/* The default colour of each syntax element is in 
+https://github.com/squidfunk/mkdocs-material/blob/master/src/templates/assets/stylesheets/main/extensions/pymdownx/_highlight.scss
+*/
+
+.highlight {
+  .k, .kn { /* keyword, name */
+    font-weight: bold;
+  }
+  .c, .c1 { /* comment, single-line */
+    font-style: italic;
+  }
+  .sd { /* docstring */
+    color: var(--md-code-hl-string-color);
+  }
+}
+
+/* 
+The following is from the previous version (Just the Docs).
+The darker colours don't work so well with the dark theme.
+*/
+/*
+.highlight {
+  .c, .ch, .cd, .cm, .cpf, .c1 {
+    color: darken(#888, 15%);
+  }
+ .cp {
+    color: #579;
+  }
+ .cs {
+    color: #cc0000;
+    font-weight: bold;
+  }
+ .k, .kc, .kd, .kn, .kr, .kv, .kp {
+    color: #080;
+    font-weight: bold;
+  }
+ .o {
+    color: #aa23ff;
+  }
+ .ow {
+    color: #080;
+    font-weight: bold;
+  }
+ .nb, .bp {
+    color: #007020;
+  }
+ .nf { 
+    color: #00C;
+  }
+ .fm { 
+    color: #080;
+  }
+ .nc {
+    color: #B06;
+    font-weight: bold;
+  }
+ .nn {
+    color: #0e84b5;
+    font-weight: bold;
+  }
+ .ne {
+    color: #F00;
+    font-weight: bold;
+  }
+ .nv, .vm {
+    color: #963;
+  }
+ .vi {
+    color: #33B;
+  }
+ .vc {
+    color: #369;
+  }
+ .vg {
+    color: #d70;
+    font-weight: bold;
+  }
+ .no {
+    color: #036;
+    font-weight: bold;
+  }
+ .nl {
+    color: #970;
+    font-weight: bold;
+  }
+ .ni {
+    color: #800;
+    font-weight: bold;
+  }
+ .na {
+    color: #00C;
+  }
+ .nt {
+    color: #070;
+  }
+ .nd {
+    color: #555;
+    font-weight: bold;
+  }
+ .s, .sb, .dl, .s2, .sh, .s1 {
+    color: #ba2220;
+  }
+ .sa {
+    color: #080;
+    font-weight: bold;
+  }
+ .sc {
+    color: #04D;
+  }
+ .sd {
+    color: #D42;
+  }
+ .si {
+    background-color: #eee;
+  }
+ .se {
+    color: #666;
+    font-weight: bold;
+  }
+ .sr {
+    color: #000;
+    background-color: #fff0ff;
+  }
+ .ss {
+    color: #A60;
+  }
+ .sx {
+    color: #D20;
+  }
+ .m, .mb, .mx {
+    color: #60E;
+    font-weight: bold;
+  }
+ .mi, .il {
+    color: #00A000;
+  }
+ .mf {
+    color: #60E;
+    font-weight: bold;
+  }
+ .mh {
+    color: #058;
+    font-weight: bold;
+  }
+ .mo {
+    color: #40E;
+    font-weight: bold;
+  }
+ .gh {
+    color: #000080;
+    font-weight: bold;
+  }
+ .gu {
+    color: #800080;
+    font-weight: bold;
+  }
+ .gd {
+    color: #A00000;
+  }
+ .gi {
+    color: #00A000;
+  }
+ .gr {
+    color: #FF0000;
+  }
+ .ge {
+    font-style: italic;
+  }
+ .gs {
+    font-weight: bold;
+  }
+ .gp {
+    color: #c65d09;
+    font-weight: bold;
+  }
+ .go {
+    color: #888;
+  }
+ .gt {
+    color: #04D;
+  }
+ .err {
+    color: #F00;
+    background-color: #FAA;
+  }
+}
+*/
\ No newline at end of file
diff --git a/docs/writing.md b/docs/writing.md
index dc751d2..e1fe9d1 100644
--- a/docs/writing.md
+++ b/docs/writing.md
@@ -1,27 +1,11 @@
----
-layout: default
-title: Writing guide
-nav_order: 5
----
-
 # Writing guide
-{: .no_toc}
 
-This document provides guidance on how to produce your essay.
+This document provides guidance on how to produce your essay. 
 {: .fs-6 .fw-300}
 
-{: .warning}
-Although we wish to accommodate novice programmers in the future,
-the guide currently has data structures and algorithms students in mind.
-
-<details open markdown="block">
-  <summary>
-    Table of contents
-  </summary>
-  {: .h4 }
-1. TOC
-{:toc}
-</details>
+!!! note
+    Although we wish to accommodate novice programmers in the future,
+    the guide currently has data structures and algorithms students in mind.
 
 An essay can have more than one author, although more than two is harder to manage.
 Deepnote makes it easy to work collaboratively on a single notebook,
@@ -31,9 +15,9 @@ You may wish to first pitch your essay idea to your peers, to recruit co-authors
 In the rest of this guide, 'you' and 'your' are both singular and plural pronouns,
 to refer simultaneously to a single author or multiple authors.
 
-{: .note}
-You may wish to keep this guide open while going through one of the
-example essays in your copy of our Deepnote project.
+!!! note
+    You may wish to keep this guide open while going through one of the
+    example essays in your copy of our Deepnote project.
 
 ## Problem
 It's worth spending time on choosing an appropriate problem before putting effort into an essay about it.
@@ -66,6 +50,7 @@ If you're undecided, make a shortlist of 2–3 problems and ask your peers for t
 An essay presents two or more algorithmic solutions for a computational problem,
 and concludes which one is better, according to some criteria.
 Possible criteria include:
+
 - time and space complexity
 - empirical run-times and memory used
 - simplicity of the solution
@@ -99,6 +84,7 @@ as no essay can explain everything from first principles. For example,
 tell the reader that they must know about binary trees to understand your essay.
 
 Following the introduction, use section headings to structure your essay, for example:
+
 - **Problem**: this section describes the problem, with some examples.
 - **Algorithms**: this section outlines two or more algorithms that solve the problem and their complexity.
 - **Implementations**: this section implements and tests only the most promising algorithms.
@@ -108,6 +94,7 @@ Following the introduction, use section headings to structure your essay, for ex
 The algorithms and implementations sections may have subsections, one per algorithm.
 
 An alternative structure implements each approach before evaluating all of them:
+
 - **Problem**: this section describes the problem, with some examples.
 - **First approach**: this section outlines an algorithm, implements it and tests it.
 - **Second approach**: this section presents another algorithm and its implementation.
@@ -187,10 +174,10 @@ unit_tests = [
 # run the function on all test inputs and compare the actual and expected outputs
 test(absolute_difference, unit_tests)
 ```
-This produces:
-> Testing absolute_difference:\
-> x < y FAILED: -11 instead of 11\
-> Tests finished.
+!!! failure "Output"
+    Testing absolute_difference:  
+    x < y FAILED: -11 instead of 11  
+    Tests finished.
 
 A unit test consists of the input values to pass to your function and the output value you're expecting.
 The library requires a short descriptive string for each unit test, so that it can indicate which tests failed.
@@ -214,8 +201,9 @@ def absolute_difference_without_abs(x: int, y: int) -> int:
 
 test(absolute_difference_without_abs, unit_tests) # same test table
 ```
-> Testing absolute_difference_without_abs:\
-> Tests finished.
+!!! success "Output"
+    Testing absolute_difference_without_abs:  
+    Tests finished.
 
 ### Type checking
 As the above examples show, your code should contain type hints
@@ -227,7 +215,8 @@ After importing the `algoesup` library, you can turn on type checking as follows
 ```python
 %pytype on
 ```
-> pytype was activated
+!!! success "Output"
+    pytype was activated
 
 Words that start with `%` are special commands for IPython, the Python interpreter used by Jupyter notebooks.
 The `%pytype` command, provided by our library, activates Google's `pytype` type checker,
@@ -243,10 +232,12 @@ def double(x: int) -> int:
 
 double([4])
 ```
-> [4, 4]
->
-> **pytype** found issues:
-> - 5: Function double was called with the wrong arguments \[[wrong-arg-types](https://google.github.io/pytype/errors.html#wrong-arg-types)\]
+!!! failure "Output"
+    [4, 4]
+
+    **pytype** found issues:
+
+    - 5: Function double was called with the wrong arguments \[[wrong-arg-types](https://google.github.io/pytype/errors.html#wrong-arg-types)\]
 
 The function is executed and produces an output because lists can also be 'multiplied' with an integer,
 but the type checker detects that line 5 should have passed integers, not lists of integers, to the function.
@@ -259,12 +250,12 @@ However, some checking is better than no checking.
 The type checker adds some seconds to the overall time to run each code cell.
 You may thus wish to initially turn off the type checking, with `%pytype off`,
 and only turn it on after all code is written and tested.
-You will have to [run all cells]({{site.baseurl}}/deepnote-how-to#run-one-or-all-cells) for the type checking to take place.
+You will have to [run all cells](deepnote-how-to.md#run-one-or-all-cells) for the type checking to take place.
 
 ### Formatting
 Once you have written, tested and type checked all your code, you should format it so that
 it follows the Python community's code style.
-You will need to format each cell, as explained [here]({{site.baseurl}}/deepnote-how-to#format-a-code-cell).
+You will need to format each cell, as explained [here](deepnote-how-to.md#format-a-code-cell).
 
 If there's a block of code that you don't want the formatter to change,
 write `# fmt: off` on its own line before the block and write `# fmt: on` after the block,
@@ -285,7 +276,8 @@ importing `algoesup`.
 ```python
 %ruff on
 ```
-> ruff was activated
+!!! success "Output"
+    ruff was activated
 
 From now on, each cell is automatically linted after it's executed. Here's an example:
 ```python
@@ -293,15 +285,18 @@ l = [1, 2, 3]
 if (not 5 in l) == True:
     print("5 isn't in the list")
 ```
-> 5 isn't in the list
->
-> **ruff** found issues:
-> - 1: \[[E741](https://docs.astral.sh/ruff/rules/ambiguous-variable-name)\] Ambiguous variable name: `l`
-> - 2: \[[PLR2004](https://docs.astral.sh/ruff/rules/magic-value-comparison)\] Magic value used in comparison, consider replacing 5 with a constant variable
-> - 2: \[[E713](https://docs.astral.sh/ruff/rules/not-in-test)\] Test for membership should be `not in`. Suggested fix: Convert to `not in`
-> - 2: \[[E712](https://docs.astral.sh/ruff/rules/true-false-comparison)\] Comparison to `True` should be `cond is True` or `if cond:`. Suggested fix: Replace with `cond is True`
+!!! failure "Output"
+    5 isn't in the list
+
+    **ruff** found issues:
+
+    - 1: \[[E741](https://docs.astral.sh/ruff/rules/ambiguous-variable-name)\] Ambiguous variable name: `l`
+    - 2: \[[PLR2004](https://docs.astral.sh/ruff/rules/magic-value-comparison)\] Magic value used in comparison, consider replacing 5 with a constant variable
+    - 2: \[[E713](https://docs.astral.sh/ruff/rules/not-in-test)\] Test for membership should be `not in`. Suggested fix: Convert to `not in`
+    - 2: \[[E712](https://docs.astral.sh/ruff/rules/true-false-comparison)\] Comparison to `True` should be `cond is True` or `if cond:`. Suggested fix: Replace with `cond is True`
 
 Every message indicates the line of the problem.
+
 - The first message is trying to tell us that `l` can be misread for `1` (one).
 - The second message recommends using constants, like `EXPECTED_VALUE`,
   instead of literals like 5 that are meaningless to the reader.
@@ -338,7 +333,8 @@ by your peers in terms of Python constructs, just add a cell:
 ```python
 %allowed on
 ```
-> allowed was activated
+!!! success "Output"
+    allowed was activated
 
 Henceforth, after a cell is executed, the `allowed` linter will list any constructs,
 modules or built-in types we haven't taught, like this:
@@ -347,11 +343,13 @@ from math import pi, sin
 
 print(f"π is approximately {pi:.5f}.")
 ```
-> π is approximately 3.14159.
->
-> **allowed** found issues:
-> - 1: sin
-> - 3: f-string
+!!! success "Output"
+    π is approximately 3.14159.
+
+    **allowed** found issues:
+
+    - 1: sin
+    - 3: f-string
 
 We haven't taught the `math.sin()` function nor f-strings, and `allowed` reports these.
 
@@ -366,7 +364,7 @@ in case you want to use even fewer constructs in your essay.
 To use that configuration, write `%allowed on -c tm112.json`.
 
 You can configure the linter with a JSON file that lists the allowed constructs.
-You can [duplicate and rename]({{site.baseurl}}/deepnote-how-to#rename-duplicate-download-or-delete-a-notebook-or-file)
+You can [duplicate and rename](deepnote-how-to.md#rename-duplicate-download-or-delete-a-notebook-or-file)
 one of the JSON configurations in the **Files** section of your project,
 and adapt it to your course.
 See the `allowed` [website](https://dsa-ou.github.io/allowed) for instructions.
@@ -424,6 +422,7 @@ To measure the run-times of a function `f`  on best, average and worst case inpu
 library function `time_cases(f, [case1, case2, ...], s, d)`.
 The second argument can be a list (or tuple) of up to 6 input-generating functions.
 The `time_cases` function works as follows.
+
 1. Call `case1(s)` to generate inputs of size `s` for `f`.
 2. Run function `f` on the generated inputs and measure its run-time.
 3. Do the two previous steps with each of the functions `case2, ...`.
@@ -438,8 +437,8 @@ from algoesup import time_cases
 
 time_cases(selection_sort, [ascending, descending], start_size=100, double=4)
 ```
-This produces something like:
-
+!!! success "Output"
+    ```
     Run-times for selection_sort
 
     Input size       ascending      descending
@@ -448,6 +447,7 @@ This produces something like:
            400          2716.7          2817.9 µs
            800         11072.4         11407.3 µs
           1600         44285.3         45512.7 µs
+    ```
 
 Running selection sort on lists from 100 to 1600 integers takes about 170 microseconds to 45 milliseconds.
 To measure precisely such small time spans, function `f` (here, `selection_sort`) is called
@@ -483,8 +483,8 @@ from algoesup import time_functions
 
 time_functions([selection_sort, sorted], descending, start_size=100, double=4)
 ```
-This produces something like:
-
+!!! success "Output"
+    ```
     Inputs generated by descending
 
     Input size  selection_sort          sorted
@@ -493,6 +493,7 @@ This produces something like:
            400          2795.7             1.6 µs
            800         11534.0             3.1 µs
           1600         45470.0             5.9 µs
+    ```
 
 As expected, the built-in sorting implementation is much, much faster.
 
@@ -504,11 +505,14 @@ If you only want to see the chart, then add arguments `text=False, chart=True`.
 ```python
 time_cases(sorted, [ascending, descending], 100, 4, text=False, chart=True)
 ```
-![chart only](sorted.png)
+!!! success "Output"
+    ![chart only](sorted.png)
 
 ```python
 time_functions([sorted, selection_sort], ascending, 100, 4, chart=True)
 ```
+!!! success "Output"
+    ```
     Inputs generated by ascending
 
     Input size          sorted  selection_sort
@@ -517,8 +521,8 @@ time_functions([sorted, selection_sort], ascending, 100, 4, chart=True)
            400          1496.9       2720369.2 ns
            800          2850.4      11090135.4 ns
           1600          5553.0      44372758.4 ns
-
-![times and chart](ascending.png)
+    ```
+    ![times and chart](ascending.png)
 
 The `1e7` above the y-axis means that the run-times must be multiplied by 10⁷, i.e. 10 million.
 
@@ -533,6 +537,7 @@ and in `time_cases(f, [case1, case2, ...], ...)` the worst case should be `case1
 
 ### Interpreting run-times
 If, as the input size doubles, the run-times...
+
 - ...remain the same, then the function has constant complexity.
 - ...also double, then the function has linear complexity.
 - ...quadruple, then the function has quadratic complexity.
@@ -553,6 +558,7 @@ Increase `start_size` and run again the code cell.
 
 If after increasing the start size several times you still don't get the run-times
 you expect from your complexity analysis, then there might be other explanations:
+
 - your complexity analysis is wrong
 - your implemented algorithm modifies its input
 - your input-generating functions are not generating best or worst cases.
@@ -570,7 +576,7 @@ Look at Deepnote's table of contents on the sidebar and check that your section
 are at the right level.
 
 Finally, let others comment on your essay and help you produce a better version.
-See our [feedback guide]({{site.baseurl}}/feedback) for details.
+See our [feedback guide](feedback.md) for details.
 
 ## Further reading
 If you're interested and have the time, here are further details on some of the above.
diff --git a/mkdocs.yml b/mkdocs.yml
new file mode 100644
index 0000000..8e82485
--- /dev/null
+++ b/mkdocs.yml
@@ -0,0 +1,90 @@
+site_name: "Algorithmic Essays"
+repo_url: https://github.com/dsa-ou/algoesup
+repo_name: dsa-ou/algoesup
+copyright: Copyright (c) 2023–2024 The Open University
+
+plugins:
+- mkdocstrings:
+    handlers:
+      python:
+        paths: [Deepnote]
+        options:
+          docstring_style: null
+          separate_signature: true
+          show_signature_annotations: true
+          show_source: false
+- mkdocs-jupyter
+- open-in-new-tab
+- search        
+
+watch:                    # folders that `mkdocs serve` will watch for changes
+- Deepnote                # look for changes in algoesup.py
+
+extra:
+  social:                 # links for the footer
+    - icon: fontawesome/brands/github
+      link: https://github.com/dsa-ou/algoesup
+    - icon: octicons/package-16
+      link: https://pypi.org/project/algoesup/
+    - icon: simple/deepnote
+      link: https://deepnote.com/workspace/lpsae-cc66-cd5cf5e4-ca6e-49d8-b6ee-dbbf202143d3/project/Algorithmic-Essays-acd23b74-5d63-4ef4-a991-3b8a049ddf6b
+
+markdown_extensions:
+  - admonition            # allow !!! note / warning / info / example / etc.
+  - attr_list             # allow {.class} after text, e.g. for buttons
+  - smarty                # curly quotes, guillemots, -- for en-dash, --- for em-dash
+  - pymdownx.highlight    # highlight code with Pygments
+  - pymdownx.smartsymbols # typeset 1/4 as ¼, 1st as 1^{st}, (c) as ©, +/- as ±, etc.
+  - pymdownx.superfences  # needed for highlighting
+
+extra_css:
+  - stylesheets/extra.css # change look of admonitions
+
+theme:
+  name: material
+  font: false             # use system font stack
+  features:
+    - content.code.copy   # add copy button to code blocks
+    - navigation.footer   # add previous/next buttons below the page
+    - navigation.sections # non-collapsible sections, listing their pages
+    # the following make navigation more confusing or require extra clicks
+    # - navigation.tabs     # show sections in header; nav panel only shows current section
+    # - navigation.tabs.sticky
+    # - toc.integrate       # show TOC in left panel, not separate right panel
+  icon:                   # icon next to repo url/name
+    repo: fontawesome/brands/github
+  palette:
+    - scheme: default     # light mode
+      toggle:
+        icon: material/brightness-6
+        name: Switch to dark mode
+    - scheme: slate       # dark mode
+      toggle:
+        icon: material/brightness-6
+        name: Switch to light mode
+
+nav:
+  - Introduction:
+    - Home: index.md
+    - example-essays.md
+    - getting-started.md
+  # not in the nav panel due to https://github.com/danielfrg/mkdocs-jupyter/issues/189
+  # - Templates:
+  #   - Basic: essays/template-intro-programming.ipynb
+  #   - Extended: essays/template-data-structures.ipynb
+  # - Examples:
+  #   - essays/example-1-to-n.ipynb
+  #   - essays/example-jewels.ipynb
+  #   - essays/example-two-sum-2.ipynb
+  #   - essays/example-two-sum-3.ipynb
+  - Guides:
+    - writing.md
+    - feedback.md
+  - Library:
+    - Reference: library.md
+  - Deepnote:
+    - Overview: deepnote.md
+    - How-to: deepnote-how-to.md
+    - deepnote-background.md
+    - deepnote-reference.md
+    - Project: https://deepnote.com/workspace/lpsae-cc66-cd5cf5e4-ca6e-49d8-b6ee-dbbf202143d3/project/Algorithmic-Essays-acd23b74-5d63-4ef4-a991-3b8a049ddf6b
diff --git a/requirements.txt b/requirements.txt
index 5b7e732..8fcd0c6 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -2,4 +2,9 @@ jupyter
 black[jupyter]
 matplotlib==3.8.0
 pytype==2023.12.8
-ruff==0.1.8
\ No newline at end of file
+ruff==0.1.8
+mkdocs
+mkdocs-material
+mkdocstrings[python]
+mkdocs-jupyter
+mkdocs-open-in-new-tab