Should you adopt Yeti now?
Use a pinned evaluation to decide whether Yeti's layout model fits your site. The supplied README describes a stylesheet that consumers can use without Sass, Node or a bundler. The installation guide, however, says Yeti has not been released and directs early testers to build from the repository. That distinction matters when choosing between trying the design system and making it a team dependency.
Our run on October 3, 2026, at commit 4577f24 installed successfully and built successfully, but the test command failed. Treat that result as a reason to investigate the snapshot before committing to it.
What our sandbox established
Installation succeeded in 7 seconds. The build succeeded in 6 seconds. Tests exited 1 after 9 seconds, without timing out. The build log reports that it wrote dist/; it does not demonstrate that we deployed a site or exercised its components in a browser.
The named failure was the check that every guide under docs/ is a fresh render of its source. It attempted to read /work/repo/docs/guides/markup.md and received ENOENT. The supplied tail does not establish whether generating documentation, restoring a file or changing the test reference would resolve it. It also does not establish that browser or screenshot suites completed.
The attached aggregate test-count field is null. The raw tools-suite footer contains its own counts, but those are not an exhaustive count of unique tests across the repository. We therefore make no aggregate passing-test claim.
Our harness records each command's outcome, exit code, elapsed time and timeout status, with a log tail for context. The MrKeyoor testing methodology explains this approach and its limits. That page was supplied in its November 1, 2026 form; it is background on provenance, not proof that the October run used every detail of today's procedure.
What you get from the stylesheet
Yeti uses named layout primitives configured through classes and data attributes. Its README describes container queries, cascade layers and native nesting as parts of the implementation. A shared token scale controls typography and spacing.
The installation guide distinguishes the base stylesheet from optional component modules. Modules add behavior such as tab focus movement, dialog focus return and form validation messages. Those are documented capabilities, not browser behaviors verified by our run. The README's accessibility claims likewise remain maintainer claims here.
The same guide describes editor completion data and generated manifest documentation. It also gives a practical limitation: editor formats cannot restrict an attribute suggestion to the component class that accepts it. Authors still need to check whether an attribute belongs on a particular element.
Check release status before following package examples
The supplied README labels Yeti 7.0.0-beta, while our recorded build log identifies yeti-css@7.0.0-alpha.0. The installation guide says no release, npm package or download is available yet, and explicitly says its later instructions describe how installation will work after release. These sources do not provide one consistent release state.
The stability guide promises that specified public names are frozen from 7.0.0-beta.0. It also says token defaults, generated-file internals, test fixtures and browser minimums may still change. A promise about public names does not resolve artifact availability or the failure observed in our sandbox.
Before adopting, confirm which artifact and version you will consume, reproduce the guide failure at the pinned commit, and evaluate the components your own pages require in your supported browsers.
Browser and license requirements can rule it out
Yeti targets Baseline 2025 and provides no polyfills for older browsers. Check that floor against your actual browser requirements before spending time on a trial.
Yeti's README identifies its license as FSL-1.1-MIT. It permits use, modification and redistribution except for offering a competing product; each release becomes MIT two years after it ships. Foundation for Sites 6 remains MIT and continues on the v6 branch. Existing Foundation users should evaluate Yeti as a successor rather than assume the current branch is an ordinary version 6 update.
Alternatives answer different needs
Pico CSS offers semantic HTML styling, but its repository is archived and v2.1.1 is its final release. Consider it only if a fixed, unmaintained starting point is acceptable. It should not be recommended as an actively maintained escape from Yeti's release uncertainty.
Bootstrap provides compiled CSS and JavaScript, but its supplied default-branch README describes Bootstrap 6 development and points Bootstrap 5 users to v5-dev. Compare the version you intend to use rather than treating the default branch as a stable production release.
Tailwind CSS describes itself as a utility-first framework for custom interfaces. It is a replacement styling approach to consider when your team prefers utilities; the supplied extract does not establish build requirements, browser compatibility or ecosystem size.
These are choices for a site's styling foundation. The supplied evidence does not establish that combining them with Yeti would be useful or conflict-free.
How to read our ratings
Scores describe the supplied evidence for this evaluation, not adoption or popularity. The rubric is: 1 means a documented obstacle prevents the basic task; 2 means substantial readiness limits remain; 3 means basic setup works with unresolved friction; 4 means detailed guidance or established support routes are available, with specific caveats; 5 requires evidence of consistent readiness beyond this single run. Community measures available support and contribution routes, not user numbers or response quality.
Setup ease is 3 because installation and compilation succeeded, while early users still need a source build. Documentation is 4 because the supplied guides explain installation, optional modules, tooling and stability, despite conflicting release descriptions and the failed guide check. Community is 4 for the documented Discussions, issue templates and contribution route; responsiveness and Yeti-specific adoption remain unmeasured. Maturity is 2 because release descriptions conflict and our test command failed.

