RootSmith Docs

Choose how to publish

Pick the way approved RootSmith pages reach your website. Use the Next.js SDK, the client package, a static site deploy hook, WordPress, a signed webhook, or MDX export.

RootSmith publishes pages on your own domain, at the path saved with each page. Open Sites → Publishing and answer How is your site built?. RootSmith shows the way to connect for your answer. When site analysis can tell what your site runs on, such as Next.js, Astro, or WordPress, it picks the answer for you.

How is your site built?MethodLive after publish
Next.js with a server (15 or 16, App Router)Next.js SDKSeconds
Astro, SvelteKit, Nuxt, or another JavaScript serverClient packageSeconds
Next.js static exportStatic site deploy hookAfter one site build
Static or Markdown site (Astro, Hugo, Jekyll, and others)Static site deploy hook or MDX exportAfter one site build, or when you add the file
Another framework with a serverWebhookWhen your code saves the page
WordPressWordPressSeconds
Another website builder (Webflow, Shopify, and others)MDX exportWhen you paste the page in

RootSmith can't publish straight to other website builders yet. Download each page when you publish and paste it into your site. You can also send the webhook to an automation tool, such as Zapier or Make, that saves the page in your builder.

Pick the SDK or the client package when you can. They're the only methods where RootSmith can refresh your page, roll back a failed update, and redirect merged pages for you.

How the settings fit together

  • Delivery endpoint: the SDK's route on your site, such as /api/rootsmith. When it's set, RootSmith publishes only through the SDK. If the SDK isn't connected, publishing stops until you fix it. Choosing another answer clears it.
  • Approval mode: Approval required or Automatic. Automatic approves automation drafts that have no flags, or only flags about your writing preferences.
  • Default schedule: Publish now or Scheduled.

Confirming a page is live

RootSmith marks a page published when it finds that exact version on your site. It loads https://<your domain><page path> and looks for an element with data-rootsmith-content set to the page ID and data-rootsmith-version set to the version. The SDK and MDX export add it for you, and so do the client package's renderHtml, WordPress posts, and the webhook's html field. A webhook receiver that renders its own HTML must add it, or you confirm the page by hand. For WordPress, RootSmith checks the address that WordPress returns.

If the first check fails, RootSmith checks again every five minutes for 24 hours.

On this page