Sweet Tooth

Four headers, three scroll behaviours, one logo problem solved

The vendor's feature list gives Sweet Tooth four header types — Standard, Centered, Expanding and Minimal — and three behaviours: sticky, sticky on scroll up, and fixed. There is also a full-screen menu option, separate mobile header styling, and a control for logo size on phones.

For a bakery site this is usually the first thing to settle, because the header carries the shop link, opening hours or a phone number on every page. Multiple logo versions are supported for the default, mobile and sticky headers, with dark and light variants, so a logo that reads well over a pale hero image does not have to be reused on a coloured sticky bar. The vendor also lists multiple widget areas inside the header, which is where you would put a small cart, a search field or a short notice.

Which of the four types suits your shop is a design call the description does not make for you. The demo at sweettooth.qodeinteractive.com is where to see the Centered and Expanding variants in use before committing.

The shop is built from product shortcodes inside pages

Sweet Tooth declares WooCommerce compatibility, and the way it puts products on a page is through named shortcodes: Product List, Product List – Carousel, Product List – Simple, and Product Info. A WooCommerce Dropdown Cart widget sits alongside them, plus a Banner shortcode and a Call to Action shortcode.

The distinction matters for how you work. Standard WooCommerce shop and single-product templates handle the catalogue itself, and the changelog records template-level maintenance for them over the years — a fix for single product star ratings in 1.10, for example. But the sections that sell on a homepage or a seasonal landing page are compositions of these shortcodes, placed wherever you want them in a WPBakery row.

That gives you a carousel of bestsellers in one band and a simple grid of three signature cakes in another without duplicating a product four times. It also means the merchandising layout lives in the page, not in a widget area, so changing it later is a page edit rather than a theme options change.

Gallery shortcodes carry the photography, but not the photos

Cake businesses sell with images, and the feature list is heavy with ways to arrange them: Masonry Gallery, Expanded Gallery, Gallery Blocks, Image Gallery, Stacked Images, Frame Slider and Vertical Split Slider, plus an Image Slider widget and an Item Showcase shortcode. There is also a Clients Carousel, a Testimonials shortcode and a Team shortcode for the parts of the site that are not a cake.

Use the shortcode that matches the shape of your assets. A masonry grid handles a mixed set of portrait and landscape cake shots; Stacked Images and Frame Slider are for a small hero arrangement with deliberate overlap; Vertical Split Slider suits a full-height opening panel on a homepage. Each of those is a different page-building decision rather than a different setting.

The vendor is explicit that it does not own the copyright to the images used in the demos and that they cannot be reused on your site without a stock licence purchase. Treat the demo as a layout reference only, and budget for your own photography.

What version 2.0 took away, and why it is the practical detail to plan around

The October 29th, 2025 release is the most consequential entry in the changelog for anyone planning a launch. Version 2.0 removed the Elated Twitter Feed plugin and the Elated Instagram Feed plugin, citing API changes at both platforms.

The feature list elsewhere still advertises an Instagram Feed widget and a Twitter Feed widget. Both statements come from the same vendor material, and the changelog is the newer one — but the description has not been reconciled, so a reader who plans around the widget list will be planning around something no longer shipped. If a live social grid on the homepage is a requirement, pick a currently maintained plugin and place it yourself; do not count on the theme's own feed widgets.

The same release also records WordPress 6.8.x and WooCommerce 10.3.x compatibility, PHP 8.3 support, WPBakery Page Builder updated to 8.7.2 and Slider Revolution to 6.7.38. Those are vendor claims about the release, not results of independent testing. The marketplace compatibility attributes state a wider range — WordPress 6.3.x through 7.0.x, and WooCommerce 9.x and 10.x — which is where to check your own stack.

One-page anchors, boxed layouts and a border around the whole site

Beyond headers and shortcodes, Sweet Tooth exposes layout modes that change the frame rather than the content inside it. There is one-page site support with anchor functionality, which lets a single long page carry a bakery's sections — story, cakes, gallery, contact — with the menu jumping between them. There is a boxed layout option, a selectable grid size, and an optional passepartout border that draws a margin around the website.

That passepartout option is the unusual one. A visible border framing the content suits an editorial food presentation and reads as a deliberate choice; on a dense shop page it eats usable width. The boxed layout does something similar. None of these are irreversible, but they set the tone before you add a single product.

A child theme is included, which is the right place for customisation so it survives the parent theme updates the changelog shows arriving regularly.

What the assembly model suits

Sweet Tooth hands you a WPBakery canvas and a large set of named blocks: product lists in three shapes, a dozen gallery and slider arrangements, testimonial and team displays, title area variants, and the header controls above. The work is composition, and the quality of the result tracks how good your photography and your shortcode choices are.

That fits a cake shop, chocolaterie or confectionery with a real catalogue and a photographer, where the homepage needs to change seasonally and each campaign section is built from existing parts. It fits a one-page presentation site that needs anchors and a strong hero.

It is a harder fit if your team has standardised on the block editor and expects to work there, or if you want the live social feed widgets the older feature list still describes. The React-based feed tools were the vendor's own, and they are gone from version 2.0. Build around that, not against it.

Questions & answers