Repository navigation
Releases
Yeti 7.0.0-alpha.2
Yeti 7.0.0-alpha.2 fixes two accessibility bugs and adds two layouts. If you're on alpha.1, update: a theme that set a motion token was overriding a reader's reduced-motion setting.
npm install @foundation/yeti@next<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@foundation/yeti@7.0.0-alpha.2/dist/yeti.min.css">Most of this release came from building a real restaurant site on alpha.1 and writing down everything that got in the way.
Accessibility fixes
- Reduced motion now always wins. Setting a motion token anywhere, even on
:root, used to beat the reader's setting, so animations ran at full length for people who had asked for less. You can still set those tokens, and you no longer need to wrap them in@media (prefers-reduced-motion: no-preference). - A surface now sets its text. A box with
data-surfacepainted its fill but kept the text color from around it, which gave dark words on a dark band in a forced color scheme. A band that stays dark is now one declaration:
<section class="box band" data-surface="base">…</section>.band { color-scheme: dark; }New layouts
leaders joins a name and a value with a dotted line, for menus, price lists, opening hours and contents pages. A long name wraps with the dots and the value on its last line, and anything after the value sits below at full width. data-row makes one element a single row, and --yeti-leaders-line sets the line.
<dl class="leaders">
<div><dt>Soup of the day</dt><dd>$9</dd></div>
<div><dt>Roast chicken with lemon and thyme</dt><dd>$24</dd></div>
</dl>divider sets a heading or short line beside a rule, for section heads, dates and an "or" between choices. data-align moves the text, and --yeti-divider-line sets the rule.
<h2 class="divider">Mains</h2>Other fixes and additions
shellandmasonrykeep their gap on a child that has a layout class of its own.- A nav bar's open panel has its own text token,
--yeti-nav-panel-text. Before, a dark--yeti-nav-panelleft dark links on it, with no token to fix them. billboardfills its container instead of stopping at the reading width.- A sticky nav sits at the top edge.
data-nowrapworks on any element, not only on a table and its cells.
What may change on your site
- Gaps in a
shell: a part with a layout class used its own gap above it, and now uses the shell's. Aboxfooter or astackonmainmay move, sometimes by a lot. Set the space you want withdata-gapon the shell. - A sticky nav no longer reads
--yeti-sticky-offset. A bar that should float below the edge now setsinset-block-start. The token still sets where everything else sticks. --yeti-color-textset on.navno longer reaches the open panel. Use--yeti-nav-panel-text.- Text color set around a surface box no longer reaches inside it. The box sets the page text.
data-paintanddata-texton the box itself still apply.
Docs
- New guidance on restyling a component, including how a site's own cascade layers order against Yeti's.
- The nav docs explain painted bars, and the masonry docs say what to use when reading order matters.
- The install guide covers two Vite issues: set
build: { cssTarget: 'esnext' }so it leaveslight-dark()alone, and copyLICENSEinto your build, because the minifier drops Yeti's banner when you use a CSS@import. - The docs now say the validator checks Yeti's vocabulary, not HTML itself.
What alpha means
Class names, attributes and tokens can still change. They freeze at the first beta, and the stability page lists exactly what will be frozen.
Yeti now has 19 layouts, 3 recipes, 22 components, 7 utilities and 307 public tokens, at about 20 KB of CSS and 4 KB of JavaScript, minified and gzipped. Bugs and proposals go to Issues, and questions go to Discussions.
Yeti 7.0.0-alpha.1
This is the first release of Yeti, the successor to Foundation for Sites. It is an alpha, published on npm as @foundation/yeti. If you use Foundation 6, nothing changes for you: foundation-sites is a separate package and stays at 6.9.0.
Foundation was built for a web where CSS could not do layout on its own. That web is gone. Yeti starts again on what browsers do natively now, and it is one stylesheet:
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@foundation/yeti@7.0.0-alpha.1/dist/yeti.min.css">What Yeti is
- Native first. HTML, then CSS, then JavaScript.
dialogandpopoverare real HTML, container queries, cascade layers,light-dark()and anchor positioning do the work Sass and scripts used to do, and JavaScript only adds to what already works. - No build, ever. No Sass, no Node and no bundler required. A build of your own works too, and you can leave out the parts you don't use.
- Named layouts, not utility classes.
stack,cluster,sidebarandgridsay what they do, and a few data attributes configure them. - One system of tokens. Type and space come from one base and one ratio, and color comes from a handful of hues. Change a value and the system recomputes in the browser.
- Light and dark built in. A page follows the reader's setting with nothing to switch on.
- Accessible by default. Focus handling, ARIA and color contrast are tested on every change.
- Readable by agents. A manifest describes every component. The docs,
llms.txtand editor completion are generated from it, and a validator checks your built pages against it. Every built stylesheet links thellms.txtfor its exact version.
What's in this release
- 17 layouts, 3 recipes, 22 components and 7 utilities
- 304 public tokens and 2 example themes
- 10 optional JavaScript modules, because every component works with no script
- A starter page and theme to copy
- About 20 KB of CSS and 4 KB of JavaScript, minified and gzipped
Install
With npm:
npm install @foundation/yeti@nextWithout Node, download the zip below, or follow the install guide to copy the files into your project.
Yeti targets Baseline 2025 browsers. There are no polyfills, so if you need older browsers, Yeti is probably not your tool yet.
What alpha means
Build something with it and tell us what breaks, but don't ship it to a client yet. Class names, attributes and tokens can still change. They freeze at the first beta, and the stability page lists exactly what will be frozen.
If you use Foundation 6
- Nothing breaks.
foundation-siteson npm is a separate package and keeps publishing 6.x from thev6branch, which continues with bug fixes. - Yeti is not Foundation 6 with new names, so there is no automatic upgrade. The migration guide maps the grid and every version 6 component to its Yeti replacement.
- The announcement has the full story. The package is
@foundation/yeti, not theyeti-cssit first mentioned.
License
Yeti is released under the Functional Source License 1.1, MIT future license (FSL-1.1-MIT). Use it freely in your own sites and products. The one thing it reserves is offering Yeti itself as a competing product. Each release becomes plain MIT two years after it ships. Foundation for Sites 6 remains MIT.
Tell us what you find
Questions go to Discussions, and bugs and proposals go to Issues. The docs cover every component with live examples.
Foundation v6.9.0 Release
Foundation 6.9 is here! This release does a lot more clean up work for improving the Sass. Thank you to everyone that help chip in and stay on top of things to get this release out the door. I am honored that so many of you choose to use Foundation. It's been a lot of fun meeting and chatting with so many of you on the Discord server.
Speaking of the Discord server, that is currently the best place to chat about Foundation. After the war with spam on the Github issues and discussion boards, I had to lock those down. If you are not on the Discord server, here is an invitation link.
Notes on Dart Sass 2.0
There is more work to do on the Sass side of things in order to get ready for the Dart Sass 2.0 release. Since Foundation is one of the largest Sass projects on the web, the Sass team reached out to me about migrating from @include to @use . I delayed this release in hopes of getting that done. It turns out that change was not so simple. It really does change some core fundamental aspects of the SCSS architecture. Therefore, it will need to be moved to the F7 release. The Sass team has been amazing to work with though. They were gracious enough to submit a couple of PRs my way in order to seed the process.
OK, now let's check out the details of this release...
Updated Requirements
Foundation 6.9 requires Node 18+. It only uses DartSass.
Featured Enhancements
- 🚀 Faster Builds with
sass-embedded. All supporting Foundation repositories have also been updated to use Dart Sass andsass-embedded. - 🚀 Your eyes will be saved from all of those Sass deprecation warnings! 👀
Bug Fixes
- 🐛 Fix for deep linking with Tabs
- 🐛 Abide will no longer add aria-describedby to hidden inputs
- 🐛 Fixed missing return type for SmoothScroll Typescript
- 🐛 Improved focus styles and behavior for switch
- 🐛 Abide will now clear existing errors on an input when re-validating
- 🐛 Fixed many sass deprecation warnings
Contributors
Thanks to the 21 amazing people who contributed code or documentation to the 6.9 release. Foundation wouldn't happen without you!
v6.8.1
Join us on our Discussions Board. This is a great place to ask questions and interact with your fellow Foundation users.
What's Changed
A small issue with the build was found after 6.8.0 was released. While it will most likely not affect anyone else, I figured that it would be nice to just ship the fix out just in case anyone was running a build directly inside of the repo.
Full Changelog: v6.8.0...v6.8.1
v6.8.0
Join us on our Discussions Board. This is a great place to ask questions and interact with your fellow Foundation users.
What's Changed
Rejoice! Foundation now works with node 16, 18 and 20! The minimum version of node that is required is now v16. A lot of packages and dependencies needed to be upgrade in order to make this happen.
Full Changelog: v6.7.5...v6.8.0
Foundation for Sites v6.7.5
Join us on our Discussions Board. This is a great place to ask questions and interact with your fellow Foundation users.
What's Changed
- fix: removing the 'invisible' class from parent list when utilizing by @pebutler3 in #12322
- Fix wrong markup in the typography base file by @tpoisot in #12338
- docs: fix typo in CONTRIBUTING.md by @Priestch in #12439
- Remplace color-adjust with the new print-color-adjust syntax by @mrleblanc101 in #12442
- build(deps): bump nanoid from 3.1.30 to 3.3.4 by @dependabot in #12430
- fix: typo in $-zf-bp-value name by @javierm in #12420
- build(deps): bump minimist from 1.2.5 to 1.2.6 by @dependabot in #12417
- docs: fixed bad code block in motion-ui page by @htemele in #12388
- build(deps): bump follow-redirects from 1.14.5 to 1.14.8 by @dependabot in #12387
- build(deps-dev): bump node-sass from 6.0.1 to 7.0.0 by @dependabot in #12386
- Documentation: Fix options name for "In-Canvas to Off-Canvas" code example by @alamowo in #12376
- Bug #12070: make _button-group.scss compatible with libsass 3.6.3 by @tjdub in #12419
- fix(abide): add aria-describedby to the input only if error is visible by @ahukkanen in #12398
- FIX difference in behaviour between mouse & keyboard interactions on Sliders by @rickcurran in #12378
- FIX SASS color interpolation warning #12333 by @thomasfrobieter in #12370
New Contributors
- @tpoisot made their first contribution in #12338
- @Priestch made their first contribution in #12439
- @mrleblanc101 made their first contribution in #12442
- @javierm made their first contribution in #12420
- @htemele made their first contribution in #12388
- @tjdub made their first contribution in #12419
- @rickcurran made their first contribution in #12378
- @thomasfrobieter made their first contribution in #12370
Full Changelog: v6.7.4...v6.7.5
Foundation for Sites v6.7.4
Join us on our Discussions Board. This is a great place to ask questions and interact with your fellow Foundation users.
Check out the details of this release below:
Featured Enhancements
- 🚀 Outlines on focus will be removed when
what-intentdetects you are using a mouse of touch. - 🚀 When an element is set to
draggable=false, callouts and force touch on iOS are also suppressed. - 🚀 New Visibility classes for dark mode, IE10+, and sticky
show-for-dark-modehide-for-dark-modeshow-for-iehide-for-ieshow-for-stickyhide-for-sticky
- 🚀 Slider now uses grab based cursors for the handle
Bug Fixes
- 🐛 No more ESLint and SassLint errors when you run a build!
- 🐛 Many dependencies updated to keep up with that dep train
- 🐛 Fixed the customizer build
- 🐛 Fixed numerous bad links on the documentation site.
- 🐛 Match height on Tabs now uses
min-height - 🐛 Fix for Accordion Menu carets not always able to be sized via sass vars
- 🐛 Removed several instance of console.log
- 🐛 The
changed.zf.mediaqueryevent is back! When the browser has been resized and crosses a defined breakpoint, this event will be triggered. You can always access the current named breakpoint viaFoundation.MediaQuery.current - 🐛 Added momentum scrolling support for Reveal, Off Canvas and Overflow prototype classes
- 🐛 Slider no longer emits
moved.zf.sliderandchanged.zf.sliderevents on init
Contributors
Thanks to those who contributed code or documentation to the 6.7.4 release. Foundation wouldn't happen without you!
Foundation v6.7.3 Release
Join us on our new Discussions Board. This is a great place to ask questions and interact with your fellow Foundation users.
Check out the details of this release below:
Featured Enhancements
- 🚀 New $
unit-warningssetting. This can allow you to suppress warnings when non-numerical values are passed to the rem-calc() method. This can be beneficial when passing CSS custom props as values instead of actual unit based values.
Bug Fixes
- 🐛 Fix null color errors with some Sass build setups
Contributors
Thanks to those who contributed code or documentation to the 6.7.2 release. Foundation wouldn't happen without you!
Foundation 6.7.2
Join us on our new Discussions Board. This is a great place to ask questions and interact with your fellow Foundation users.
Check out the details of this release below:
Featured Enhancements
- 🚀 New
$body-safe-paddingsetting. This will add safe padding to the body. This can be good if you want your site to be automatically padding in from the edge of non-rectangular displays such as phones with notches.
Contributors
Thanks to those who contributed code or documentation to the 6.7.2 release. Foundation wouldn't happen without you!
Foundation v6.7.1
Join us on our new Discussions Board. This is a great place to ask questions and interact with your fellow Foundation users.
Check out the details of this release below:
Featured Enhancements
- 🚀 Touch event are now passive when possible
- 🚀 safe padding added to body for non-rectangular displays
Bug Fixes
- 🐛 Puppeteer moved to dev dependencies
- 🐛 Fixed invalid HTML with meta tag added for media query access in JS
- 🐛 More doc fixes
Contributors
Thanks to those who contributed code or documentation to the 6.7.1 release. Foundation wouldn't happen without you!