Blocks
Build your page from pieces that don’t break when you move them
Hero, gallery, testimonials, FAQ, form, featured products. You choose which blocks each page carries, in what order and with what content. How each piece looks is written by your team or by the AI. No canvas, no boxes that slip out of place, and no website that only its maker understands.
Step by step
How a page actually gets built
No dragging boxes around until they line up. You pick the sections from a list, write what they say and decide the order they go in. How each one looks is already solved.
-
You pick the sections
Open the page, press “add block” and choose from a short list. A services page is usually a hero, some text, three highlights, an FAQ and a form.
hero · text · gallery · FAQ · form
-
You fill in their fields
Each block asks for what it needs and nothing else: a title, some copy, an image from your library. If a required field is missing, the panel tells you when you publish, not afterward.
title · copy · image with its alt text
-
You put them in order
Move the form up, push the gallery down, drop the testimonials until you have some. Reordering is moving a row: there’s nothing to knock out of place because there’s no canvas.
up · down · out
-
You publish
Until then it’s a draft only you can see. When you publish, the page joins your site, your sitemap and your menu if you put it there.
draft → published
How each piece looks isn’t part of those four steps. That’s your theme’s code, and your team or the AI changes it without touching a comma of what you wrote.
The catalog
Fourteen blocks, and each one knows how to draw itself
A block has two halves: the fields you fill in, defined in the core, and the component that draws them, written in your theme. You touch the first from the panel; the second is changed by your team or by the AI.
-
Hero, text, image and gallery
The basics of any page. You write the title and the copy, pick the image from your library — alt text required, focal point included, so a crop on a phone doesn’t cut off heads — and the theme decides where each thing goes.
-
Testimonials, logos and highlights
The trust sections. A testimonial is a record with its quote and its name: fix the quote on Tuesday and the site shows it on Tuesday, without touching the design or republishing the whole page.
-
FAQ
You write the question and the answer. They’re drawn as expandable items that open without JavaScript, and the FAQPage data Google reads to show them in search comes from those same questions. Nobody writes that code by hand.
-
Form
You choose which of your forms goes on the page. The block walks through its fields, so it can’t invent one or drop a required one: add “how did you hear about us?” and it shows up without touching the design. The submission goes to the core, never to the theme.
-
Featured products
Pick specific products or a rule, and the grid resolves against what’s published. Unpublish the rain boots in October and they disappear from the home page without anyone editing the home page. The price shown is the price charged.
-
Pricing, CTA, video and divider
A plan table, a button with its line, a YouTube video and a divider for breathing room. And if a page carries a block the server doesn’t know, it’s skipped: the page is served anyway and the visitor never sees an error.
The catalog, in numbers
A closed catalog is what keeps everything in place
- blocks ready to use, from the hero to featured products
- 14 blocks ready to use, from the hero to featured products new ones are written by the team
- halves in every block: the fields you fill in and the component that draws them
- 2 halves in every block: the fields you fill in and the component that draws them schema in the core · component in your theme
- levels of nested menu, with one document per menu so two people never step on each other
- 3 levels of nested menu, with one document per menu so two people never step on each other header · footer · whatever you need
- errors on screen when a block is missing: if your theme doesn’t have it, the base theme’s is used
- 0 errors on screen when a block is missing: if your theme doesn’t have it, the base theme’s is used and if the server doesn’t know it, it’s skipped
Content and design
Ask for “a testimonials section” and watch what happens
The testimonials block already exists in the catalog, so the AI adjusts or writes its component in your theme. For that section to show up on your home page, the block has to be added to the page, and that’s content: the panel offers it as a button, you press it with your own permissions, and it’s logged as a content change. The line isn’t crossed, not even for convenience.
- If the model writes your title inside the component, the version is rejected.
- Change a text in Pages and the site shows it. No regenerating, no credits spent.
- What it looks like, the AI changes. What it says, you do.
change «the button in yellow»
change «a dark background»
change «the title on the left»
change «a bigger title»
change «a rounded button»
From the panel
Move a block at three in the morning and nothing breaks
Every block draws itself with its own content and knows nothing about what sits above or below it. That’s why moving the form up, dropping the testimonials or slotting a gallery into the middle is moving a row in a list, not a redesign. There are no overlaps to fix and no phone layout to check afterward: that’s already written into the theme.
-
If your theme doesn’t have a block, the base theme’s is used
Never a blank gap or an error message. And the day someone writes yours, it takes over without touching a single page.
-
Fields are validated on save, not when you look at them
A link with a strange address, an image with no alt text or data from another account never gets saved, whether it arrives through the panel or the API.
-
Every save goes into the content history
With its author and its date. If someone leaves a page half done on a Friday, you go back to Thursday’s version and get on with your life.
- Pages
- Posts
- Media
- Store
- Forms
- SEO
Pages
Home
Page blocks
- Hero
- Featured
- Testimonials
- Form
- FAQ
Your page is assembled from blocks. The design of each piece is code you can open, compare and roll back.
Questions
What people ask about blocks
Is this a visual builder, like Elementor?
No. In a builder you drag boxes around a canvas and the result is data from that canvas. Here you pick blocks from a catalog, order them and fill them in; how each block looks is a code file your team or the AI can open, read, compare and roll back. The assembly is blocks; the design of the pieces is code.
Can I ask for a block that isn’t in the catalog?
Yes, and the team writes it. A new block brings new fields, and fields are defined in the core so they stay typed and validated. The AI can change how any block looks and create helper pieces inside your theme, but it doesn’t invent fields: if a change needs a piece of data that doesn’t exist, it tells you instead of making it up.
What happens if I move a block or remove it?
Nothing that breaks the page. Each block draws itself with its own content, so you can reorder or remove them from the panel without touching the design. If a page carries a block your theme doesn’t implement, the base theme’s is used; if the server doesn’t know it, it’s skipped.
What if I need one more field on a post or a product?
You can have it, and it doesn’t take a new block. Our team defines custom fields for your account — visiting hours, a license number, a spec sheet — and they show up in their own tab in the editor for you to fill in. Your theme reads them and the AI can draw them, but neither you nor it invents them: the team defines them so they stay validated.
Can I paste HTML or third-party code?
There is an html block, but only our team can edit it, and it’s sanitized on save: no scripts or inline styles, and frames only from a list of allowed domains. Pasting code without checks is the fastest way to break a website, so it isn’t within reach of an editor or the AI.
Do the blocks look right on a phone?
Yes. Every component is written responsive from the base theme up, and the AI receives the accessibility and animation rules along with the data contract. The first screen has to be fully readable without JavaScript; a site that can’t be read without it counts as broken, whoever wrote it.
What about a link to a page I haven’t published yet?
It isn’t drawn. A link to a draft reaches the theme without an address and the theme doesn’t show it, so a broken link to something that doesn’t exist yet never appears. When you publish the page, the link shows up on its own.
Your first page, built this afternoon
A site at yourname.wixy.app, with blocks, forms, SEO and 50 credits a month. Free forever, and no card needed.