Home page content structure

The content of the store's homepage is edited in the CMS in the control panel. The homepage is built from blocks: some of them are completely filled in by you, some display the store's own information, and some belong to the developer. The guide will help you identify the type of block, choose the right editing place, and check when you need the help of a developer before publishing the content.

Where to find the content of the homepage

Open CMS → Contents . The content of the home page is content attached to the store's existing home page, not a new page: it does not have its own address. The new home page content is created by selecting New Content and using the Section template, with Home as the Targeting value.

Separate information pages and blog articles have their own templates Page and Blog in the same tool. So don't look for the front page in the page list.

The content is first saved as a draft. The editor confirms the draft save , and the content appears as a draft in the list. Unpublished content is not yet visible in the store: if you open the public address before publishing, the store displays a page not found page. This is expected.

The front page is a stack of blocks

On the left side of the editor are the Insert and Layers tabs . Insert provides blocks grouped together, and Layers shows Blocks already added to the page, which you can arrange. A blank page prompts: add a block from the left to start.

You can duplicate and delete a block. To add content to list-style blocks, use the Add Row function, and arrange rows using the Move Up and Move Down functions.

Three block types

Blocks are grouped under the Add tab. This grouping helps you distinguish between content that you can fill in yourself, content that comes from store data, and embeddings that require developer assistance. First, identify the source of the block's content: your own text and images are edited in the block, but content from store data is not overwritten by hand. To add code or an external frame, developer assistance is required.

1. Blocks that you fill in yourself

The Home , Content , Media , and Layout groups contain blocks where you can customize everything: images, titles, text, button text, and links. Edit the visible content of these blocks directly in the editor. In addition to the image, check the title, other text, button text, and link target to ensure that different parts of the block correspond to the same campaign or message. Check the whole thing in the preview before publishing.

2. Blocks that display store-specific information

The Online Store group contains blocks that retrieve content from the store. You choose what and how much to display, for example a category or a filter; the content is generated by the store. The product name is not written in such a block. If the block displays the wrong product, the correction is made in the product information, not on the home page.

3. Blocks that belong to the developer

The Embed group, as well as the Custom Script block and Code field, introduce code or an external frame to the page as is. They can break the page, slow it down, or cause a security issue, and the effects are not visible in the editor. Ask a developer for help with these instead of trying them yourself. In your request, please specify what the embed or code should display on the front page and which external service it is related to.

What do you do yourself?

• You add a new block to the homepage and select the appropriate block type for the purpose.
• You rearrange the blocks and remove the unnecessary ones.
• You change the images, titles, texts and links of your own blocks.
• You add and remove rows from the lists: another banner, another image, another lift.
• You schedule campaign content with Start and End values, which will cause the content to appear and disappear on its own.
• You do the same for each language in your store. The Language Region filter in the content list shows which language the content belongs to.

A value left blank in one language will appear blank to the customer. It will not be charged in the other language.

When to ask a developer

• The element you want does not exist as a block. The new block type is a development, not a setting.
• Spacing, alignment, size, or color appear incorrect. These cannot be fixed with blank blocks of text or spacers; they mask the real problem and degrade the page.
• The block that displays store information shows the wrong things.
• The page looks correct on a computer and incorrect on a phone.
• You are about to implement a block that requests a code or external address.

The request is a normal outcome, not a failure. Navigating the missing block produces a page that no one can maintain.

Four practical rules

• The block for one item looks broken. Carousels only show arrows and dots when there is more than one item. Add more rows.
• Select an image using the editor selector. A handwritten image address can display a placeholder image instead of failing visibly, making the page appear complete when it isn't.
• Preview in the editor and publish separately. The editor will tell you when there are Unpublished changes on the page. Publishing is done with the Publish action, which is different from saving.
• Give the change a moment to take effect before checking it in the public store.