The content and structure
HTML says what is on the page: headings, paragraphs, buttons, forms, menus and sections.
<button>Save</button>This guide starts at the beginning. Learn what the files are, where they go and how to build a real FG UI page without technical jargon.
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.
For a basic FG UI website, you mainly need one HTML file plus the FG UI assets folder. You can learn the deeper web-development concepts as you go.
HTML says what is on the page: headings, paragraphs, buttons, forms, menus and sections.
<button>Save</button>CSS controls the design. FG UI gives you the CSS, so you do not have to style every control yourself.
fgui-btn--primaryJavaScript adds behaviour such as opening a modal, changing a carousel slide or showing a toast message.
assets/js/fgui.jsFollow these steps in order. You can start with a completely blank folder.
Inside it, create a file called index.html.
Keep the folder structure intact so the files can find one another.
class="fgui" to the bodyAdd your own CSS after FG UI and override the primary token.
A lot of people want their buttons and highlights to match their own logo or brand. FG UI makes that simple.
The same working controls are shown in both cards. Try the button and toggle the option, then compare how the brand colour changes.
Same FG UI components. No new component CSS. The colour tokens are simply different.
For your first site, this is all you need to understand. You can learn about the extra hover and soft colour tokens later.
<style>
.fgui {
--fgui-primary: #790fcc;
}
</style>Put this after the line that loads fgui.css. Do not open FG UI's main CSS file and change it directly.
This is not a screenshot. It is a real interface running inside this page.
This hero is already responsive and uses FG UI's typography, spacing, borders, buttons and design tokens.
Use ready-made components instead of designing every box from scratch.
Components are designed to adapt down to narrow screens.
Buttons, forms, cards and larger patterns share the same visual language.
Add your own words, images and links, then keep composing FG UI components.
Save this as index.html beside the FG UI assets folder.
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>My Website</title>
<link rel="stylesheet" href="assets/css/fgui.css?v=1.2.0">
<style>
.fgui {
--fgui-primary: #790fcc;
}
</style>
</head>
<body class="fgui">
<main class="fgui-container fgui-stack fgui-stack--lg">
<section class="fgui-marketing-hero">
<div>
<div class="fgui-eyebrow">Welcome</div>
<h1>My first FG UI website</h1>
<p class="fgui-lead">Change this text to your own.</p>
<button class="fgui-btn fgui-btn--primary">Get started</button>
</div>
<div class="fgui-marketing-hero__visual">
<div class="fgui-marketing-hero__visual-mark">FG</div>
</div>
</section>
</main>
<script src="assets/js/fgui.js?v=1.2.0"></script>
</body>
</html>Browse the component showcase, then use the full documentation when you want to go deeper.