minor doc fixes

docs/source/conf.py

@@ -44,11 +44,9 @@
     "IPython.sphinxext.ipython_console_highlighting",
     "IPython.sphinxext.ipython_directive",
     "sphinx.ext.autosectionlabel",
-    "sphinx.ext.napoleon",
     "myst_nb",
     "sphinx_design",
     "notfound.extension",
-    "sphinx_design",
     "sphinx_copybutton",
 ]
 
@@ -232,7 +230,7 @@
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
-# html_static_path = ["_static", "nb_tutorials/_images", "nb_examples/_images"]
+html_static_path = ["../logos"]
 
 # Add any extra paths that contain custom files (such as robots.txt or
 # .htaccess) here, relative to this directory. These files are copied

docs/source/contributing/jupyter_style.md

@@ -29,10 +29,14 @@ the repository where the notebook is in (pymc or pymc-examples).
 * When using non meaningful names such as single letters, add bullet points with a 1-2 sentence description of each variable below the equation where they are first introduced.
 
 
-## Post directive
-The first cell of all example notebooks should have a level 1 markdown title (that is a title with a single `#`) followed by the post directive. The syntax of the post directive is as follows:
+## First cell
+The first cell of all example notebooks should have a MyST target, a level 1 markdown title (that is a title with a single `#`) followed by the post directive.
+The syntax is as follows:
+
+```markdown
+(notebook_id)=
+# Notebook Title
 
-```
 :::{post} Aug 31, 2021
 :tags: tag1, tag2, tags can have spaces, tag4
 :category: level
@@ -42,15 +46,22 @@ The first cell of all example notebooks should have a level 1 markdown title (th
 
 The date should correspond to the latest update/execution date, at least roughly (it's not a problem if the date is a few days off due to the review process before merging the PR). This will allow users to see which notebooks have been updated lately and will help the PyMC team make sure no notebook is left outdated for too long.
 
-Tags can be anything, but we ask you to try to use [existing tags](https://github.com/pymc-devs/pymc/wiki/Categories-and-Tags-for-PyMC-Examples) to avoid the tag list from getting too long. Each notebook should
-have a single category indicating the level of the notebook. Choose a category from [existing categories](https://github.com/pymc-devs/pymc/wiki/Categories-and-Tags-for-PyMC-Examples#categories).
+The [MyST target](https://myst-parser.readthedocs.io/en/latest/syntax/syntax.html#targets-and-cross-referencing)
+is important to ease referencing and linking notebooks between each other.
+
+Tags can be anything, but we ask you to try to use [existing tags](https://github.com/pymc-devs/pymc/wiki/Categories-and-Tags-for-PyMC-Examples)
+to avoid the tag list from getting too long.
+
+Each notebook should have a single category indicating the level of the notebook.
+Choose a category from [existing categories](https://github.com/pymc-devs/pymc/wiki/Categories-and-Tags-for-PyMC-Examples#categories).
 
 Authors should list people who authored, adapted or updated the notebook. See {ref}`jupyter_authors`
 for more details.
 
 ## Code preamble
 
-In a cell just below the cell where you imported matplotlib (usually the first one), set the ArviZ style to darkgrid (this has to be in another cell than the MPL import because of the way MPL sets its defaults):
+In a cell just below the cell where you imported matplotlib and/or ArviZ (usually the first one),
+set the ArviZ style to darkgrid (this has to be in another cell than the matplotlib import because of the way matplotlib sets its defaults):
 
 ```python
 RANDOM_SEED = 8927
@@ -122,6 +133,7 @@ and `<date>` should preferably be month and year.
 
 authored
 : for notebooks created specifically for pymc-examples
+
 adapted
 : for notebooks adapted from other sources such as books or blogposts.
   It will therefore follow a different structure than the example above
@@ -130,9 +142,11 @@ adapted
   ```markdown
   Adapted from Alice's [blogpost](blog.alice.com) by Bob and Carol on ...
   ```
+
 re-executed
 : for notebooks re-executed with a newer PyMC version without significant changes to the code.
   It can also mention the PyMC version used to run the notebook.
+
 updated
 : for notebooks that have not only been re-executed but have also had significant updates to
   their content (either code, explanations or both).

docs/source/index.md

@@ -19,6 +19,7 @@ Probabilistic Programming in Python
 :::{button-ref} learning
 :color: primary
 :ref-type: ref
+:class: sd-fs-2 sd-px-5
 
 Get started!
 :::
@@ -94,6 +95,7 @@ PyMC is a non-profit project under NumFOCUS umbrella. If you value PyMC and want
 ::::{div} sd-d-flex-row sd-align-major-center
 :::{button-link} https://numfocus.org/donate-to-pymc3
 :color: secondary
+:class: sd-fs-2 sd-px-5
 
 
 Donate
@@ -108,13 +110,13 @@ Donate
 :::
 
 :::{grid-item-card}
-:img-background: https://www.numfocus.org/wp-content/uploads/2017/07/NumFocus_LRG.png
+:img-background: _static/sponsors/numfocus.png
 :link: https://numfocus.org/
 :shadow: none
 :::
 
 :::{grid-item-card}
-:img-background: https://github.com/pymc-devs/pymc/raw/main/docs/pymc-labs-logo.png
+:img-background: _static/sponsors/pymc-labs.png
 :link: https://www.pymc-labs.io/
 :shadow: none
 :::