Update documentation contributor guide

[dprada]

Summary

• replace the docs README stub with a detailed contributor guide for building and publishing documentation
• highlight environment setup, notebook execution, autosummary cleanup, and GitHub Pages workflow expectations
• remind contributors about tracking .nbconvert.last_run markers and include a docs-focused pre-PR checklist

Testing

• not run

---

https://chatgpt.com/codex/tasks/task_e_69082a46b5c48326b8aae92a69837211

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.23%. Comparing base (6a88cc8) to head (40798b6).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Fix broken conda environment commands

The environment setup snippet uses conda env create -f devtools/conda-envs/docs_env.yaml and conda env update -f …, but the YAML file does not define an environment name. Running those commands raises CondaValueError: Key 'name' missing unless the user supplies a name or the helper scripts are used. The instructions should either pass -n <env> or point contributors to create_conda_env.py/update_conda_env.py so setup succeeds【F:docs/README.md†L24-L32】【F:devtools/conda-envs/docs_env.yaml†L1-L18】

Useful? React with 👍 / 👎.