Menu icon Foundation

My Posts

  • 2
    Replies
  • Normalize.css no longer needed?

    By Paul

    normalizecssscss

    Hello everyone. So I noticed that in the example generate index.html pages Normalize.css is no longer included. Is this because Foundation 5 +jquery2.0 only supports browsers that don't need normalize.css anyway? or maybe just an oversight? If... (continued)

    Last Reply by Rafi Benkual over 4 years ago


  • 5
    Replies
  • Optimize for used styles

    By Paul

    cssfile size

    Hello, I'm wondering if there is some type of optimizer to just generate used styles. Out of the box, foundation has a ton of canned styles/functionality however at a size cost. Question: using some precompilation tool like compass, is there a way to... (continued)

    Last Reply by Subwaysurfersmod about 2 months ago


My Comments

Paul commented on Paul's post over 4 years

Not sure if it's needed with "modern browsers." Probably. Anyway I found a reference to including it via sass precompilation:

https://github.com/zurb/foundation/issues/3187

Hope this helps someone else with the same concern since it wasn't very apparent in the getting started docs :p

Paul commented on Paul's post over 4 years

Also, if generating components via .scss you can also comment out import lines in foundation.scss

here is where each is brought in:

// Make sure the charset is set appropriately
@charset "UTF-8";

// Behold, here are all the Foundation components.
@import
"foundation/components/accordion",
"foundation/components/alert-boxes",
"foundation/components/block-grid",
"foundation/components/breadcrumbs",
"foundation/components/button-groups",
"foundation/components/buttons",
"foundation/components/clearing",
"foundation/components/dropdown",
"foundation/components/dropdown-buttons",
"foundation/components/flex-video",
"foundation/components/forms",
"foundation/components/grid",
"foundation/components/inline-lists",
"foundation/components/joyride",
"foundation/components/keystrokes",
"foundation/components/labels",
"foundation/components/magellan",
"foundation/components/orbit",
"foundation/components/pagination",
"foundation/components/panels",
"foundation/components/pricing-tables",
"foundation/components/progress-bars",
"foundation/components/reveal",
"foundation/components/side-nav",
"foundation/components/split-buttons",
"foundation/components/sub-nav",
"foundation/components/switch",
"foundation/components/tables",
"foundation/components/tabs",
"foundation/components/thumbs",
"foundation/components/tooltips",
"foundation/components/offcanvas",
"foundation/components/visibility";

Paul commented on Paul's post over 4 years

Ah ok. I suppose to could pick and choose by component as you suggest. I knew with JS I could, didn't think about the same for the css.

It would be nice if in _config.cscc there could be a component flag/toggle. Nice having everything in one place, though grouped by component blocks. Then compass just generates selected & custom css props.

Thanks for your reply,
Paul

Posts Followed

No Content

Following

    No Content

Followers

My Posts



My Comments

You commented on Paul's post over 4 years

Not sure if it's needed with "modern browsers." Probably. Anyway I found a reference to including it via sass precompilation:

https://github.com/zurb/foundation/issues/3187

Hope this helps someone else with the same concern since it wasn't very apparent in the getting started docs :p

You commented on Paul's post over 4 years

Also, if generating components via .scss you can also comment out import lines in foundation.scss

here is where each is brought in:

// Make sure the charset is set appropriately
@charset "UTF-8";

// Behold, here are all the Foundation components.
@import
"foundation/components/accordion",
"foundation/components/alert-boxes",
"foundation/components/block-grid",
"foundation/components/breadcrumbs",
"foundation/components/button-groups",
"foundation/components/buttons",
"foundation/components/clearing",
"foundation/components/dropdown",
"foundation/components/dropdown-buttons",
"foundation/components/flex-video",
"foundation/components/forms",
"foundation/components/grid",
"foundation/components/inline-lists",
"foundation/components/joyride",
"foundation/components/keystrokes",
"foundation/components/labels",
"foundation/components/magellan",
"foundation/components/orbit",
"foundation/components/pagination",
"foundation/components/panels",
"foundation/components/pricing-tables",
"foundation/components/progress-bars",
"foundation/components/reveal",
"foundation/components/side-nav",
"foundation/components/split-buttons",
"foundation/components/sub-nav",
"foundation/components/switch",
"foundation/components/tables",
"foundation/components/tabs",
"foundation/components/thumbs",
"foundation/components/tooltips",
"foundation/components/offcanvas",
"foundation/components/visibility";

You commented on Paul's post over 4 years

Ah ok. I suppose to could pick and choose by component as you suggest. I knew with JS I could, didn't think about the same for the css.

It would be nice if in _config.cscc there could be a component flag/toggle. Nice having everything in one place, though grouped by component blocks. Then compass just generates selected & custom css props.

Thanks for your reply,
Paul

Posts Followed

No Content

Following

  • No Content

Followers

  • No Content