Weva Docs

Weva Documentation

Weva is an HTML/CSS UI layer for Unity 6 / URP. You author UI in standard .html and .css files; Weva parses them, runs a real CSS cascade, lays the document out (block / inline / flex / grid / positioned), paints it, and renders it through a URP render-graph pass.

The design rule is loud and simple: if a feature has a well-known web behavior, Weva's behavior matches it — or Weva doesn't ship it. A subtly different behavior is worse than none, because an AI model (or a developer who knows the web) produces code that looks right and fails in surprising ways. Anything not in the supported subset fails loudly rather than silently miscomputing.

This documentation describes the runtime engine. The Figma import plugin (com.weva.figma) is documented separately.

Status

Pre-1.0 (com.weva 0.1.0). The headless layers — parser, cascade, layout, paint — are production-quality and covered by ~1900 NUnit tests. The Unity bridge layers (URP renderer feature, IMGUI fallback, TextCore bootstrap, hot reload, DevTools overlay, form controls + IME) are wired but still being validated against a real Unity 6000.4 project.

Contents

  1. Getting Started — install the package, create a document, load an HTML/CSS pair, set up URP rendering, size the viewport.
  2. Supported HTML — elements, attributes, and document structure rules.
  3. Supported CSS — properties, values, selectors, units, cascade behavior, at-rules, and the known divergences from Chrome.
  4. Animations & Transitions — @keyframes, transition / animation shorthands, easings, and which property kinds interpolate.
  5. Architecture — the parse → cascade → layout → paint → render pipeline and where each pass lives in the source tree.
  6. Text & Fonts — the ATG-primary / SDF-fallback text stack, font resolution, the default-face policy, and gradient text.
  7. Rendering — the URP render-graph pass, batching, the IMGUI fallback, and idle/scroll caching.
  8. Samples — the sample pages under Assets/UI/ and what each exercises.
  9. Testing — how the NUnit suites are organized, how to run them headlessly, and the layout-vs-Chrome audit tooling.

Author-facing guide vs. this reference

AuthoringGuide.md is the task-oriented manual for building UI — controller binding, events, forms, gestures, virtualized lists, DevTools. The pages above are the reference for what the engine supports and how it is put together. Start with Getting Started, then reach for the Authoring Guide when you build something real.