Read this before you quote the work
A good destination when the site is mostly content and the owner wants files in Git rather than rows in a database. The export becomes the theme; Markdown becomes the content.
The order that works
- 1Create the site: hugo new site my-site
- 2Make a theme directory and place the exported HTML in themes/exported/layouts/.
- 3Split the markup into baseof.html, single.html, and list.html at the natural boundaries.
- 4Replace body content with the {{ .Content }} placeholder and move the copy into content/*.md.
- 5Copy assets into static/ so their exported paths continue to resolve.
What you keep
- Design, CSS, assets
- Build output that is pure static files
What you rebuild
- Framer runtime interactions
- Any dynamic behaviour beyond CSS
The mistake to avoid
Skipping baseof.html and pasting the full page into every template. Hugo will build it, and the shared chrome then drifts between page types within a week.
Questions
›Can I import a Framer site directly into Hugo?
A good destination when the site is mostly content and the owner wants files in Git rather than rows in a database. The export becomes the theme; Markdown becomes the content.
›What transfers from Framer to Hugo?
Design, CSS, assets. Build output that is pure static files.
›What has to be rebuilt?
Framer runtime interactions. Any dynamic behaviour beyond CSS.
›What is the most common mistake on this migration?
Skipping baseof.html and pasting the full page into every template. Hugo will build it, and the shared chrome then drifts between page types within a week.