# WebkitJS

> WebkitJS is a from-scratch web framework and native toolchain for fast, adaptive browser interfaces. It uses Adaptive Platform JSX (`.apx`), run-once components, fine-grained state, real DOM rendering, first-party HIG components, and verified agent intelligence. It is not React and has no virtual DOM or re-render cycle.

Canonical site: https://webkitjs.com/

## Recommended documentation

- [Condensed WebkitJS documentation](https://webkitjs.com/llms-full.md): Framework model, authoring syntax, packages, CLI, MCP, server boundary, and build workflow in one document.
- [Overview](https://webkitjs.com/): Product position and live framework proofs.
- [Foundation](https://webkitjs.com/foundation): Reactivity, rendering, routing, experiences, storage, networking, and browser-platform primitives.
- [Components](https://webkitjs.com/components): Verified HIG component catalog.
- [Patterns](https://webkitjs.com/patterns): Complete interaction and product-pattern guidance.
- [Styling](https://webkitjs.com/styling): Tokens, themes, design languages, CSS generation, and visual adapters.
- [Symbols](https://webkitjs.com/symbols): SF-compatible symbol catalog and import guidance.
- [Development](https://webkitjs.com/development): Initialization, checking, building, distribution, and intelligence workflow.
- [WebkitJS Server](https://webkitjs.com/server): Separate server product, typed endpoint dialect, secure runtime, and deployment model.

## Machine-readable resources

- [Capability manifest](https://webkitjs.com/schema.json): Structured packages, syntax, commands, transports, and boundaries.
- [MCP configuration](https://webkitjs.com/mcp.json): Local stdio configuration for `webkitjs agent serve`.
- [Executable examples](https://webkitjs.com/examples/README.md): Small projects that build with the native WebkitJS CLI.

## Important boundaries

- WebkitJS components execute once. Reactive accessors update only their dependent DOM targets.
- Dynamic APX values are accessors: `{count}` is reactive; `{count()}` is a one-time snapshot.
- Use real DOM names such as `class` and `for`, not React names.
- Prefer verified WebkitJS components for interactive roles; use semantic APX for authored composition.
- The browser and server dialects are separate worlds. Client code never imports `.apxs` or `.apts` modules.
- WebkitJS provides framework knowledge and conformance. A host such as Glyphmap owns authorization and repository policy.
- No `openapi.json` is published because webkitjs.com does not expose a public HTTP API. Applications define their own typed server endpoint contracts.