FG UI 1.3 development

Theme Inheritance 1.3

Phase 2 component inheritance across local Light and Dark semantic surfaces.

PHASE 2
ACTIVE FG UI 1.3 DEVELOPMENT

FG UI 1.2.0 remains Stable. This page exercises additive 1.3 theme-composition work against the live /dev runtime.

FG UI 1.3 · Phase 4A

Theme Builder + Site Configuration

Build a site-level appearance declaration that FGUI understands before styled paint. Phase 4A starts with the site default Theme contract, then adds default Accent, visitor permissions, generated integration and preview/reset controls.

+0.0.6

Site default Theme

Choose the appearance used when no visitor preference is active.

Leave blank to use bundled Manrope. Load your custom font in your site; FG UI never fetches third-party font services automatically.

The site default Accent is declarative through data-fgui-accent-default. FG UI derives contrast-safe Light and Dark recipes from the hue.

When disabled, saved visitor Theme preferences are ignored and standard FGUI Theme switchers become unavailable.

When disabled, the site Accent remains authoritative and saved visitor Accent preferences are ignored.

Phase 4A contract: Theme and Accent defaults are site declarations. Visitor preferences are overrides only when the site permits them.

Runtime contract

FGUI exposes the resolved declaration through FGUI.theme.getSiteConfig(). The same configuration is used by the zero-flash startup path and the full theme runtime.

Dark surface

Composition remains independent

Site configuration does not replace local Light/Dark/Hybrid composition.

Preview + reset

Preview the current builder values without changing this Laboratory page or writing visitor preferences.

Preview

Configured application

LIVE

This isolated preview receives the selected Theme and generated Accent recipe.

Hybrid-target region

Generated integration

This updates directly from the Theme, Accent and visitor-permission choices above. The runtime script stays before the stylesheet so saved/default appearance resolves before styled paint.

LIVE OUTPUT

Declarative foundation

The generated integration will ultimately use the same pre-CSS order proven in Phase 3A.

<html data-fgui-theme-default="hybrid"><script src="fgui.js"></script><link rel="stylesheet" href="fgui.css">
7-step batch: this page is intentionally growing through +0.0.1 → +0.0.7. The final step performs the complete Phase 4A validation and stops.