v1.0.0

Documentation version

Currently searching v1.0.0

Search pages, component props, utilities and tokens.

↑↓ to move to openesc to close

Open files in your editor

On a Mac, right-click the folder in Finder, hold Option, and choose Copy as Pathname.On Windows, hold Shift, right-click the folder, and choose Copy as path, then delete the quote marks.

GuidesLumos 1.0.0

Importing a Webflow site

Move a Webflow site to Lumos while preserving its design, content and history.

The lumos-import-webflow skill treats a migration as a measured substitution. It keeps the exported HTML, CSS, JavaScript and content as evidence, then replaces Webflow variables, classes and components with their Lumos equivalents. The finished site should match the published site before the Webflow code is removed.

Collect the source material

  • The published URL, kept live until the new site is ready.
  • An unzipped Webflow code export.
  • A CSV export for every CMS collection.
  • The existing 301 redirect CSV from Webflow Site Settings.
  • Access to the Webflow project for component props, CMS bindings, filters and motion.
  • Decisions for Ecommerce, Memberships, Logic and native search, which have no automatic one-to-one replacement.

Scan before changing anything

Terminal
node .agents/skills/lumos-import-webflow/scan-export.mjs path/to/webflow-export

The report identifies the pages, shared site chrome, components, collection templates, forms, Webflow widgets, third-party libraries and embeds. Record the paths and decisions in the skill's This project section as you go; several of them cannot be recovered after the old site is unpublished.

Work in three passes

PassWorkProof
1. RebuildBring across the HTML, CSS, JavaScript, fonts, images and shared chrome.The local page matches the live Webflow page.
2. ConvertMap variables, breakpoints, classes and components to Lumos, moving local CSS and JavaScript with each component.The converted page still matches the pass-one baseline.
3. ConnectCreate routes and bind collections, forms and the chosen CMS.Content and item counts match the live site.

What done means

Every route and piece of content remains, screenshots match, redirects are flattened to one hop, and any Webflow feature that remains is named with a reason. Webflow component markup, variables, u- classes and webflow.js are gone wherever Lumos replaces them; the site's own classes, libraries and interactions remain with the components that use them.