Button + card + status
Small pieces stay reusable and predictable.
FG UI is intentionally simple to integrate. Copy the local assets, load the stylesheet and JavaScript, add the fgui class to your page wrapper, then use components.
Use the normal documentation for stable integration guidance, and see What’s new in 1.2 for the 64 additive families and new theme/reader namespaces.
Every layout, component, interaction, icon and interface pattern on this website is powered by FG UI itself. No Bootstrap, Tailwind or external UI framework is used.
You do not need to understand frameworks, package managers or build tools. The beginner guide explains folders, HTML, CSS and FG UI in plain English, then walks through a real page from start to finish.
The stable package does not require a build tool, package manager or external framework.
<link rel="stylesheet" href="assets/css/fgui.css?v=1.2.0">
<body class="fgui">
<button class="fgui-btn fgui-btn--primary">
Save changes
</button>
<script src="assets/js/fgui.js?v=1.2.0"></script>
</body>fgui wrapper.FG UI scopes its interface system through the FG UI wrapper so component typography and box sizing are applied consistently.
Complete stylesheet, tokens, layout primitives and all component styling.
Interactive components and the public JavaScript API.
Local SVG sprite containing the 800 stable icon IDs.
Six local WOFF2 subsets used by the default FG UI font stack.
The Basic layer contains reusable primitives. The Combined layer composes those primitives into larger product patterns.
Small pieces stay reusable and predictable.
Use larger patterns when you need complete application or website sections quickly.
<svg class="fgui-icon" aria-hidden="true">
<use href="assets/icons/fgui-icons.svg?v=1.2.0#fgui-icon-search"></use>
</svg>The icon sprite is local, so the interface does not wait for a third-party icon network request.
FG UI exposes a deliberately small public API for integration and dynamic content.
Initialise supported interactions inside a root.
Open a supported controlled surface.
Close a supported controlled surface.
Toggle supported component state.
Trigger FG UI toast feedback.
Work with the local icon system.
Configure supported runtime options.
Read the current FG UI locale state.
Resolve runtime localisation strings.
Prefer existing tokens, utilities and components before adding project-specific styling.
Use Basic components to build unique screens and Combined patterns to accelerate common product structures.
The stable package is designed so your interface can run without a CDN or external UI service.
All 457 Stable families, root classes, release status, hooks, modifiers and accessibility attributes.
Core expectations, advanced controls, automated gates and manual release checks.
Supported browsers, modern platform features and fallback policy.
Stable release and compatibility policy for future updates.
Move from setup into the visual component showcase, then review the testing and stability work behind the release.