_layouts: Include CSS inline #32
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
For some reason, GitHub Pages doesn't seem to be including the assets like it should be and is replacing them with normalize. I don't know why this is, but it could be a while before I figure out what's happening. In the interim, hack around the problem by just moving the CSS inline. This involves copying 'style.css' to the the '_includes' folder so we can "include" it inside a '<style>' tag. Signed-off-by: Stephen Finucane <stephen@that.guru>
|
This is a bit of a hack, but there's nothing semantically wrong with it and it should get things up and running again (finally). Who knows what's happening with GitHub Pages 😕 |
|
Thanks! |
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.
For some reason, GitHub Pages doesn't seem to be including the assets
like it should be and is replacing them with normalize. I don't know why
this is, but it could be a while before I figure out what's happening.
In the interim, hack around the problem by just moving the CSS inline.
This involves copying 'style.css' to the the '_includes' folder so we
can "include" it inside a '<style>' tag.
Signed-off-by: Stephen Finucane stephen@that.guru