1Footer documentation
Platforms, frameworks and availability
Choose a delivery path and see which automatic repair adapters are released or still in development.
Last reviewed
Choose delivery and automation separately
A platform can support a server-rendered package or HTML export before automatic native installation is released. The table below distinguishes those paths. “In development” means the automatic adapter is not ready for production use.
Cloudflare delivery can serve compatible sites across frameworks. It needs an eligible domain and provider setup. Wix and Shopify require native paths rather than ordinary Cloudflare proxying.
| Platform / framework | Delivery | Automatic repair |
|---|---|---|
| Vercel · Next.js App Router / TanStack Start | Native server delivery. | Available Automatic staged repair through connected Vercel access. Source preparation also uses the matching GitHub connection when needed. |
| Cloudflare · compatible websites | Footer HTML is added at the edge, across compatible hosts and frameworks. | Available Automatic checks and recovery through connected Cloudflare access. The domain and hosting provider must allow this delivery path. |
| Framer | Native exports and connected Server API synchronization. | Available Connected publishing can synchronize an installed footer. Compatible Cloudflare delivery is another option when the domain supports it. |
| Lovable | Website import, component delivery and compatible Cloudflare delivery. | Available Migration detection refreshes the saved platform. Automatic delivery repair depends on the connected destination, such as a supported Vercel project or Cloudflare zone. |
| React SDK · Next.js, TanStack Start, Remix, Astro | A server or build loader supplies the published HTML and CSS to your app. | Setup required Install in your framework and publishing workflow. Automatic source repair is available for the released Vercel combinations above; broader installers are in development. |
| WordPress | The downloadable plugin can render the footer on your server. | In development Automatic native installation, updates and recovery through owner-bound WordPress access are in development. |
| HubSpot | Export a native HTML/CSS module snapshot and publish it in your CMS. | In development Export and republish snapshots when content changes. Account-connected native publishing and repair are in development. |
| Webflow / Squarespace / other HTML sites | HTML/CSS exports or compatible Cloudflare delivery. A client embed alone does not establish initial-HTML delivery. | Setup required Automatic repair is available through compatible connected Cloudflare delivery. Native publishing varies by platform. |
| Astro native automatic installer | The React SDK server/build artifact is available today. | In development The native middleware installer for automatic prerendered and server delivery is in development. |
| Netlify native automatic repair | Compatible Cloudflare delivery can be used today when your domain permits it. | In development Native draft builds, verification and recovery are in development. Live provider, navigation and security-policy validation are still required. |
| Shopify native automatic repair | A native theme delivery adapter is in development. | In development Automatic installation, publication updates, pause/resume and rollback need provider permissions and live storefront verification before release. |
| Wix native automatic repair | Native server rendering and site-wide placement are in development. | In development Automatic migration repair is not available yet. A widget or crawler-only markup does not establish visible initial HTML for ordinary visitors. |
Install the React server/build package
Install the compiled package in the website project. Use the actual website ID from your workspace and the public domain you added.
npm install https://app.1footer.com/downloads/onefooter-react-2.0.0.tgzLoad the publication on the server
Run the loader on your server or during a build, then pass the same artifact into the rendered component. Keep workspace API keys on the server. The public website binding can be used without a workspace secret.
Use the current request pathname for page targeting. A static build must load an artifact for each generated route.
import { loadOneFooter } from 'onefooter-react/server';
const artifact = await loadOneFooter({
websiteId: 'YOUR_WEBSITE_ID',
domain: 'example.com',
path: requestPathname,
});
// Return artifact as server loader data for the page.Render the artifact into the page
Render the component as part of the initial document, then hydrate with the same artifact. A null result means unavailable: preserve a last successful artifact or local navigation. An empty artifact means paused or excluded: keep it empty rather than restoring stale content.
Install the footer once in your shared layout. Framework request loaders and client-side navigation must keep the artifact in sync with the current pathname.
import { OneFooterClient } from 'onefooter-react/client';
// artifact comes from your server loader or build.
<OneFooterClient
artifact={artifact}
fallback={<footer>Existing navigation</footer>}
/>Static sites and CMS snapshots
Include the published HTML and CSS in the generated document. Add export and upload to your normal publishing workflow so later footer changes reach the site.
A browser-only script can show a footer after loading without putting the links in the initial response. Use server/build rendering or a compatible delivery adapter when initial-HTML delivery matters.