Use React inside WordPress or expose the same content to an external frontend. Choose client, static, or server rendering one template at a time.
ReactWP does not force the frontend away from WordPress. Choose the relationship that fits your project.
WordPress resolves the request and serves a normalized route to the React theme. ReactWP then owns templates, navigation, media, document head updates, scroll, and page transitions.
Build your first templateExpose normalized routes, menus, settings, SEO, previews, and authenticated users to React, Vue, Svelte, Astro, or another frontend stack.
Connect a headless frontendStart with the browser. Generate stable public pages. Add a server only where the request truly depends on it.
Explore rendering
registerTemplate('Home', {
loader: () => import('../../templates/Home'),
render: 'static',
cache: {
tags: ['post-type:project']
}
});render: 'client'The original ReactWP runtime. WordPress serves the shell and React renders the route in the browser.
render: 'static'Generate route HTML ahead of time, serve it through WordPress, and hydrate it in the browser.
render: 'server'Render request-dependent HTML through the optional Node service, then hydrate the same template.
Editors keep the administration system they know. Developers receive one normalized contract across direct loads, client navigation, static output, SSR, and external frontends.
Understand route payloadsAuthor WordPress and frontend code together, then generate a deployable installation with the assets required by the selected rendering modes.