Skip to content

Build a parallel Furo site from the Rd topics - #166

Open
soodoku wants to merge 2 commits into
masterfrom
sphinx-docs-pilot
Open

soodoku wants to merge 2 commits into
masterfrom
sphinx-docs-pilot

Conversation

@soodoku

@soodoku soodoku commented Aug 21, 2026

Copy link
Copy Markdown
Member

sphinx-docs.yml calls r-canon's new reusable-sphinx.yml, which renders
tuber's help topics into semantic Sphinx objects with
rd2sphinx and builds them under
sphinx-build -W --keep-going.

The pkgdown site is untouched. There is deliberately no deploy: on this
shim, so nothing races it for the Pages deployment. Every run uploads the HTML
as a tuber-furo-site artifact instead, which is what makes the two builds
comparable before anyone decides whether to switch.

What the build produces, run locally against this branch

  • 73 reference pages from 128 Rd topics with include = "exports"
  • 77 Furo HTML pages, clean under -W --keep-going
  • all 73 names in NAMESPACE's export() directives have a page (checked
    name by name, not counted)
  • 308 entries in objects.inv, including package-qualified forms such as
    tuber::yt_search, so other Sphinx projects can link into tuber
  • genindex.html and searchindex.js present

Depends on

gojiplus/r-canon#20, and resolves once v2 advances to include it.

Blocked until then: reusable-sphinx.yml@v2 does not exist yet, so this
workflow will fail to resolve on the first run.

sphinx-docs.yml calls r-canon's reusable-sphinx.yml, which renders tuber's
help topics into semantic Sphinx objects with rd2sphinx and builds them under
sphinx-build -W --keep-going. All 73 exported objects get a page, and each is
registered in objects.inv so other Sphinx projects can link into them.

Deliberately no deploy: the pkgdown site stays the published one. Every run
uploads the HTML as a tuber-furo-site artifact instead, which is what makes
the two comparable before anyone decides whether to switch.
rd2sphinx now renders Rd bodies with R's own tools::Rd2HTML rather than
translating them by hand, and no longer configures Furo's view-source and
edit-this-page buttons. Those pointed at sphinx-docs/reference/*.rst, which is
generated on every build and not in version control: the view link 404'd, and
the edit link opened GitHub's create-a-new-file editor for a path that does not
exist, which would have committed a build artifact.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant