Usage

The homepage

After activation the Grove layout has these homepage blocks (all of them on, edit them in Design → Layouts):

Block	What it shows	How to edit
Grove top note	Two notes and a link in the top bar	Block content (HTML)
Grove hero	Headline, buttons, three facts, an arch with sun, botanicals, products and a ring seal	Block content (HTML); keep the classes
Grove: shop by concern	Pills that search your catalogue for “dry”, “dull”, “redness” …	Block content: change the labels and the q= words
Shop by *ritual*	Ritual arches (block template “Ritual arches”)	Categories block: pick the categories; settings: label, text, 3 or 4 arches
Bestsellers	Arch cards (block template “Arch product grid”)	Products block: filling, 3 or 4 columns, label
Three steps, *ten* minutes.	Ritual steps (block template “Ritual steps”)	Products block with three products; settings: label, text, set title, note
Grove: ingredient spotlight	Ingredient of the month and four garden seals	Block content (HTML)
Ritual notes / Kind words	Journal posts and customer quotes	Blog and Testimonials blocks
Grove: our promises	Four promises with icons	Block content (HTML)

A word between asterisks in a block name (Shop by *ritual*) is set in italic as the accent word of the theme.

On Multi-Vendor the layout also shows Featured Vendors as quiet vendor cards.

Ritual steps

Choose three products in the block (Products block → template Ritual steps, filling Manually). The first three are the steps i, ii and iii. The label above each step is “Step one/two/three” plus the first part of the product feature RITUAL_STEP (Cleanse|60 seconds → “Step one · Cleanse” and the timing “60 seconds”); without the feature the size is shown. The set box lists the three products and the sum of their prices; Add the ritual to bag adds all three in one go (products with a select option go in with the option’s first variant, the one the product page preselects). A set discount (“save 10 %”) is a cart promotion of your store (Marketing → Promotions, e.g. “the cart contains these three products”); Grove only shows the sum, so the texts stay true.

Product data the cards and product pages use

Create these product features (Products → Features, type Text unless noted, set the Feature code):

Feature code	Example value	Where it shows
KEY_INGREDIENT	Rosa canina	Latin name under the card name and the product title; the ingredient seal. As a Select feature whose variants have images, the seal shows the variant image; otherwise Grove picks a botanical illustration by name (rosehip, rose, lavender, chamomile, calendula, aloe, eucalyptus, oat, sea buckthorn, mint/nettle, cedar/vetiver, olive/squalane, primrose, minerals/clay, jade/quartz, honey)
SIZE	30 ml	Card meta row and the line under the product title
CLAIMS	Cold-pressed, Vegan, Recyclable glass	Up to four claim icons under the buy box; the first two also run round the ring seal on the product image
RITUAL_STEP	Treat|3 drops	Ritual steps block
INSIDE_1, INSIDE_2, INSIDE_3	Rosehip seed oil: softens dry patches.	“What is inside” band on the product page
HOW_TO_USE	Cleanse: massage onto dry skin | Press three drops: warm the oil and press	“How to use it” steps on the product page

RITUAL_STEP, INSIDE_* and HOW_TO_USE are hidden from the stock Features tab because Grove renders them. Products without these features simply show no seal, no Latin line and no extra sections.

Images. Cut-outs or product shots on a plain light ground work best; square images, product in the lower two thirds (the arch crops the top corners). Grove asks CS-Cart to keep PNG transparency in thumbnails, so transparent PNG cut-outs sit directly on the arch colour.

Category pages

The category image appears in a wide arch next to the title and description. The Grove: not sure tile block (category page layout) moves into the product grid after the second card; edit its text and link in the block content or disable it.

Refills and subscriptions

The comps show a “refill every 12 weeks” purchase type. CS-Cart has no subscriptions in the core, so Grove does not show it. A subscription add-on can use the styling contract .gr-ptype (radio cards, see the developer notes).