Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Style Guide for Writing Sphinx Extensions #578

Open
4 tasks
mmcky opened this issue Dec 14, 2021 · 1 comment
Open
4 tasks

Style Guide for Writing Sphinx Extensions #578

mmcky opened this issue Dec 14, 2021 · 1 comment
Assignees

Comments

@mmcky
Copy link
Member

mmcky commented Dec 14, 2021

The documentation for writing sphinx extensions can be confusing and incomplete. It would be nice to put together a style guide that captures some of the learning from the ebp project so that others can use it (or possibly upstream to Sphinx).

I think there is scope to write both a tutorial and reference elements to the documentation:

  • tutorial for writing an extension for jupyter-book for custom admonitions
  • more details on the overall execution model of sphinx (init, parsing, transforms, post_tranforms, translators)

Other Topics:

  • how cross referencing works in sphinx
  • adding compatibility with ref and numref via labels
@mmcky mmcky self-assigned this Dec 14, 2021
@choldgraf
Copy link
Member

Im a big fan of minimal reproducible examples. Could we define the 4-5 most common ways to extend Sphinx, and document a minimal reproducible examples for each? That could be useful to copy paste as well as teach

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

No branches or pull requests

2 participants