This repository has been archived by the owner on Sep 16, 2019. It is now read-only.
Improved foundation.scss file #606
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
olefredrik
added a commit
that referenced
this pull request
Dec 11, 2015
Improved foundation.scss file
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Individual components should all be imported in one line through
@import foundation. This just loads the mixins for the components and does not add any CSS. When you@includethe individual components is when CSS is added so those are the only items that need to be commented out if you want to exclude them.Look at how the Foundation Zurb Template does it for reference: https://github.com/zurb/foundation-zurb-template/blob/master/src/assets/scss/app.scss
Here's a discussion on this: zurb/foundation-sites-6#20 (comment)