XTend Developer Center

Welcome to the XTend Developer Center. These docs explain XTend for developers who want to use Web Components, RMT app shells, local modules and SSR in their own products.

Learning paths

Goal	Start
Build an ESM JavaScript or SSR app	ESM Registry, Quick Start Guide
Build directly with HTML and JavaScript	XTend Classic, Quick Start Guide
Understand RMT	XTendRMT Overview
Author RMT vNext	RMT vNext Authoring Guide, RMT AnimationEngine, RMT Reference, RMT vNext Migration Notes, RMT vNext Release contract, RMT Syntax Basics
Author Native-First XTend	Native-First Authoring Guide, Native-First RMT Recipes, Native-First Migration Guide, Native-First Release Review
Build Maraca app orchestration and PWA output	XTend Maraca, Maraca Orchestration
Verify enterprise remote surfaces	RMT vNext Remote Surfaces, RMT vNext Enterprise Surface Registry, RMT vNext Cross Surface Events, RMT vNext Enterprise MFE contract
Use or migrate components	Component Development, Component Long-Tail Migration
Build managed workspaces	SurfaceManager Authoring Guide, SurfaceManager Controller, SurfaceManager Runtime, SurfaceManager Migration Guide
Verify Design Tokens	Design Tokens
Add SSR	RMT Node SSR Adapter, RMT PHP/Laravel SSR Adapter
Add pages, forms and navigation with SSR	Shared page runtime for Node and Laravel
Editor, linting and VS Code	RMT Linter, RMT Language Server, RMT App Platform Tooling, RMT Tooling Release Gates
Instrument and inspect XTend apps in the browser	XTend DEV API, XTend Dev Surface
Verify release surface	Package Export Lock, Type Exports, XTend Loader Types, XTend API Types, XTend Policy Types, XTend Builder Types, XTend Catalog Types, XTend Vendor Types
Verify release evidence	Release Readiness, Previous Release Bridge, Release Acceptance, Conditional Network Evidence, Conditional Network Evidence CI, Release Report Pack Dry Run Evidence, Readiness CI Bundle

conditional network ci: xtend.epic13.conditional-network-evidence-ci.v1
release pack evidence: xtend.epic13.release-report-pack-dry-run-evidence.v1
previous release bridge: prior local release bridge
previous release bridge path: ./release-verification.md

Product model

XTend UI provides the visible Web Components. XTendRMT describes app shells, state, actions, events, resources, surfaces, hydration, validation and surface transitions. Fabric coordinates runtime work; the RMT kernel adds scheduler lanes, fibers and telemetry. The ESM Registry exposes convenient JavaScript aliases from the package root for browser, bundler and SSR apps. XTend Classic delivers directly authored HTML and JavaScript through a local runtime manifest and xtend-loader.js. Maraca builds loaderless, kernel-orchestrated ESM apps from .rmt sources with bundle reports, browser bridges, mobile Web App Manifest output, optional PWA Service Worker scaffolding and strict contract gates. All paths share the same public runtime contracts.

Choose A Delivery Path

Choose the ESM Registry for familiar named imports in a JavaScript, TypeScript, bundler or SSR application. Choose XTend Classic for buildless HTML-first pages, dynamic catalogs and progressive enhancement. Choose XTend Maraca when RMT source should become a shipped app bundle with an inline registry, kernel scheduling, SSR/hydration, validation, surface transitions, a mobile manifest, a generated app-shell Service Worker or build evidence. Project size alone does not decide between the paths.

RMT vNext Release Surface

The RMT vNext Authoring Guide, RMT vNext Migration Notes and RMT vNext Release contract belong together. The release path points at demos/xtendrmt/fixtures/vnext-reference/source.rmt and demos/xtendrmt/fixtures/vnext-reference/generated/core.json, so an integrator can review the authoring example, compiler output and gate matrix in one pass.

RMT vNext Enterprise Surface

RMT vNext Remote Surfaces, RMT vNext Enterprise Surface Registry, RMT vNext Cross Surface Events and RMT vNext Enterprise MFE contract describe the Enterprise MFE path through rmt-vnext-enterprise-mfe-ready. The path remains network-free to verify: remote manifests, surface registry, cross-surface events and browser-smoke artifacts are local fixtures.

Tooling

npm run dev:local
xt rmt lint app.rmt
xt rmt lint app.rmt --json
xt rmt lint app.rmt --agent
xt maraca build app.rmt --orchestration strict --kernel strict --hydration strict --validation strict --transitions strict --css external --json
xt maraca build app.rmt --out dist --web-app-manifest --json
xt maraca build app.rmt --out dist --pwa --json
node tools/rmt-language-server/server.js
node scripts/run_xtend_tests.js rmt-tooling-docs --json
node scripts/run_xtend_tests.js maraca-docs rmt-vnext-tooling rmt-editor-packaging type-exports-rmt --json

The tooling path uses the public schema xtend.rmt.tooling-docs.v1. For orchestrated Maraca apps, xtend.rmt.app-orchestration.v1, xtend.rmt.form-validation.v1 and xtend.rmt.surface-transitions.v1 are also relevant.

Next steps

• Quick Start Guide
• ESM Registry
• XTend Classic
• XTend Dev Surface
• XTend DEV API
• XTend Maraca
• Maraca Orchestration
• RMT vNext Authoring Guide
• RMT AnimationEngine
• RMT Reference
• RMT vNext Migration Notes
• RMT vNext Release contract
• Native-First Authoring Guide
• Native-First RMT Recipes
• Native-First Migration Guide
• Native-First Release Review
• RMT vNext Remote Surfaces
• RMT vNext Enterprise Surface Registry
• RMT vNext Cross Surface Events
• RMT vNext Enterprise MFE contract
• Best Practices
• Trusted DOM and Sanitizing
• Trusted DOM Boundary Browser Proof
• Visual Snapshot Automation
• Coordinate Parsedown with RMT
• Changelog