FNJ
AFTER YOUR CONVERSION

Your site is ready.
Here's what comes next.

Preview it, make it yours, and publish it on your own infrastructure. This guide takes you from conversion to launch.

Explore the guide
01 / YOUR NEW SITE

Start with the result

FNJ gives you a working preview and the code behind it. Review the conversion before you choose where it goes next.

·· 01

Preview the result

Open the live preview, then switch between desktop and mobile. Check every important page, link, form, and interaction.

·· 02

Make it yours

Edit the downloaded code, or connect an MCP-compatible agent to update supported site content. Review changes before publishing.

·· 03

Keep the code

Download the ZIP for a local copy. You can also push your saved site to a GitHub repository you control.

✳

Before you publish: test interactive elements and mobile layouts. Some features from the original platform can need manual work in exported code.

02 / DEPLOYMENT

Put it on Cloudflare

Publish the converted static site to Cloudflare Pages in your own account. FNJ handles the upload; Cloudflare serves the live site.

☁

Cloudflare Pages

A live URL for your converted site.

Cloudflare custom domain guide ↗
  1. 01From the conversion result, open More actions → Deploy with token. Saved sites also have a deploy action in the dashboard.
  2. 02Choose Cloudflare. Create an API token with Pages: Edit permission and paste it into FNJ.
  3. 03Select Check token. Choose your account, or enter its Account ID if it does not appear. Name the project and deploy.
  4. 04Open your new pages.dev URL. For your own domain, add it under Custom domains in that Cloudflare Pages project.
FNJ deploys static output. Your Cloudflare token is stored encrypted so you can publish updates to the same site later.
USE WITH YOUR AGENT

Cloudflare deployment prompt

Paste this into your MCP-connected agent to coordinate the launch and verify the live site.

Help me deploy my converted FNJ site to my own Cloudflare Pages account.

1. Use my connected FNJ MCP to call list_sites, then get_site for the site I choose. Ask me which site only if it is unclear.
2. Check the site's pages, live URL, and pending changes. FNJ MCP cannot connect a new Cloudflare account. If this is the first deployment, guide me to the site's Deploy with token action in my FNJ dashboard. I will enter my Cloudflare Pages token directly in FNJ. Never ask me to paste a token in chat.
3. Confirm in the FNJ dashboard that the saved deploy target for this site is Cloudflare. If it is connected and there are unpublished changes, use FNJ MCP's publish tool to publish them. Do not call publish if the saved provider is uncertain; it might redeploy to a different provider. If the MCP connection is read only, tell me to authorize write access.
4. Open the returned Pages URL, check the home page and important routes on desktop and mobile, and report the live URL and any issues. If the site is already live with no pending changes, verify it instead of forcing a publish. Do not claim success until the public URL loads.

03 / SOURCE CODE

Keep it in GitHub

Send your code to an existing repository you control. Use it as a backup, continue editing locally, or make it part of your own workflow.

⌘

GitHub repository

Your generated code, on your branch.

Create a fine-grained token ↗
  1. 01Create a repository in GitHub with an initial commit, such as a README.
  2. 02From your saved site in the FNJ dashboard, choose Push to GitHub. Select current HTML with saved site changes, or the original generated source.
  3. 03Enter owner/repository and a fine-grained token for that repository with Contents: Read and write.
  4. 04Review the fnj-site/ folder on the fnj-export branch. Your default branch stays untouched.
Pushing to GitHub saves code; it does not publish the website. FNJ uses the token for that push and does not save it.
USE WITH YOUR AGENT

GitHub code push prompt

Give this to your agent to place the latest code in a repository you control.

Help me put the current code for my converted FNJ site in my own GitHub repository.

1. Use my connected FNJ MCP to call list_sites and get_site. Ask me which site or repository only if it is unclear. I want the current HTML, including saved site changes.
2. FNJ MCP can identify the site but cannot export its files or push to GitHub. If you have authorized browser access, use the site's Push to GitHub action in my FNJ dashboard. I will enter any GitHub token directly in FNJ, never in chat. FNJ writes to the fnj-export branch under fnj-site/ and leaves the default branch alone.
3. If you cannot use the FNJ dashboard, ask me for a current Download ZIP and use your authorized GitHub connection to add its files to a dedicated branch. Do not request a GitHub token in chat. Do not overwrite existing repository files without checking with me.
4. Verify the repository, branch, commit, and key files, then give me their links. A GitHub push stores the code; it does not itself make the website live. Tell me what remains for a public deployment. Do not claim success without a real commit.

04 / USE BOTH

Publish the site.
Keep the source.

Deploy the static site to Cloudflare from FNJ, then push the current HTML to GitHub. You get a live URL and a copy of the code in your own repository.

FNJ conversion
→
Cloudflare Pages
+
GitHub branch

Ready for the next step?

Open your site in FNJ, review it, and choose where to publish.

Go to dashboard
More agent prompts Convert another site

Ready to convert your website?

Paste your published Framer URL to generate a production-ready project in minutes.

Example: https://your-site.framer.websiteYour published site’s address — the one visitors see. A custom domain works too.