Remove common Micro.blog elements from head and use new partial instead #21
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
|
@svendahlstrand I'm a little out of my element with this one. Is there anything I need to change outside of adding this partial, such as modifying/deleting any other files? |
|
Well, I can't tell you with 100% certainty. In theory, you could have JavaScript or some other external thing that depends on how stuff was organized in the But, as with any change, it's probably a good idea for you to test my changes as well before merging. |
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.
Hey! 👋 This pull request introduces the new partial that is provided by the Micro.blog environment. With that, we know that all the necessary Micro.blog head elements are present, with the added bonus of making this theme compatible with Hugo 0.117.
I'm not bumping the version number; that's up to you, @pimoore, should you decide to merge this one.