Create HTML export #360
Open
Create HTML export #360
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This creates a new command:
which uses LaTeXML to convert the manuscript to an HTML version. It uses @dginev's https://github.com/dginev/ar5ivist which is a good set of defaults and css files (same settings used in ar5iv.org).
In particular it uses the
ar5ivistdocker image, so if a user wants to use this, they need to have docker setup. There's currently no conda-forge implementation of latexml, so this is the only option.I could also create a GitHub action for this if it's of interest. In theory you could have a GitHub pages be generated for any SYW paper hosted on GitHub.
@dfm wdyt? I know you are interested in mystjs as well so I'll just point out that this would not rule out mystjs integration; they could definitely be integrated in some way. This is just a LaTeX -> HTML converter that works on the exact same input files.
This would likely be better suited as a plugin or a
.contribbut I found it really difficult to get it working this way due to the "spooky action at a distance" import structure in the.smkfiles. This seems like the only option for right now. Maybe we can refactor things later so that plugins/user-defined postprocessing is possible.Fixes #321