[Sync to prerelease] document mode-specific content #1657
Merged
Conversation
This file contains hidden or 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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.
Description
Sync of #1656 to
prerelease.Original PR
document mode-specific content
This documents the CSS classes
.light-contentand.dark-content, as suggested by @mcanouil on 4/28.It also adds a subsection header for "cell renderings" on the execution options page, to make it easier to link to that content.
I also noticed that the html themes page contains documentation of our use of SCSS for dark mode on quarto-web itself, so I updated it.
I'm always torn between making documentation useful or didactic. The
.light-content/.dark-contentexample here may be too didactic, as dark-specific text is not a thing that people generally want to do.