Deploy & embed

Deploy (publish) uploads your current project build so your Webflow site can load it.
Embed gives you a copy-ready loader script for Webflow.

Hosted publish assets are served through Cloudflare R2 on the Cloudflare edge network (the same CDN family Webflow uses), which helps maximize compatibility and delivery speed. Project files are published under https://ssscript.dev/<username>/<project>/... (for example: https://ssscript.dev/valla.federico/t1/app.css).

Before you publish Paid

Paid feature: Hosted publish

Publishing requires sign-in and an active subscription.

If publishing is locked, the top-right action shows Upgrade instead of Publish.

• You need to be signed in.
• You need an active subscription to use hosted publish.
• Your project must build successfully.

Deploy flow (what you will see)

1. Click Publish in the header.
2. A Deploy overlay opens with this confirmation:
   • “This will build the current project and upload the output to your publish pipeline…”
3. Confirm the project URL shown in the modal (https://ssscript.dev/<username>/<project>/).
4. Click Publish now.
5. The status area updates live:
   • Ready to publish.
   • Building project…
   • Uploading build output…
   • Publish completed successfully.
   • or Publish failed: …

The overlay stays open so you can review the result and close it when you want.

Extra visibility in the Deploy modal

• Last published at appears in the footer so you can quickly confirm freshness.
• Files to deploy (N) is expandable and lists each file with its final public URL.
• File names in that list are clickable and open the live asset URL.
• Current Files (top-right) opens a second modal that loads the currently deployed files from Cloudflare for this project.
• Both modals use a top-right X to close.

Rollback

If a publish goes wrong, you can roll back to the previously deployed version. Ssscript keeps an archive of your prior deployment so you can restore it.

1. Open the Deploy overlay.
2. If an archive is available, you will see a Rollback action.
3. Click it to start the rollback. The terminal logs progress:
   • “Rollback: restoring previous deploy from archive…”
   • “Rollback complete: restored N file(s), removed M newer file(s).”
4. The public URL is updated to point at the restored files.

Rollback requires sign-in. If no archive exists (e.g. you have only published once), the option is not shown.

Embed flow

• Open Embed from the terminal panel.
• You get a single Loader Script to copy — a <script> block that handles both JS and CSS loading, environment detection, and dev-server fallback.
• If your project has a linked Webflow site, you can click Apply loader to Webflow to inject the script automatically via the Custom Code API.

If you are not logged in

The overlay clearly tells you the loader points to local dev URLs only and asks you to sign in for hosted publish and fallback URLs.

If you are logged in and published

The loader targets your published project namespace (https://ssscript.dev/<username>/<project>/) so you can republish and keep using the same snippet.

See Embedding in Webflow for placement details.