An alternative way to make style changes to html output without recreating an entire new theme via documentation.yml #1356
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
Added content about an alternative way to establish style.
An alternative way to make style changes to html output without recreating an entire new theme via documentation.yml
|
👍 cool enough for folks wanting to do this, thanks! |
This was referenced Mar 14, 2021
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.
Added content about an alternative way to make style changes without recreating an entire new theme that needs to be pulled in as a separate node module or even a separate repository.
There are a couple reasons I can imagine this isn't best practice. There are likely additional reasons.
However, it has so much "easy and just works" quality, that I figured I'd share.