Foundation, the responsive front-end framework from ZURB, has stopped getting new features. Version 6.9.0 is its final planned feature release, according to the project’s own GitHub announcement of September 2026.
Version 6 still gets bug fixes. The next major version arrives as Yeti, a CSS-first rewrite that needs no Sass and no build step.
What Is Foundation?
ZURB, a product design company, built Foundation from the global CSS and jQuery plugins it already used on client projects, along with its style guide. The goal was faster prototyping.
What came out was a grid and a set of ready-made UI components, with optional JavaScript plugins on top, all written in HTML, CSS, Sass and JavaScript.
It’s released under the MIT License, so anyone can use or fork it for any purpose. The one limit is that you can’t sell Foundation itself.
The first release came in September 2011. The latest stable release, as of November 2026, is 6.9.0, published 27 September 2024. For a sense of size, version 6.0 launched at 60 KB of CSS and 84 KB of JavaScript (ZURB, November 2015).
Who maintains it depends on which source you read. The official FAQ still names ZURB, with four people on the core framework. Wikipedia says volunteers have looked after Foundation since 2019.
The FAQ page has no date on it, so I’d trust the 2019 reference more. Then in September 2026 an announcement brought up a successor called Yeti.
Foundation for Sites, Foundation for Emails and Foundation for Apps
The Foundation name covers more than the website framework.
Foundation for Sites is the one people mean by default. It builds responsive websites, and marketing sites and e-commerce stores are the usual projects, with portfolios showing up too.
Foundation for Emails produces responsive email templates on table-based layouts that work in clients like Outlook and Gmail. Inky, an HTML-like templating language, is its companion.
Foundation for Apps targets more complex web apps. Angular handles stateful transitions, and there’s a full-screen grid.
Unless a section says otherwise, the rest of this covers Foundation for Sites.
How Does the Foundation Grid Work?
A container gets split into 12 columns by default, and each cell picks up its width per breakpoint through size classes such as small-6 or large-4.
Layouts start at the small breakpoint and scale up, so a class set at small carries to every larger screen unless you override it.
The XY grid documentation puts the default gutter between cells at 20px on the small breakpoint and 30px at medium.
Float, Flex and XY grids
Foundation 6 includes the older float and flex grids alongside the newer XY grid, and the XY grid is the default.
| Grid | Built on | How to switch to it | Docs label |
|---|---|---|---|
| Float grid | CSS floats | Set $xy-grid and $global-flexbox to false | Legacy |
| Flex grid | Flexbox | Set $xy-grid to false | Legacy |
| XY grid | Flexbox | Default in foundation.css | New |
More Flexbox integration arrived in Foundation 6.2, and 6.9.0 still uses the XY grid as its default layout system.
What the XY grid adds
The XY grid handles horizontal and vertical alignment, and it can size cells automatically. It also has a full vertical grid.
Gutters collapse at the breakpoints you choose, and block grids come from classes like small-up-2 or large-up-6.
The docs describe these as features only possible with Flexbox.
Where grid choice goes wrong
Pick one grid per build.
The Sass docs treat foundation-xy-grid-classes, foundation-grid and foundation-flex-grid as mutually exclusive options, so including more than one is a mistake. Block grid classes also do not work on vertical grids.
Native CSS Grid is a different thing. Foundation’s grid classes don’t use it, so anything that needs track-based placement gets its own CSS.
Which Components and JavaScript Plugins Come With Foundation?
Foundation ships CSS components for forms, navigation, containers and media, with JavaScript plugins that add behavior to them. The documentation splits them into styled components and a plugin layer.
Container components include Accordion, Dropdown, Off-canvas, Reveal (the modal), Tabs and Responsive Accordion Tabs. Navigation has Dropdown Menu, Drilldown Menu, Accordion Menu and Magellan.
Orbit is the carousel, and Tooltip does what its name says. Abide validates forms. Equalizer, Interchange, Toggler, Smooth Scroll and Sticky cover page behavior, and Slider sits in a category of its own as a control.
How the jQuery dependency works
Every plugin runs on jQuery. The docs say jQuery must be imported before Foundation, and they name no required jQuery version.
Calling $(document).foundation() starts every plugin on the page, while calling .foundation() on one element starts only that part. Data attributes such as data-accordion attach a plugin to markup, and every plugin file expects foundation.core to be loaded first.
Anything added to the page after load stays inert until you call .foundation() on it. This is the usual trap with modals and tab sets built from fetched HTML.
Motion UI and accessibility
Transitions and animation come from Motion UI, a separate Sass library that the docs list among Foundation’s libraries. Plugins like Reveal and Toggler can draw on it.
Each plugin carries its own accessibility support, which means the plugin page is where keyboard and ARIA behavior gets documented. Restructure a plugin’s markup and you should retest focus order and screen reader output before shipping.
How Does Sass Customization Work in Foundation?
You customize Foundation through a Sass settings file, and you don’t need to override compiled CSS. Variables in that file are declared with !default, so any value you set before the import replaces the framework default.
Settings file and mixins
Start by copying _settings.scss into your project and importing it before foundation. The file has to import util/util, and npm users may need to point that path at node_modules/foundation-sites/scss/util/util.
Examples of what you can change include $button-background and $button-radius, plus the $button-sizes map.
Every component has an export mixin. @include foundation-everything pulls in all of them, while including only the components you use shrinks the output.
The catch is that settings don’t update on their own when Foundation changes. A custom settings file drifts unless you keep an eye on the release notes.
Pre-compiled CSS or a Sass build
The npm package ships minified and unminified CSS in dist/css, so you can skip compiling entirely. The cost is that you skip variable changes too.
A Sass build gets you custom variables and trimmed output, in exchange for a compiler in your toolchain.
Pre-compiled CSS is fine for a small site with default styling. For anything branded, use the Sass build.
Compiler requirements in 6.9
Foundation 6.9 requires Node 18 or newer and uses Dart Sass only.
The Sass documentation page says otherwise. As retrieved in November 2026, it still recommends Ruby Sass 3.4+ or node-sass 3.4.2+ and never mentions Dart Sass.
Treat the 6.9.0 release notes as the current word and the docs page as stale on this point. Users in the project’s GitHub discussions still report node dependency issues, so pin your Node version before debugging anything else.
How to Install Foundation
You can install Foundation through npm or Yarn, or start from a CLI starter template. A plain download works too, as does a jsDelivr CDN link or a hand-written HTML starter file. The official installation page documents all of them.
Which one you pick mostly comes down to whether you want to compile Sass.
| Route | What you get | What it needs |
|---|---|---|
| CDN (jsDelivr) | Compressed CSS and JS, pinned to a version | jQuery loaded first |
| Download zip | Compiled CSS and JS plus a starter index.html | Nothing to compile |
| npm or Yarn package | Source Sass and JS plus compiled files | Your own build setup |
| Basic template | Sass compilation and a starter HTML file | Yarn |
| Experienced (ZURB) template | Panini, webpack, BrowserSync, asset compression | Yarn |
The docs mark the basic template as the one recommended for beginners. On the CDN side, separate builds exist for the float grid and for right-to-left layouts, plus one for prototyping classes.
Set up the basic template
- Clone the starter template with
git clone https://github.com/foundation/foundation-sites-template basic-project. - Move into the folder with
cd basic-project. - Run
yarn installto pull in the dependencies. - Start the dev build with
yarn start. - Edit the starter HTML file and the Sass files it compiles.
That’s the whole setup, since the template already bundles Sass compilation.
Where setup breaks
The installation docs name no Node.js version, even though the 6.9.0 release notes set a minimum.
Windows users get an odder instruction. The docs still tell them to point node-gyp at Python 2.7 through windows-build-tools. A Dart Sass-only build has no native compile step, so that workaround reads like a leftover from the node-sass era.
Bundlers send mixed signals too. The JavaScript docs recommend Grunt or Gulp for combining files, while the installation page lists webpack for the ZURB template and never mentions Gulp. Follow whichever template you actually cloned.
Manual setups mostly come down to script order. The HTML starter loads jQuery, what-input and Foundation in that order, calls $(document).foundation(), and puts a no-js class on the html tag.
Is Foundation Still Maintained in 2026?
Yes, but only for fixes. Version 6 still gets bug fixes and no new features, since 6.9.0 was the final planned feature release.
What happens to Foundation for Sites 6
Version 6 moves to a v6 branch, and that branch keeps receiving bug fixes. The foundation-sites package on npm keeps publishing 6.x from it.
The repository itself has been renamed from foundation-sites to yeti. GitHub redirects the old URL and git remotes, and stars, forks, issues and history carry over. Open issues and pull requests against 6.x get retargeted to the v6 branch.
For teams that need stability, the announcement’s own advice is to stay on version 6. The develop branch is now Yeti 7 and stays unstable until beta, so don’t build anything on it yet.
What Yeti changes
Calling Yeti a port of Foundation would be wrong. It’s a reimagined framework that drops most of the tooling Foundation 6 is built on.
It needs neither Sass nor a build step, and it ships no polyfills. It targets Baseline 2025 browsers. Layouts are named, and type and spacing draw from one token scale. Dark mode and theming come built in.
The license changes too. Yeti uses the Functional Source License 1.1 with an MIT future license, so each release converts to MIT two years after it ships. The one reserved use is offering Yeti itself as a competing product.
Foundation for Sites 6 stays MIT.
Where the sources disagree on Yeti
Wikipedia’s article still says the team expected Foundation for Sites 7 to drop older browsers and adopt Flexbox or a calculated grid. The 2026 announcement describes a rewrite under a new name instead.
Status is split as well. One snapshot of the main repository’s README says Yeti is in alpha with class names still open to change, while another copy says 7.0.0-beta with class names frozen.
The release record settles it, at least for now. GitHub and npm list only two Yeti releases, 7.0.0-alpha.1 and 7.0.0-alpha.2, both published on 4 November 2026, and no beta. The announcement says Yeti moves to the yeti-css package name on npm when it reaches beta, so treat Yeti as alpha today. Check the status line in the repository before committing a project to either label.
Foundation for Emails
Foundation for Emails lives in its own repository and moves on its own schedule.
npm lists version 2.5.1, and registry metadata shows it last updated on 12 March 2026. The repository README says maintenance updates continue while new feature development happens in Inky v2.
The Yeti announcement doesn’t describe Emails at all, though it names Inky as part of Foundation’s home. For email templates, Inky is the project to follow, not Yeti.
Foundation vs Bootstrap, Bulma and Tailwind CSS: Which Should You Choose?
For a new project, pick Bootstrap or Tailwind CSS. Keep Foundation for an existing version 6 codebase or for email templates.
| Framework | Style approach | JavaScript | Status in November 2026 |
|---|---|---|---|
| Foundation 6 | Components plus XY grid | jQuery plugins | Bug fixes only, successor in alpha |
| Bootstrap 5 | Components plus grid | Vanilla JS | Version 6 alpha out |
| Bulma 1.x | Flexbox-based components | None, CSS only | Dart Sass rewrite |
| Tailwind CSS 4 | Utility classes | None | CSS-first configuration |
Version 5 stays the stable Bootstrap choice for now, since the first Bootstrap 6 alpha only appeared on 8 October 2026. Bulma 1.0 was a full rewrite on Dart Sass that moved colors to CSS variables, and Tailwind v4 moved configuration from a JavaScript file into CSS.
jQuery is where these frameworks split most clearly. Bootstrap 5 dropped it and saved 85 KB of minified JavaScript (InfoQ, 2020). Foundation’s docs, on the other hand, still require jQuery to be imported before Foundation. Of everything above, that’s the part I’d worry about most.
Which framework fits which project
For component-first sites with a big ecosystem behind them, Bootstrap 5 is the safe choice. Custom designs built from utility classes point to Tailwind CSS 4, and Bulma fits when you want CSS only, with no JavaScript shipped.
A Foundation 6 site that already works should stay put. Responsive email templates are the other exception, since Foundation for Emails still fits there, with Inky as the path forward.
Pros and cons of Foundation
The good side is mostly control. Sass gives you fine-grained say over the output through per-component imports, and the 6.x line is stable and still gets fixes. The plugin set is mature, and the MIT license on version 6 is a plus as well.
The bad side is easy to list. Plugins are bound to jQuery and nothing new is coming after 6.9.0. The successor isn’t stable yet either, and the community is far smaller than Bootstrap’s.
When Foundation is the wrong fit
Foundation 6 is the wrong pick when the project needs features that don’t exist yet.
A new build that expects feature releases is the obvious case, since the last planned one has shipped. A codebase that is removing jQuery has little reason to adopt a framework built on it. And a team that wants Yeti today will find it still in alpha, with class names that can change until beta.
Teams that rely on a deep pool of examples and answers should look elsewhere too, because Bootstrap has a far larger community.
None of that justifies migrating a site that works. The announcement says nothing breaks for Foundation for Sites 6 users, so the cheapest path for a working site is usually no path at all.
Foundation FAQ
Can you use only the grid without the rest of the framework?
Yes. The download page lets you uncheck all components and keep only the grid, and a Sass build can include just the grid mixin.
The output then carries no component CSS.
Does Foundation work with Drupal, WordPress and Rails?
Yes. Sources describe it running with Drupal and WordPress, and with .NET back ends too. A Foundation Rails gem installs by adding one line to the Rails Gemfile.
Which browsers does Foundation 6 support?
The XY grid documentation lists Chrome, Firefox, Safari 6+, IE11, iOS 7+ and Android 4.4+. That list dates from the version 6 era, so check it against the browsers your audience actually uses.
Older Internet Explorer versions aren’t covered.
Is Foundation a good choice for beginners?
Manageable, if you already know HTML and CSS. The docs mark the basic template as the beginner route, and the CDN link skips Sass tooling entirely.
Version 6 is feature-frozen at 6.9.0, which matters if you plan to build skills around it for years.
What to Do With an Existing Foundation 6 Site
I’d stay on version 6 and tie any move to a dated trigger, not to the Yeti announcement.
As of 12 November 2026, Yeti 7 and Bootstrap 6 are both pre-release, so a migration started today targets an API that is still moving.
Start by isolating the jQuery-dependent plugins, then pin your Node and Dart Sass versions. Prototype in Yeti only after a stable 7.0.0 exists.
jQuery goes first because removing it lowers the cost of a later move toward Bootstrap 5, which ships without jQuery.
Staying means living with a feature-frozen framework and plugin code tied to jQuery. That’s the price, and it holds until Yeti publishes a stable release. That release is the event that would change this advice.
- How to Apply NARS Foundation Like a Pro - November 10, 2026
- How to Do Makeup for a Wedding That Lasts - November 8, 2026
- How to Store Makeup to Keep It Fresh - November 7, 2026