Wix HTML: maintain CMS content after exporting a website

Maintain CMS content after exporting a website

1. 01

   Audit content and existing URLs

   List public article or item paths and compare them with the capture report. Separate missing pages from missing CMS functionality. Keep an authorized export or backup of structured records from the original system when available; the public page capture is not a database backup.

2. 02

   Choose a future publishing model

   For a small static site, maintain article files and an index in your repository. For structured content, use the CMS workflow supported by your saved FNJ site or a service in your own account. Define fields such as title, slug, body and image, and avoid copying private records into public page files.

3. 03

   Verify what the FNJ collection can publish

   Ask list_collections for publishesPages and routePrefix, then list_items for the current content. create_collection creates storage fields; it does not automatically bind an item-page template. Read the returned field keys before create_item. If no publishing template exists, render a listing with add_section or clone an existing route with create_page, then adapt its content.

4. 04

   Test one draft before scaling

   Create one clearly labeled draft item or page and check its content, path, title, image and navigation. Confirm that a published item really has a reachable URL before importing more. Verify a listing links to the right route and that updating content changes the intended page. Keep the original CMS available until this workflow is demonstrated.

Give your agent a clear starting point

Copy this prompt for your connected agent and fill in the project details. Tasks that inspect browser requests, edit downloaded files or configure another service may need your agent's own browser or code tools. FNJ MCP alone does not configure those external services. Keep credentials in the relevant account's setup screen, never in the prompt.

Source: Wix. Output: static HTML, not the original builder workspace.

Inspect CMS content for my FNJ site [site ID] with list_collections and list_items. I need [collection name] with [fields] and pages under [path]. Report publishesPages, routePrefix and the actual field keys before creating anything. Do not assume create_collection binds a page template. Propose a supported publishing plan, then create one draft example using an existing styled route when needed. Show its preview and URL; do not bulk import or publish before approval.

Platform checks: Wix CMS, member records and booking data are not exported by capturing a public page. Inventory visible content and obtain authorized structured data separately when needed. Rebuild missing dynamic sections or choose a new CMS workflow; verify a real item page instead of treating a successful fetch as a collection migration.

Verify the result before launch

• ✓Captured item URLs match the content inventory.
• ✓Collection storage and page publishing are distinguished.
• ✓A new test page can be reached directly and from its listing.

Use the final hosted preview as well as the saved FNJ draft. Keep a backup of the reviewed files, record what remains external and test the important customer action on the final domain. A draft edit, downloaded ZIP and live site can represent different versions until you export and deploy the intended one.

Common questions

Does a captured CMS article remain editable?

Its captured HTML is editable, but that is different from editing the original collection database. Choose how new articles, indexes and item pages will be created and published, and verify one complete example first.

Can I cancel Wix hosting right after exporting?

First verify the content, assets, routes and business actions on the replacement host. Compare the preview with Wix at two screen widths and verify galleries, booking links and important page content before switching traffic. Keep or replace external dependencies before relying on the new site.

Where do these HTML changes get deployed?

Use a compatible static host in your own account. FNJ supports deploying the saved site to your own Cloudflare Pages account, and exporting code to your own GitHub repository. A GitHub push stores code; configure hosting separately and confirm the reviewed version is what visitors receive.