foldkit.dev is hosted on AWS behind Cloudflare. It measures traffic with Vercel Web Analytics. It sends email through Buttondown.
| Technology | Version | First seen |
|---|---|---|
| Frontend Build Tools & CSS3 | ||
| – | 7 Nov 2026 | |
| – | 7 Nov 2026 | |
| – | 7 Nov 2026 | |
| CDN & Hosting3 | ||
| – | 7 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 7 Nov 2026 | |
| Email Marketing & Lead Capture1 | ||
| – | 7 Nov 2026 | |
| Error Tracking & Performance Monitoring1 | ||
| – | 7 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 7 Nov 2026 | |
| Site Search1 | ||
| – | 7 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
Counted from every stack change we've recorded: of the sites we watched running one of this site's tools, how many went on to add another. A pattern across sites, not a forecast for this one.
us1-smtp.messagingengine.comus2-smtp.messagingengine.comotto.ns.cloudflare.comrobin.ns.cloudflare.comletsencrypt.orgpki.goog; cansignhttpexchanges=yesletsencrypt.orgdigicert.com; cansignhttpexchanges=yesssl.comcomodoca.comcomodoca.compki.goog; cansignhttpexchanges=yesv=spf1 include:spf.messagingengine.com ?allgoogle-site-verification=oOszDpwNR4x7ogyJ8siTf6XXyljtblaOc-iYlVXdD20User-agent: * Allow: / Content-Signal: ai-train=yes, search=yes, ai-input=yes Sitemap: https://foldkit.dev/sitemap.xml # Agent-friendly digests. Every page is also available as Markdown by # appending `.md` to its URL (e.g. https://foldkit.dev/get-started.md) # or by requesting the page URL with `Accept: text/markdown`. # https://foldkit.dev/llms.txt # https://foldkit.dev/llms-full.txt # https://foldkit.dev/openapi.json # # Read-only JSON content API, documented at https://foldkit.dev/api # https://foldkit.dev/api/v1
# Foldkit > Foldkit is a TypeScript frontend framework built on Effect-TS that uses The Elm Architecture: a single Model, pure update, and side effects confined to Commands. This index lists every page on the Foldkit documentation site with a short description. Every page is also available as Markdown by appending `.md` to its URL (e.g. https://foldkit.dev/get-started.md). A single-file concatenation of every page is available at https://foldkit.dev/llms-full.txt. When to use Foldkit: - Building a browser single-page application in TypeScript around The Elm Architecture: one Schema-defined Model, Messages as facts, a pure update function, and side effects confined to Commands. - Extending a codebase that already uses Effect-TS, since Foldkit shares its idioms (Effect, Schema, Match, Option) and its ecosystem. - Applications where agents write or audit significant code. Explicit state transitions and Messages-as-data make programs inspectable, and the Story and Scene test frameworks drive them without a browser. - Not a fit for: server-only projects with no browser UI, teams staying on React and JSX idioms, or codebases avoiding the Effect ecosystem. How an agent works with Foldkit: - Scaffold a new application with `npm create foldkit-app@latest` (pnpm, yarn, and bun equivalents work too). - Fetch any page below as Markdown by appending `.md` to its URL, or by requesting the page URL with `Accept: text/markdown`. - Connect to a running app through the DevTools MCP server (`npx @foldkit/devtools-mcp init`) to inspect the Model, replay history, and dispatch Messages. - Install the repository skills from https://foldkit.dev/ai/skills for architecture guidance, program generation, and application audits. ## Developer Resources - [llms-full.txt](https://foldkit.dev/llms-full.txt): Every documentation page concatenated into one Markdown file. - [Content API documentation](https://foldkit.dev/api): The read-only JSON API for this site: endpoints, authentication, versioning and deprecation policy, rate limit headers, and the error model. - [Content API service index](https://foldkit.dev/api/v1): The endpoint list and policies as JSON. Pages, sections, examples, and blog posts hang off it. - [openapi.json](https://foldkit.dev/openapi.json): OpenAPI 3.1 description of this site's machine-readable content endpoints, with a typed schema for every response. - [Sitemap](https://foldkit.dev/sitemap.xml): Every page URL on the site. - [AI overview](https://foldkit.dev/ai/overview): How Foldkit's explicit architecture supports coding agents, and the resources available to them. - [Agent skills](https://foldkit.dev/ai/skills): Installable repository skills for architecture guidance, program generation, and application audits. - [DevTools MCP server](https://foldkit.dev/ai/mcp): Connect an agent to a running Foldkit application. Published on npm as @foldkit/devtools-mcp. - [GitHub repository](https://github.com/foldkit/foldkit): Source code, issues, and discussions. - [Blog RSS feed](https://foldkit.dev/blog/rss.xml): Release announcements and deep dives. - [About](https://foldkit.dev/about): What Foldkit is, who builds it, and how it is released. - [Contact](https://foldkit.dev/contact): Issues, chat, security reports, and contributions. - [Privacy](https://foldkit.dev/privacy): What this site collects and what stays in your browser. ## Docs - [Coming from React](https://foldkit.dev/react/coming-from-react): See how Foldkit replaces component-owned state and Effects with one Model, Messages, update, Commands, Subscriptions, and Submodels. - [Coming from TanStack Query](https://foldkit.dev/react/coming-from-tanstack-query): Foldkit has no useQuery. AsyncData models remote values, while caching, refetching, invalidation, deduplication, and request races remain visible application policy. - [Field Validation](https://foldkit.dev/core/field-validation): Model each field as NotValidated, Validating, Invalid, or Valid. Compose synchronous and asynchronous Rules, cross-field checks, and form-level validation. - [Get Started](https://foldkit.dev/get-started): Create a Foldkit project from a starter, inspect the generated structure, or add Foldkit to an existing Vite application. - [Project Organization](https://foldkit.dev/patterns/project-organization): Start with one main module, then separate Messages, Commands, Submodels, and Subscriptions when ownership or file size makes the split useful. - [Roadmap](https://foldkit.dev/introduction/roadmap): Where Foldkit is today, how it got here, the work remaining before 1.0, and the architectural promises that will not change. - [Routing & Navigation](https://foldkit.dev/core/routing-and-navigation): Define routes with bidirectional parser combinators that decode URLs into typed values and build URLs from Schema-validated parameters. - [Testing](https://foldkit.dev/testing): Test Foldkit programs with Story and Scene. Story drives the update loop directly, while Scene drives the rendered view through accessible locators. - [Why Foldkit](https://foldkit.dev/introduction/why-foldkit): Why Foldkit exists and the principles behind its design. ## Guides - [Foldkit vs Elm: Side by Side](https://foldkit.dev/elm/foldkit-vs-elm-side-by-side): A side-by-side comparison of the same pixel art editor built in both Foldkit and Elm. Same architecture, different host: ports vs Commands, decoders vs Schema, and what each side gives up. - [Foldkit vs React + Effect Atom](https://foldkit.dev/react/foldkit-vs-react-effect-atom): Two Effect-native architectures: Effect Atom distributes state across reactive cells inside React, while Foldkit builds the application around one Model and update function. - [Foldkit vs React: Side by Side](https://foldkit.dev/react/foldkit-vs-react-side-by-side): A side-by-side comparison of the same pixel art editor built in both Foldkit and React. Covers state management, side effects, testing, performance, and architectural tradeoffs. ## Core - [Architecture](https://foldkit.dev/core/architecture): How Model, Messages, update, view, Commands, Subscriptions, and the Runtime form Foldkit’s Elm Architecture loop. - [Async Data](https://foldkit.dev/core/async-data): A six-state value type for asynchronously loaded data in the Model: Idle, Loading, Refreshing, Failure, Stale, and Success, with stale-while-revalidate and keep-stale-on-failure built in. - [Canvas](https://foldkit.dev/core/canvas): Declarative 2D rendering with a Schema-defined Shape AST and pointer events translated to canvas-local coordinates. - [Commands](https://foldkit.dev/core/commands): Describe one-shot Effects caused by Messages, map their results back into Messages, test them as values, and interrupt keyed work when needed. - [Counter Example](https://foldkit.dev/core/counter-example): Build and trace a minimal Counter through its Model, Message Schema, update, view, init, and Runtime wiring. - [Crash View](https://foldkit.dev/core/crash-view): Replace the default Runtime crash screen and report unrecoverable failures without treating expected Effect failures as crashes. - [CustomElement](https://foldkit.dev/core/custom-element): Create typed Foldkit builders for native custom elements by declaring their properties and CustomEvents with Schema. - [DevTools](https://foldkit.dev/core/devtools): Inspect Message history, Model changes, Commands, and Mounts in the development overlay. Configure time travel, filtering, history limits, and AI dispatch. - [Dom](https://foldkit.dev/core/dom): Use Effects for one-time DOM work and composable Streams for events, media queries, and key bindings. - [Embedding](https://foldkit.dev/core/embedding): Embed a Foldkit widget in another application through a Schema-typed handle. Covers initial Flags, inbound and outbound Ports, disposal, and React integration. - [File](https://foldkit.dev/core/file): Read and select browser files through an opaque File type, with event attributes for native inputs and drop zones. - [Freeze Model](https://foldkit.dev/core/freeze-model): Deep-freeze the Model in development to catch accidental mutation at the write site. Covers what is frozen and the Runtime cost. - [Http](https://foldkit.dev/core/http): Provide a Fetch-backed HttpClient to Commands while keeping browser requests CORS-simple by disabling trace header propagation unless it is required. - [Init & Flags](https://foldkit.dev/core/init-and-flags): Construct the first Model and startup Commands. Routing supplies the current URL, while Schema-validated Flags support fresh client boots and hydration. - [Machine](https://foldkit.dev/core/machine): Model multi-state workflows as typed transition tables with guards, shared Edges, update integration, structural analysis, and pure tests. - [Managed Resources](https://foldkit.dev/core/managed-resources): Acquire a stateful handle while a Model condition holds, expose it to Commands, and release it when dependencies change. Covers Layers and Submodel lifting. - [Messages](https://foldkit.dev/core/messages): Define the facts update can handle as a Schema-backed Message union, with naming conventions for user actions, Command results, and Submodel wrappers. - [Model](https://foldkit.dev/core/model): Define application state as one Schema-backed Model. Foldkit uses its runtime Schema to preserve state across hot updates and validate unknown data. - [Mount](https://foldkit.dev/core/mount): Run DOM work while a specific rendered element exists. Mount supplies the live Element, emits declared result Messages, and keeps setup paired with cleanup. - [Preserve Scroll](https://foldkit.dev/core/preserve-scroll): Restore window scroll position across Vite dev reloads. Covers when restoration runs and its window-only scope. - [Query](https://foldkit.dev/core/query): Fetch, cache, and refresh remote data with reusable Submodels and less boilerplate. - [Render](https://foldkit.dev/core/render): Synchronize Commands and Effects with the browser render cycle so DOM reads and CSS transitions land on the intended frame. - [Resources](https://foldkit.dev/core/resources): Provide app-lifetime Effect services to Commands, Subscriptions, Mounts, and Flags, or provide a service directly when sharing is unnecessary. - [Runtime](https://foldkit.dev/core/runtime): Configure a page-owning application with makeApplication, or mount a reusable widget with makeElement and embed. - [Server Rendering](https://foldkit.dev/core/server-rendering): Render the same application to HTML for request-time SSR or build-time SSG, then hydrate it in place through a validated build-id and Flags handoff. - [Slow Warnings](https://foldkit.dev/core/slow-warnings): Measure development-mode update, view, patch, and Subscription dependency phases, interpret warnings, and tune thresholds after profiling. - [Submodel](https://foldkit.dev/core/submodel): Split a large application into child state machines while preserving parent-to-child Message flow. Covers Update.foldChild, h.submodel, OutMessages, reflection, testing, and DevTools. - [Subscriptions](https://foldkit.dev/core/subscriptions): Run ongoing Streams whose lifetime follows Model-derived dependencies. Covers restart behavior, timers, animation frames, live dependency reads, and Submodel lifting. - [Update](https://foldkit.dev/core/update): Handle every Message with a pure update function that returns the next Model and Commands. Use Match and modifyFields to keep transitions exhaustive and immutable. - [View](https://foldkit.dev/core/view): Return a Document or Html value as a pure function of the Model. Covers document metadata, element builders, events, and view decomposition. - [View Memoization](https://foldkit.dev/core/view-memoization): Skip stable view subtrees with createLazy and createKeyedLazy, choose cache keys by entity identity, and profile before adding memoization. - [View Transitions](https://foldkit.dev/core/view-transitions): Animate qualifying renders with the browser View Transitions API. Covers route direction, shared elements, and when a running transition is skipped. ## Best Practices - [Immutability](https://foldkit.dev/best-practices/immutability): Update Models immutably with modifyFields, preserving references for unchanged branches and keeping state transitions predictable. - [Keying](https://foldkit.dev/best-practices/keying): Use stable Model identifiers to preserve identity for mapped list items and entities rendered at one position. - [Messages](https://foldkit.dev/best-practices/messages): Name Messages as verb-first, past-tense facts, and name Command result Messages after the Command that produced them. - [Side Effects & Purity](https://foldkit.dev/best-practices/side-effects-and-purity): Keep update and view deterministic by confining outside work to Commands, Subscriptions, Mounts, ManagedResources, and other Runtime-managed boundaries. ## Patterns - [Anti-patterns](https://foldkit.dev/patterns/anti-patterns): Architectural warning signs in Foldkit apps, with idiomatic replacements for ambiguous state, leaky Submodel boundaries, misplaced side effects, stale async results, Command ordering, and live handles. - [Informing Submodels](https://foldkit.dev/patterns/informing-submodels): Relay a change a Submodel does not own (a URL, a server push, an auth change) through a helper it exposes, so it can update its own state in response. - [Subscription Organization](https://foldkit.dev/patterns/subscription-organization): Organize Subscription records by ownership and lift child Subscriptions through nested Model and Message types. ## Tooling - [Oxlint Plugin](https://foldkit.dev/tooling/oxlint-plugin): Install and configure @foldkit/oxlint-plugin, then see what each Foldkit-specific rule accepts and rejects. ## FAQ - [Performance](https://foldkit.dev/faq/performance): Foldkit’s rendering cost model, TodoMVC benchmark results, development-mode overhead, and the tools for measuring and memoizing expensive views. ## Foldkit UI - [Anchor](https://foldkit.dev/ui/anchor): Position and portal floating panels with the same Floating UI runtime used by Listbox, Combobox, Menu, Popover, Tooltip, and Date Picker. - [Animation](https://foldkit.dev/ui/animation): Coordinates CSS enter/leave animations via a state machine and data attributes. Works with both CSS transitions and keyframe animations. - [Button](https://foldkit.dev/ui/button): A stateless wrapper around the native button with accessibility attributes, event wiring, and styling hooks. - [Calendar](https://foldkit.dev/ui/calendar): Accessible inline calendar grid with 2D keyboard navigation, locale-aware headers, and min/max/disabled-date constraints. - [Checkbox](https://foldkit.dev/ui/checkbox): Accessible checkbox with indeterminate state support. - [Combobox](https://foldkit.dev/ui/combobox): A searchable selection Submodel with parent-controlled filtering, single-select and multi-select modes, and anchored positioning. - [Date Picker](https://foldkit.dev/ui/date-picker): An accessible Date Picker that wraps Calendar in a Popover, with focus management, click-outside dismissal, and a hidden input for native form submission. - [Dialog](https://foldkit.dev/ui/dialog): A modal dialog backed by the native dialog element with focus trapping and scroll locking. - [Disclosure](https://foldkit.dev/ui/disclosure): A stateless, controlled show-and-hide helper for inline content, with disclosure semantics and keyboard behavior. - [Drag and Drop](https://foldkit.dev/ui/drag-and-drop): Accessible drag and drop with keyboard support, auto-scrolling, and screen reader announcements. - [Fieldset](https://foldkit.dev/ui/fieldset): A stateless wrapper around the native fieldset with linked legend and description attributes. - [File Drop](https://foldkit.dev/ui/file-drop): Headless file drop zone that accepts drag-and-drop plus click-to-browse via a hidden native file input. - [Foldkit UI](https://foldkit.dev/ui/overview): Choose between stateful Submodels and stateless render helpers in Foldkit’s headless UI package. Covers accessibility, styling, installation, and the component catalog. - [Hover Intent](https://foldkit.dev/ui/hover-intent): Behavior-only Submodel for delayed hover and focus reveal across a trigger and panel. - [Input](https://foldkit.dev/ui/input): A thin wrapper around the native input with ARIA linking and styling hooks. - [Listbox](https://foldkit.dev/ui/listbox): A selection Submodel with single-select and multi-select modes, keyboard navigation, typeahead, and anchored positioning. - [Menu](https://foldkit.dev/ui/menu): An anchored action-menu Submodel with keyboard navigation, typeahead, dismissal, and optional modal behavior. - [Meter](https://foldkit.dev/ui/meter): A scalar value in a known range with meter semantics, clamped aria-valuenow, and threshold data attributes. - [Nav](https://foldkit.dev/ui/nav): A stateless helper for URL-driven navigation with aria-current page semantics. - [Popover](https://foldkit.dev/ui/popover): An anchored floating panel for arbitrary content, with dismissal, focus return, portaling, and optional modal behavior. - [Progress](https://foldkit.dev/ui/progress): Task progress with determinate and indeterminate states, progressbar semantics, and data-state styling hooks. - [Radio Group](https://foldkit.dev/ui/radio-group): A selection Submodel for radio options, with roving tabindex, keyboard navigation, and read-only behavior. - [Select](https://foldkit.dev/ui/select): A stateless wrapper around the native select with ARIA linking, change handling, and styling hooks. - [Selection Submodels](https://foldkit.dev/ui/selection-submodels): Use create<Item>() factories to keep one item type across a selection Submodel’s view, update, programmatic helpers, and OutMessages. - [Slider](https://foldkit.dev/ui/slider): A numeric range Submodel with pointer dragging, keyboard navigation, constraints, steps, and ARIA slider semantics. - [Switch](https://foldkit.dev/ui/switch): A stateless, controlled toggle for immediate on-and-off actions, with keyboard behavior and switch semantics. - [Tabs](https://foldkit.dev/ui/tabs): A selection Submodel for tab panels, with roving tabindex, horizontal and vertical orientation, and automatic or manual activation. - [Textarea](https://foldkit.dev/ui/textarea): A thin wrapper around the native textarea with ARIA linking and styling hooks. - [Toast](https://foldkit.dev/ui/toast): Stack of transient notifications anchored to a corner of the viewport with per-entry enter/leave animations and auto-dismiss. - [Tooltip](https://foldkit.dev/ui/tooltip): Non-interactive floating label that appears on hover or focus and hides on leave, blur, or Escape. - [Virtual List](https://foldkit.dev/ui/virtual-list): Render only visible rows plus overscan while spacers preserve scroll geometry. Supports fixed and variable row heights, measurement, and programmatic scrolling. ## Testing - [Scene](https://foldkit.dev/testing/scene): Drive the rendered VNode tree with accessible locators, dispatch interactions, resolve lifecycle results, and assert on the resulting HTML. - [Story](https://foldkit.dev/testing/story): Drive update with Messages, inspect the Model and Commands, and supply Command results without executing their Effects. ## Examples - [API Cache](https://foldkit.dev/example-apps/api-cache): Query caching without a query client. Demonstrates stale-while-revalidate, request deduplication, invalidation, and interval refetching. - [API Cache Query](https://foldkit.dev/example-apps/api-cache-query): The API Cache app rewritten with experimental Query.define. Fetching and retained entries live in Query Submodels. The parent folds Got* Messages. - [Auth](https://foldkit.dev/example-apps/auth): An authentication flow with Submodels, OutMessage, protected routes, and session management. - [Canvas Art](https://foldkit.dev/example-apps/canvas-art): Click the canvas to spawn bouncing balls. Dem
| – |
| 7 Nov 2026 |
| – | 7 Nov 2026 |