HTML import
Import an HTML template into WordPress: the file becomes a page of blocks, its CSS becomes settings
A template you bought, a page from an agency, a draft from another tool: upload it, and it stands as a page of blocks — with the fonts, colours and spacing of the template, each of them a setting you change in the editor like on any other page. No foreign CSS lies on the page. What the template could only do with a script is listed afterwards, with the block that takes its place.
What comes in
- Sections, groups, headings, text, buttons, pictures, lists
- Tabs from a tab strip, accordions from details, tables with a head row and a side column
- Header and footer as templates that apply everywhere; the nav as a menu template with its submenus
- The pictures from the zip or from the web, into the media library
- Google fonts with their weights, the colours and the width of the template as those of the site
What the CSS becomes
- Every rule a setting on its block: spacing, size, colour, radius, shadow
- Hover and focus as states, narrow widths as variants
- A style block in the page or a linked style.css — both
- Breakpoints the builder does not know are moved to its own
- What finds no block is named — not silently dropped
What you do afterwards
- Build the form under Forms and put the form block in its place
- Enter a video as the Video block instead of an iframe
- Replace a slider with Reviews or a Carousel
- Look through it once on a phone
- Publish
The dialog
One file, three decisions.
Under Pages → "From a template" you pick the .html or the zip, name the page and say what the file shows: a page, a single post — it then becomes the template for every post — or a list, which becomes the template for the blog. And whether the header and footer of the template should become the header and footer of the site.
The result
What was built, and what to know.
After about twenty seconds you see how many blocks the page is made of, which templates came with it — menu, header, footer — and a list of what the importer had to leave aside: a script, a form, a rule without a block, a moved breakpoint. Every entry says what builds it in ambera.
In the editor
Every setting is yours.
The page stands as a draft in the editor. Click the heading and you see its size, its font and its colour as classes — the same ones every other block carries. Change, move, delete, put a block of your own in between: the page belongs to you, not to the template.
Questions
Which templates work?
Any .html file with its CSS — in a style block or in a linked style.css — on its own or as a zip with the pictures beside it. Pictures from the web are fetched into the media library. The cleaner the template, the better the result: a page of sections with headings and paragraphs comes in almost completely, one made of absolutely positioned layers does not.
What stays behind, and why?
Scripts, because a layout of blocks holds no JavaScript — the blocks bring their own behaviour. Forms, because the site decides where something is sent; they stay as an HTML block until you have built the form under Forms. iframes, because the Video block is there for that. And single rules that only a script sets, such as the active tab — the block has its own setting for it. The list after the import names each of these.
Does the page look like the template?
Yes — we measure it. Our test photographs the template and the imported page at 1400 and 390 pixels and compares the pictures, counts the words and checks font and colour of every piece of text. A deviation is a bug we fix, not a quirk of the template.
Can I build a post or the blog from a template?
Yes. "What the file shows" knows three cases: a page; a single post — the first heading becomes the title, the running text the content, the date the date, the picture the post image, and it becomes the template for every post; a list of cards — it becomes the template for the blog, the first card the template for every entry.
Is this in the free version?
Yes. The import belongs to Light like the editor itself. What the imported page would need in Pro blocks — a shop, a member login — needs Pro; the page itself does not.
The WordPress theme builder has a name.
Built in Switzerland. Built for WordPress.