Closed abea closed 5 years ago
Interesting. Shouldn't be a problem, you'll just be pushing those styles on the real site.
Sorry, I realized that the skeleton.css
file includes a lot of element targeted styling, and worry this could conflict with a lot of project styles. Perhaps #23 would be the right solution, and we can leave the bare bones styles for the pk-pattern-library chrome to exist in extraHead, so we're not pushing it via pushAssets?
@grdunn Why don't you want to push it with pushAsset
?
@abea won't that push the styles on every page load?
Oh, you're right. That's not ideal.
Closes #23
The main thing lost here is the html
style since it doesn't go under the body class. Our projects have that in the boilerplate already, though.
Bumping this.
@abea The only thing I would be sad to see go is the Nunito type treatment that was used as the default for the design. I believe this was initially not great, because it set on the body and cascading down. Ideally, we could scope the $pkpl-font-family
sass variable to appropriate classes.
There should be classes in the markup to target, ie:
pkpl__group-title
pkpl__navigation-section-title
pkpl__navigation-group-title
Ah -- I am seeing this now here:
Edit: Seeing now that was later removed. Heh.
Moving this since they were overriding my project styles too easily.