Build your homepage with sections

Your homepage is a stack of sections. You choose which sections, in what order, with what content. This lesson gives you a starting order and explains what each section is for.

The section library#

Every theme can use the core section set. The ones you will reach for most:

• Hero. Full-width image or video, a heading and a button. Up to three per page.
• Collection list. Category cards.
• Product grid. Products from one category, with a count and a "view all" link.
• Featured product. One product with its add-to-cart button embedded.
• Banner. One to three promotional images with links.
• Image with text. A photo beside a paragraph; you choose the side.
• Rich text. Heading, text and a button.
• Testimonials. A slider of customer quotes, fed automatically from the Reviews module when it is on.
• FAQ. An accordion of questions and answers, which also outputs FAQ structured data.
• Newsletter. A signup form with the KVKK consent text you set.
• Logo list. Brand or press logos.
• Video. YouTube, Vimeo or an uploaded file, loaded lazily.
• Marquee. A scrolling announcement strip.
• Countdown. A timer to a real end date, with an option to hide when it ends.
• Custom HTML. Free HTML, sanitised; scripts are not allowed.

Modules can add their own sections. The Blog module, for example, adds a latest-posts section.

A homepage order that works#

For a new store, this order answers the questions a first-time visitor has, in the order they have them:

1. Hero. One image, one sentence about what you sell, one button to your main category. Not a slideshow of five messages.
2. Collection list. Your top categories, so visitors can pick their lane.
3. Product grid. Best sellers or new arrivals, eight products.
4. Image with text. Who you are and why you make or pick these products.
5. Testimonials. Real reviews, once you have them. Leave it out until then.
6. FAQ. Shipping time, return policy, payment options.
7. Newsletter. With honest consent text.

Add sections in the customizer, drag them into order, fill in each one's settings, and check the preview. Publish when the page reads well on a phone.

Announcement bar#

A marquee or announcement bar at the top of every page is the right place for one line: free shipping above an amount, a delivery cutoff, a holiday notice. One line, changed when the fact changes. If it says "ships in two days", it must ship in two days.

Countdowns and urgency#

Use the countdown section only for an offer with a real end date and switch on "hide when over". Kambloo does not support fake timers anywhere, and a timer that resets is the fastest way to lose trust.

Static pages#

Some pages are not built from sections. Create these as static pages in your admin:

• About. Who you are, where you are, how long you have been doing this.
• Contact. Address, email, phone, working hours. Customers and the law both expect the seller's identity to be easy to find.
• Shipping. Carriers, delivery times, costs, free shipping threshold.
• Returns. The 14-day withdrawal right and how to start a return from the customer account.

Link them from the footer. These pages do more than inform customers: Kambloo reads your shipping and return pages to suggest FAQs, and AI answer engines read them when asked about your store's policies.

Headings#

Each page should have one main heading. Themes place the page or product title as the main heading; sections use lower-level headings. Do not paste extra main headings into rich text sections.

Common mistakes#

• A hero slider with several rotating messages. Visitors read the first one, if any.
• A homepage without categories, so visitors have to use search to go anywhere.
• Empty testimonials with placeholder quotes. Leave the section out until you have real ones.
• An announcement bar that has said "launch offer" for six months.
• No shipping and returns pages, which means more support emails and weaker AI answers about your store.

Apply this in your store: build the seven-section homepage above, create the four static pages, link them in the footer and publish.