Export your Strikingly HTML code to GitHub

From converted site to reviewed source

1. 01

   Select the export you intend to keep

   Convert your published Strikingly site first. Check section-based navigation and any additional public pages separately. Store and membership widgets can be visible in a capture without their hosted data or permissions moving with them. Select current HTML with saved site changes when you want the current static version. Check the preview and download a backup before handing off the files.

2. 02

   Prepare a repository you control

   Create a dedicated GitHub repository with an initial commit, such as a README. In FNJ's Push to GitHub action, enter owner/repository and a fine-grained token with Contents: Read and write access to that repository. Enter the token directly in FNJ, not in an agent conversation.

3. 03

   Review the export commit

   Open the fnj-export branch and the fnj-site/ folder. Review anchor targets and widget URLs; ensure no membership or order data is mixed with the public-page files. Review additions, changes and removed files before opening a pull request. FNJ's export keeps the default branch unchanged.

4. 04

   Choose how future changes reach the repository

   Use your code editor for repository changes. When exporting another version from FNJ, review the refreshed export branch before merging again; changes made outside FNJ may need manual reconciliation. Keep related styles and assets in the same change so previews are reproducible.

5. 05

   Configure hosting separately

   To publish the static site, deploy the folder containing index.html through your chosen host. If you configure Cloudflare Git integration, select the repository branch and directory that contain the reviewed export. Pushing a repository by itself does not configure that hosting.

Check the files in your export branch

FNJ writes under fnj-site/ on fnj-export. The static export should include index.html and its referenced page and asset files. File names and asset folders vary by capture; inspect the actual export rather than creating placeholder files.

fnj-export branch
└── fnj-site/
    ├── index.html
    ├── captured page files
    └── referenced styles and assets

If fnj-site/ already belongs to another project, use a separate repository. A later FNJ export refreshes its managed folder, so review your edits before using the export action again.

Strikingly to GitHub: questions

Does exporting Strikingly code to GitHub make the website live?

A push stores code in a repository. Publishing needs a separately configured host or deployment workflow. FNJ's export branch does not automatically enable GitHub Pages or connect Cloudflare Git integration.

Which branch and folder does FNJ use?

FNJ writes to the fnj-export branch under fnj-site/ and does not change the default branch. Review the commit before merging. Keep a dedicated repository for the exported site when practical.

Will later changes in Strikingly automatically sync to GitHub?

No. Review and export a new version when you want an update. Track section changes and related anchor links together. Document which widgets use Strikingly or third-party services, and keep membership records out of the code export. Use the repository for page changes rather than as a substitute for an access-control service.

Can my connected MCP agent push these files for me?

FNJ MCP can identify the site but cannot itself export files or push to GitHub. An agent needs authorized browser access to FNJ's GitHub action, or a downloaded ZIP and its own authorized GitHub connection. Enter credentials directly in the relevant service, never in the prompt.

Continue with the right setup

Converting requires a signed-in FNJ account and current conversion access. Review FNJ pricing for purchase terms. For help using your own agent, follow the deployment guide and prompt library.

Improve the exported site before launch