Docs Automation Baseline#
This page documents the shared docs and CI baseline for
design-research-problems.
The problems repo shares the common module-repo docs baseline with the rest of the family, but it also owns one repo-specific generator: the public problem catalog. This page clarifies where the shared baseline ends and where problem-catalog-specific automation begins.
Workflow Responsibilities#
ci.ymlowns lint, type, test, docs-consistency, docstring, and coverage-oriented checks.examples.ymlowns example execution, generated example docs, and example-derived badge metrics.docs-pages.ymlowns the published docs build.workflow.ymlremains the aggregate maintainer workflow entry point.
Problem-Catalog-Specific Automation#
design-research-problems also owns one repo-specific generator that is not
part of the generic shared baseline:
scripts/generate_problem_catalog_docs.py
That generator produces the full packaged-problem catalog under
docs/problem_catalog/. It is intentionally a problems-only utility because
no other repo exposes a comparable public inventory of benchmark entries.
The shared baseline vs repo-specific split is therefore:
Shared baseline: docs checks, badges, examples, and docs publishing.
Problems-specific utility: generated catalog pages and the curation layer that explains how to browse them.
When To Update This Page#
Refresh this page whenever workflow ownership changes or when a new docs, examples, badge, or catalog-generation utility becomes part of the expected maintainer flow.