Read this before you quote the work
The lowest-ceremony generator on this list. Point Eleventy at a folder of exported HTML and it will build it as-is; templating is something you introduce later, only where you want it.
The order that works
- 1Install: npm i -D @11ty/eleventy
- 2Drop the exported HTML files into src/ and configure that as the input directory.
- 3Add .eleventy.js declaring passthrough copy for the asset and font folders.
- 4Introduce a base layout in src/_includes/ and add a layout key to each page's front matter.
- 5Build with npx eleventy and deploy the _site folder anywhere static.
What you keep
- Everything a static export contains, with no conversion step
What you rebuild
- Nothing for a static site
The mistake to avoid
Forgetting passthrough copy. Eleventy only emits files it knows how to process, so images and CSS vanish from the build output while the HTML looks fine locally.
Questions
›Can I import a Framer site directly into Eleventy?
The lowest-ceremony generator on this list. Point Eleventy at a folder of exported HTML and it will build it as-is; templating is something you introduce later, only where you want it.
›What transfers from Framer to Eleventy?
Everything a static export contains, with no conversion step.
›What has to be rebuilt?
Nothing for a static site.
›What is the most common mistake on this migration?
Forgetting passthrough copy. Eleventy only emits files it knows how to process, so images and CSS vanish from the build output while the HTML looks fine locally.