> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usedynamite.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Read /start/capabilities before choosing an integration. Use the deployed server’s tools/list for current tool inputs.

# Frameworks

> Install on a site builder or custom application.

Install the script once in your shared layout. Give targets stable selectors and make sure they exist before Dynamite binds them.

| Platform | Typical installation |
| - | - |
| Webflow or Framer | Site-level custom code |
| Shopify | Storefront theme |
| WordPress | Shared template or script enqueue |
| HTML / server rendering | Shared document head |
| React / SPA | App-level layout with a stable target boundary |

Use the published site when checking installation.

## React and client navigation

React can overwrite external DOM changes during hydration or rerendering. Use a stable wrapper outside interactive subtrees, or insert content after a stable anchor. Keep forms and application state owned by React.

Dynamite observes History API navigation and binds on the next animation frame. If a target renders later, you need an application-specific lifecycle integration. Calling `refresh()` does not discover missing elements.

For deeper integration, use the [adaptive library](https://docs.usedynamite.com/internals/decision-pipeline.md#the-adaptive-library-is-a-separate-integration) with your own renderer.

## Domains and checkout

Origins must match exactly, including scheme, hostname, and port. Configure staging separately from production.

A storefront script does not automatically run in checkout or apply discounts. Keep prices, stock, and checkout behavior in the commerce platform.

Check initial load, client navigation, back/forward navigation, and the original state before publishing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.