Once UI Handbook
Vibe coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Getting started
What is Once UI?
Install & config
Page skeleton
Your first page
Upgrade from 1.8 to 2.0
Once UI without Next.js
Build and launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Common patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Forms that wire themselves
An icon rail that opens on hover
Maps without an API key
Segmented controls that slide
Design tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Border radius & nested corners
Bring your own icons
Give one section its own style
Override Once UI styles without !important
A logo before you have one
Agent resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles
Block updates
Block updates changelog
TrademarkTrademark
Ctrl k
Search…
Sign up
Once UI Handbook
Vibe coding
Introduction to vibe coding
Set up your local dev environment
Essential tools for vibe coding
Build your first Once UI app
Getting started
What is Once UI?
Install & config
Page skeleton
Your first page
Upgrade from 1.8 to 2.0
Once UI without Next.js
Build and launch
How to launch a portfolio site that actually gets you hired
How to build a documentation site with MDX and Next.js
How to ship a landing page and dashboard with authentication in Next.js
How to launch a social app with Next.js and Supabase
Common patterns
Hero section
Static panel
Form layout
Highlighted card
Responsive stacking
Decoration layers
Dialog & modal
Toast & feedback
Tables & lists
Loading states
App shell navigation
Dashboard & charts
Chat & messaging
Auth & verification
Settings & split panels
Data filters & toolbar
Command palette
Pricing & plans
Accordion & FAQ
Media & uploads
Empty & error states
SEO, Open Graph, and structured data
Documentation code blocks with live preview
Carousels, galleries, and before/after comparisons
Date pickers and scheduling
Context menus and dropdown actions
Tags, chips, and multi-value inputs
Roadmap & kanban
Form inputs & controls
Progress, status & badges
Scrolling & feeds
Profile, avatars & identity
Social proof & logo clouds
Masonry & media grids
Table pagination, search & bulk selection
Banners & announcements
Footer layouts
Onboarding & first run
Waitlist & coming soon
Forms that wire themselves
An icon rail that opens on hover
Maps without an API key
Segmented controls that slide
Design tips
Color & surfaces
Harness overview
Row, Column & Grid
Spacing & rhythm
Icons & buttons
Reveal & motion
Theme tokens, FOUC-free init, and runtime style controls
Tooltips and hover cards
Border radius & nested corners
Bring your own icons
Give one section its own style
Override Once UI styles without !important
A logo before you have one
Agent resources
Column, not Flex
Semantics over CSS
Typography scale
Common gotchas
Block anchors
Validate generated code
Pro block registry
Match task bundles
Block updates
Block updates changelog
TrademarkTrademark
Once UIDocumentationBlog
© Once UI. All rights reserved.
Built with Aveiro
Design Tips

A logo before you have one

How to give an app a clean mark before it has a designed logo with Logo's monogram prop, and how to turn a real SVG logo into a loading splash with LogoLoader.
Updated 3 days ago
Override Once UI styles without !important
3 min · Design tip · Logo
From @once-ui-system/core 2.7.0, an app with no logo yet gets a clean mark from its name, and a product with a real SVG logo gets a loading splash drawn from it.

The placeholder logo problem

Most new apps don't have a logo yet. So someone, often an AI agent, draws a quick SVG icon or a fake wordmark to fill the header, and nobody ever replaces it. It is the first thing people see and it looks like a placeholder, because it is one. Once UI 2.7.0 adds two things for this. monogram on Logo gives you a decent mark before you have a designed one, and LogoLoader turns the logo you do have into a loading splash.

A mark from the name

Pass monogram next to text and Logo draws a plain solid shape before the name.
import { Logo } from "@once-ui-system/core";

<Logo text="Acme" monogram href="/" />
The shape is one of five geometric marks, picked from a hash of text, so the same name always gets the same mark. It is filled with the strongest neutral text colour, so it is black in light mode and white in dark mode, with no tile behind it and no brand colour. That is on purpose: it reads like a favicon, not like a logo someone tried to design. If you'd rather show letters, pass a string. One or two characters read best.
<Logo text="Acme" monogram="A" href="/" />
A few rules worth knowing:
  • icon wins. Once you have a real icon file, set icon and monogram is ignored, so you can leave it in place while you wait for the design.
  • Beside text, the mark is decorative. It is hidden from screen readers, because the text already names the logo.
  • It is inline SVG. It renders on the server and adds no dependencies.
If you use an AI agent with Once UI, the agent docs now tell it to reach for monogram and never to draw its own icon or wordmark SVG.

A splash from your real logo

When you do have a logo, LogoLoader draws it as a loading state. Each letter and shape of the SVG is traced in turn, then the logo fills in and holds.
"use client";

import { useState } from "react";
import { LogoLoader } from "@once-ui-system/core";

export function Splash() {
  const [introDone, setIntroDone] = useState(false);

  return (
    <LogoLoader
      src="/trademarks/wordmark.svg"
      height={120}
      settled={introDone}
      onComplete={() => setIntroDone(true)}
    />
  );
}
Pass the file as a URL with src, which is fetched on the client, or as markup with svg to skip the request. Only the geometry is read from the file, so scripts, handlers and styles in the SVG never reach the page.
Prop
What it does
color
neutral by default, or brand, accent, inherit
order
Shows the filled logo with no intro
Fires once the intro has played
Because the logo is drawn in one colour, one file covers both themes. Use order="document" for a logo whose file lists the symbol last, so it lands after the letters. Set settled after the first play, as in the example. That way a remount, or a load that runs long, shows the finished logo instead of starting the strokes again. With reduced motion turned on, the tracing is skipped and the logo simply fades in. Keep LogoLoader for page and app splashes. LogoSpinner is still the looping Once UI mark, and Spinner is still the one for buttons and fields. More design tips live in this section.
reading draws left to right, document keeps the file's order
settled
onComplete