Gavia UIv1.0.0

Why Gavia UI

An independent Vue foundation with explicit styles, app-scoped services and editable tokens.

A small application contract

Vue is the library's only required peer dependency. Routing, network requests and business state belong to your application. Import reset, base styles and a theme explicitly.

Choose built-in text for your application

The 1.0 source uses English when locale configuration is omitted. To keep Russian text, install WlConfig with wlLocaleRu in your app entry point. Missing fields in partial locales use English; spread the full preset before custom overrides. The Playground selects a preset explicitly when its language changes. Copied SFCs use their host app's configuration. This migration is part of the prepared 1.0 release candidate; publication is a separate step.

Show Vue code
import { WlConfig, wlLocaleRu } from "gavia-ui";
app.use(WlConfig, { locale: wlLocaleRu });
// A Russian preset with one application-specific label:
// app.use(WlConfig, { locale: { ...wlLocaleRu, accept: "Продолжить" } });

Override a label when your app needs it

Omitted or undefined text props follow the current locale. An explicit string, including an empty string, keeps priority; keep a meaningful accessible name when suppressing text. Change locale from a component through useWlConfig().setLocale(...): mounted controls update and other Vue applications keep their own configuration. Application content, slots and custom prop strings remain your app's translations.

Show Vue code
import { useWlConfig, wlLocaleRu } from "gavia-ui";
const configuration = useWlConfig();
configuration.setLocale(wlLocaleRu);
configuration.setLocale(undefined); // Restore the English fallback in 1.0.

One component, five themes

Gavia, Gavia Dark, Classic, Classic Dark and Newspaper share components and behavior. Change tokens or pass-through attributes instead of forking components.

Start with a working consumer

The repository includes Vite, Nuxt and custom-theme starters. Examples on component pages use the same SFC source as the copy button. Browser and manual assistive-technology acceptance are recorded separately from unit checks.

Source and guide