Link to docs in core notebook

[ricardoV94]

Description

In this section: https://www.pymc.io/projects/docs/en/stable/learn/core_notebooks/dims_module.html#what-functionality-is-supported

We should link to the relevant docs entries:

• https://www.pymc.io/projects/docs/en/stable/api/dims/distributions.html
• https://www.pymc.io/projects/docs/en/stable/api/dims/transforms.html
• https://www.pymc.io/projects/docs/en/stable/api/dims/math.html

Also every time we reference a specific distribution ZeroSumNormal, Categorical, we should link to the specific entry.

The notebook name is a bit silly with PyMC dims module, what other library would it be?. Let's rename it simply to Dims module

[monikagotnochills]

I’ve reviewed the CONTRIBUTING guidelines and the Jupyter style guide, and I understand we need to:

Rename the notebook title to “Dims module”.

Insert links to the dims.distributions, dims.transforms, and dims.math API pages.

Add inline links for each referenced distribution (e.g. ZeroSumNormal, Categorical)
I would like to formally request ownership of the documentation improvements for the Dims module (https://www.pymc.io/projects/docs/en/stable/learn/core_notebooks/dims_module.html#what-functionality-is-supported)). I’ve prepared a clear approach to ensure high-quality, maintainable updates:

My Implementation Plan:
Title Optimization

Rename PyMC dims module: what functionality is supported? → Dims module: what functionality is supported? to eliminate redundancy.

For Documentation Linking

I will add a dedicated "Relevant Docs" section with:

markdown

• Distributions
• Transforms
• Math
  Automated Distribution Linking

Develop a Python script to auto-link key terms (e.g., ZeroSumNormal, Categorical) to their docs:

Uses nbformat to parse notebooks

Skips code blocks/inline code via regex splitting

Replaces:
ZeroSumNormal → ZeroSumNormal
Categorical → Categorical

Quality Assurance

Manual verification of all links

Pre-commit hook to prevent regression

Screenshot validation of rendered changes
My timeline to complete the project would be!
Phase 1 (2 days): Implement title + doc links

Phase 2 (3 days): Build/test linking script

Phase 3 (1 day): Full regression check

Final Deliverable: PR with updated notebook + verification report

[ricardoV94]

This issue definitely doesn't need an LLM planning ;)