XTend Why XTend Runtime paths Platform stack Documentation

Native-first application orchestration

Build for the web.
Scale with Web Components.

XTend keeps small HTML projects simple, then adds declarative orchestration, diagnostics, and controlled remote surfaces when your product grows.

One native-first toolkit

A small entry point, not a small ceiling.

Start with semantic HTML, familiar ESM JavaScript or TypeScript, or declarative RMT without closing the path to a larger application tomorrow.

Native UI

Load owned Web Components from a local manifest and compose them directly in semantic HTML.

  • No required UI framework
  • Themeable component contracts
  • Viewport-aware loading

Declarative applications

Move state, actions, resources, routes, and surfaces into reviewable RMT source when complexity grows.

  • Compiler and language tooling
  • Browser and server adapters
  • Maraca production builds

Production evidence

Keep scheduling, diagnostics, security decisions, and release readiness visible instead of implicit.

  • Fabric lanes and reporters
  • Accessibility and security gates
  • Deterministic verification

Progressive architecture

Choose the runtime path you need.

XTend Classic, the ESM Registry, and XTend Maraca share the same local, inspectable component and orchestration foundation.

XTend Classic

HTML, JavaScript, and manifest-driven Web Components

Author regular HTML, preload the first viewport, and let xtend-loader.js register deeper components as they approach the viewport.

Best for: landing pages, documentation, progressive enhancement, and small application shells.

Learn XTend Classic

ESM Registry

Named imports for JavaScript and TypeScript applications

Import scheduling, rendering, typed app and store APIs from @ccslabs/xtend, then boot the RMT orchestration host once with await readyXTend().

Imports stay side-effect-free, while browser, bundler, Vite, and DOM-neutral SSR projects use the same concise API.

Best for: JavaScript and TypeScript teams that want framework-style DX with native platform boundaries.

Explore the ESM Registry

Application platform

RMT source and Maraca builds

Compile declarative application records into optimized ESM bundles with explicit hydration, transitions, PWA policy, and production evidence.

Best for: stateful products, governed teams, reusable shells, and server-capable delivery.

Explore XTend Maraca

Source to governed surface

Every layer has a visible responsibility.

XTend scales through explicit boundaries rather than hiding application behavior inside a monolithic runtime.

  1. 01

    Author

    Start in HTML or describe state, actions, events, resources, and surfaces in RMT.

  2. 02

    Compose

    Connect XTend UI, routing, browser capabilities, and host adapters without surrendering platform primitives.

  3. 03

    Observe

    Use Fabric lanes, fibers, reporters, and hydration policy to make runtime work measurable.

  4. 04

    Scale safely

    Let XScaler preflight remote code and XSurface Shard create lifecycle-owned, ATC-compatible handoffs.

ESM Registry · JavaScript and TypeScript

Start with the module workflow you already know.

Use the package root with a browser import map, Vite, or another ESM-aware bundler. The import is side-effect-free; readiness explicitly starts the orchestration kernel.

XTend Classic · No application build required

The page you are viewing uses XTend Classic.

Preload only the first viewport and leave the remaining component modules to the loader.

Keep the entry point simple

Build one page. Keep the path to a platform.

Start in semantic HTML, build a typed ESM application, learn RMT, or inspect every runtime and gate directly in the repository.

XTend · Native-first by design Back to top Documentation GitHub
Apache-2.0 · Built with XTend Classic