Add custom CSS to documentation #640
Merged
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
|
Nice one @mtorpey, I've enabled auto-merge so if the CI passes this'll be merged. |
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.
It may be useful to have our own custom CSS in the HTML version of manual, as recently when adding images in figures. There's some system for this in GAPDoc, but it appears to be for adding user-choosable styles that can be turned on and off, which isn't quite what we want. Here, we simply append some custom css to GAPDoc's main
manual.cssfile after copying it to the directory, which the GAPDoc manual at least says we're allowed to do.This can hopefully avoid hacky non-semantic HTML we might be tempted to write in the future.