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 5

Theme Package Composition + Export / Import

Create one portable, versioned appearance package for FG UI and FGUI-J. Packages describe supported Theme/Accent configuration only; arbitrary CSS tokens are deliberately excluded.

+0.0.7

Package source

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

Package contract

The schema records product compatibility, supported modes, site defaults, preference locks, the semantic Hybrid surface model and preview metadata.

Safety boundary: package import never accepts arbitrary CSS variables or executable code.

FGUI.theme.exportPackage() and FGUI.theme.validatePackage() expose the Phase 5 package contract.

Exported package

Canonical JSON updates from the source controls above.

LIVE JSON

Import package

Paste a version 1 FG UI theme package. Validation happens before any builder values change.

No package imported yet.

Import rules

Unknown executable behavior and arbitrary design-token payloads are not applied. Only the versioned site Theme, Accent, preference locks and fixed compatibility metadata are accepted.

Portable by design

The same JSON can be consumed by core FG UI, FGUI-J, or future adapters without changing the visual contract.

Generated integration

Preview

Configured application

Preview remains isolated from visitor preferences.

Hybrid-target surface
7-step batch: +0.0.7 final checkpoint: package composition, validated import/export, compatibility rules, FGUI-J adapter guidance and responsive coverage are complete.