Overview

These setups are application code, outside the library: your application decides which pages load the files and when content changes.

#WordPress

WordPress enqueues the stylesheet and script as any other. WordPress shows the lines, the optional wordpress.php in the built files, which registers every file as a handle, and how a plugin that extends a product uses its handles.

#Elementor

Elementor replaces a widget’s markup while you edit it and adds popups later. With the files enqueued, one line that observes the document starts what Elementor adds and destroys what it removes, as WordPress shows.

#Astro client navigation

Astro’s client router swaps the page without loading it. Observing the document handles every swap: the departing page’s components are destroyed and the new page’s start, and an element with data-astro-transition-persist keeps its components. Astro shows the script; see also the Astro navigation lifecycle.

#React

@pelatform/react holds React components with the markup, classes and ARIA of the HTML ones, for Next.js, Astro islands and a WordPress plugin on WordPress’s own React. React shows each setup.

#Other hosts

Laravel, Blade and other plain-HTML hosts use the same CSS and Browser assets, or an ESM client entry. No server framework adapter is included. For content they insert or replace later, see Dynamic content.

#AI agents

A coding agent, such as Claude Code, writes Pelatform UI as these pages do when it reads them first. AI agents gives the setup it keeps, the order it composes in and the lines for a project’s instructions.