Understand the difference between a mockup, HTML export and Nova website Print

Quick answer

A concept image shows a design. An HTML export contains website files. A Nova project is edited through Nova’s supported tools. Keep the format you intend to maintain, and check what can be imported or published before assuming one format can be edited as another.

Keep the editable source for later changes

For a Nova project, use the Nova project editor and republish the approved update. For HTML, keep the public source and any build project. For WordPress or Joomla, preserve native content, templates, and builder data. Nova for WordPress currently creates the site and hands later editing to WordPress; it does not provide Nova-side editing of every published WordPress site.

• Edit an existing Nova project
• Revise public HTML files
• Create with Nova for WordPress and continue in WordPress

Reference: current Nova for WordPress editing boundary.

Identify what you have

• Concept image: useful for reviewing layout, colors, imagery, and content direction. It does not contain working navigation, a real form handler, or editable page source.
• HTML/static export: editable code and assets that can be previewed and published through a supported hosting workflow. Keep the source files for later changes.
• Nova project: a builder-managed website edited through the account’s Nova interface. Use the actual import/export and publishing options offered by that version and service.

Choose how future edits will work

For an external HTML project, keep one local source project and a record of the published output. For WordPress, use the CMS/editor that owns the page. For a Nova site, keep edits in the builder unless a supported export/handoff changes that workflow.

An HTML export does not automatically become a natively editable Nova or WordPress page. Ask about supported conversion/import before planning future editing around it.

Check the handoff

1. Confirm you have the source or supported editable project, assets you may use, and the intended editing tool.
2. Preview the working site on computer and phone-sized widths. Check links, missing assets, and the real submission path for forms.
3. Confirm the exact hosting destination and publishing method. Check HTTPS and the live site after publication.
4. Keep the prior working version and a note of where future edits belong. Avoid maintaining competing copies that overwrite each other.

If something is missing

Ask for the actual website files or editable project rather than only a screenshot. Provide the affected page and missing asset/function. A visual concept can guide the repair, but the published site still needs working files and supported services.

Related help

• AI website builder, AI coding tools and website services: what is included?
• Publish an AI-generated static HTML website to cPanel
• Build an Astro website locally and host the static output on cPanel
• AI Free, Starter and full hosting: understand the editing tools

Last content review: October 31, 2026. Check the version and features available in your own account.

AI editing guidance and linked workflow documentation reviewed November 2, 2026. Existing video and earlier review history retained.