Type to search pages and rules.

Browse pages

Overview

The web pages state what the React and Svelte frontends do the same way: one TypeScript toolchain, one generated API client, and one shared UI package across structure, rendering, components, UI, patterns, data, and testing. No project selects this folder directly; selecting the React Stack or Svelte Stack applies it through that stack's folder chain. A developer or agent adding a route, a component, or data code to a React or Svelte frontend finds the shared rule here and the stack-specific rule on the stack page.

Markdown

How the Pages Fit Together#

Each page here follows one frontend principle page and states what the two web stacks do the same way: one toolchain, one generated client, one shared UI package. Where React and Svelte differ, the shared page states the rule once and each stack page names the binding for its stack. A team that adds a web screen reads the principle page, then the shared page here, then the stack page where the stacks differ.

Shared Web Pages#

  • Web Structure: the application tree, the frame, use-case marks, and the generated records file.
  • Web Rendering and Routes: the route metadata rule both stacks share.
  • TypeScript Web Components: the registry source, the closed element list, and the shared route checks.
  • Web UI: the registry build, suite marks, CSS decisions, and source rules for shared UI.
  • Web UI Patterns: one implementation per platform for each chosen pattern.
  • Web Data and State: the generated client, failure mapping, cache updates, and state ownership.
  • Web Testing: Vitest beside the module and Playwright against a running stack.

Stacks#

  • React Stack: the rendering mode choice and the names, files, and libraries React alone requires.
  • Svelte Stack: the rendering mode choice and the names, files, and libraries Svelte alone requires.