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

Add ability to build and map alternate documentation formats #70

Open
samuel-emrys opened this issue May 25, 2021 · 3 comments · May be fixed by #74
Open

Add ability to build and map alternate documentation formats #70

samuel-emrys opened this issue May 25, 2021 · 3 comments · May be fixed by #74

Comments

@samuel-emrys
Copy link

Sphinx is capable of building documentation in a range of different formats detailed by sphinx.builders. It would be good to be able to support building and indexing all of these such that they are linkable via the widget. It's a feature that I really like about what readthedocs does. I'm personally only really interested in pdf, but here's a list of formats that might be useful:

  • pdf
  • text
  • epub
  • xml (maybe?)

Example of what I would like to be able to do with respect to the "Downloads" section:

rtd_downloads

If you can provide some advice on how this might be best implemented I might be able to allocate some time to implementing this.

samuel-emrys added a commit to samuel-emrys/sphinx-multiversion that referenced this issue Jun 2, 2021
Add documentation detailing appropriate configuration of the
smv_build_targets configuration setting including exemplars to
illustrate the features and also limitations of this feature.

Add documentation detailing appropriate configuration of the
smv_clean_intermediate_files configuration setting.

Add exemplar usage of the new artefacts object in the html context
within template files.

Closes Holzhaus#70.
samuel-emrys added a commit to samuel-emrys/sphinx-multiversion that referenced this issue Jun 2, 2021
Add documentation detailing appropriate configuration of the
smv_build_targets configuration setting including exemplars to
illustrate the features and also limitations of this feature.

Add documentation detailing appropriate configuration of the
smv_clean_intermediate_files configuration setting.

Add exemplar usage of the new artefacts object in the html context
within template files.

Closes Holzhaus#70.
@Holzhaus
Copy link
Owner

Holzhaus commented Jun 17, 2021

I implemented that for https://manual.mixxx.org over at @mixxxdj/manual by using the HTML context variables to construct a path.

@samuel-emrys
Copy link
Author

samuel-emrys commented Jun 17, 2021

Hi @Holzhaus , I'm not sure that's exactly the same thing. That requires you to independently and externally generate the pdf documentation. What I've implemented in PR #74 will use sphinx builders to generate the pdf version of the documentation at the same time as the html documentation for each version and make a link to that artefact available in the build context.

The "for each version" part of documentation generation is the hard part when it comes to creating artefacts, without essentially recreating everything that sphinx-multiversion already does - so I think that it has a place within the scope of sphinx-multiversion.

Unless you're integrating your pdf build with sphinx-multiversion in a way that I can't see?

@samuel-emrys
Copy link
Author

@Holzhaus can you elaborate on how you're building the pdf documentation?

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 a pull request may close this issue.

2 participants