You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Read the Docs injects some custom values into the MkDocs configuration (mostly extra CSS and JS), and Pydoc-Markdown should pick that up.
Pydoc-Markdown should also pick up the --site-dir argument which is where Read the Docs expects the HTML content to go to. The current workaround is to manually pass --site-dir $PWD/_build/html as an argument to Pydoc-Markdown.
And with readthedocs-custom-steps, we still have access to all of these arguments starting with mkdocs. Pydoc-Markdown could have a mode where arguments are passed to the renderer directly, for example
$ pydoc-markdown -- "$@"
Which can then parse the --site-dir as well as the --config-file.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
--site-dir
argument which is where Read the Docs expects the HTML content to go to. The current workaround is to manually pass--site-dir $PWD/_build/html
as an argument to Pydoc-Markdown.Describe the solution you'd like
Read the Docs kicks of MkDocs builds like this:
And with
readthedocs-custom-steps
, we still have access to all of these arguments starting withmkdocs
. Pydoc-Markdown could have a mode where arguments are passed to the renderer directly, for exampleWhich can then parse the
--site-dir
as well as the--config-file
.The text was updated successfully, but these errors were encountered: