Skip to content

Maison Template: An Editorial Home Goods Storefront

Maison Template: An Editorial Home Goods Storefront

Maison is one of the five store templates in Zugo: an editorial shop for ceramics and home goods, with a product grid, a working cart drawer, a sign in screen and a customer account area. Cloning it into your own project is free and calls no model, so credits start only at your first edit.

Below is what the template actually contains, which parts function and which are placeholder, and what it takes to turn a storefront page into a shop that takes money.

What does the Maison template include?

The storefront runs the full length of a considered ecommerce page. A hero with a seasonal line and a product still, a trust strip, an everyday collection grid, a featured capsule collection with its own story, a founders section, a journal signup, and a footer organized by category with care, shipping and returns links.

The cart is real interface, not a picture. Adding an item opens a drawer with the line items, a subtotal, a shipping line, a total and a checkout button, and a small confirmation appears when something is added. The item count in the header updates with it.

Behind the account link sit two more screens: a sign in form, and a customer area with an overview greeting, recent orders, a saved items list, a profile block with a default shipping address, and lifetime totals. It is the standard shape of a direct to consumer account page, already assembled.

There is also a journal view, which matters more than it sounds. A shop that publishes has somewhere to send traffic that is not a product page, and the template treats that as part of the store rather than a bolt on.

Why does this storefront lead with a story instead of a grid?

Because the template is built for a brand that competes on character rather than on price. The founders section tells a small specific origin story, and the product copy talks about who made each object and where. That is deliberate positioning, not decoration.

It matters when you rebrand. If you sell something where price and specification decide the purchase, tools, parts, electronics, this structure fights you and Volt is the better starting point in the same category. If you sell something where the buyer wants to feel something about the object, this structure does most of the persuasion for you.

The practical test is simple. Ask whether your customer would read two paragraphs about how a product is made. If yes, keep the story blocks and pour your own into them. If no, your first edit should be replacing them with specifications and comparison.

What works and what is placeholder?

Worth being precise about, because a store page raises money questions immediately.

Element What it is What makes it real
Storefront, all sections Real, publishable page Nothing, swap the copy and images
Cart drawer, add to cart, totals Working interface Nothing for display purposes
Checkout button Visual, no payment is taken Connect Stripe
Sign in screen Layout only, accepts anything Connect Supabase for real accounts
Order history and lifetime totals Placeholder figures Connect a database, then several edits
Review counts, maker counts Placeholder copy Replace with your own true numbers

That last row is not a formality. The template ships with invented review counts and studio counts belonging to a fictional brand, and publishing them as your own is both dishonest and easy to check. Replace them in your first pass, even if the replacement is a smaller number or nothing at all.

How do you turn Maison into your own shop?

You describe changes in chat and the page rebuilds. Five edits do most of the work:

  1. Brand and category: "rename the shop to Kiln, sell handmade tableware only, rewrite the hero and the founders story".
  2. Products: "replace the eight products with my six, use these names, prices and short descriptions".
  3. Palette and type: "cooler palette, off white and slate, a serif headline and a plainer body face".
  4. Structure: "remove the capsule collection block and put a bestsellers shelf in its place".
  5. Trust: "replace the trust strip with delivery time, returns window and a materials note".

Do them one at a time. Every rebuild is opened in a sandbox before it reaches you, so a build that fails to render is never delivered, which makes trying a structural idea cheap. Product images are worth handling early: a store template lives or dies on photography, and good structure cannot rescue weak photos.

What does reshaping Maison cost?

Cloning runs no model, so copying the finished storefront into your own project costs nothing.

Action Credits Note
Clone the template into a new project 0 Copy of a finished page, no AI involved
One edit in chat 3 Products, copy, palette, structure
Full rebuild of the storefront 6 When the result should not resemble Maison
Multi page platform, first three pages 12 Shop plus journal plus policies
Each additional page 3 Category pages, care guide, about
Edit in Hi-Fi mode 6 Hi-Fi costs double throughout

The Free plan gives 5 credits, enough for the clone and one edit, which is usually enough to see your own products in the grid. Pro is $25 a month for 200 credits, Business is $99 a month for 800. On Pro that is around 66 edits or 33 full rebuilds in a month.

A real rebrand of a store tends to run longer than a landing page: six to ten edits is normal, because products, copy, trust content and structure each need a pass. Budget accordingly rather than being surprised in the middle.

Can Maison actually take money?

Not on its own. The cart works as an interface and the checkout button is a visual until you connect Stripe, which is one of Zugo's built in integrations and handles both one off payments and subscriptions.

Once Stripe is connected, the practical questions become the boring ones that decide whether a shop functions: what happens to stock levels, how shipping is priced by destination, how a refund is issued, what an order confirmation email says. Zugo can build a good deal of this, and Resend covers the emails, but each piece is a conversation of edits.

If you are weighing whether to run a store this way at all, does it work for ecommerce is the honest version of that question, and can I sell what I build covers ownership of the result.

Who is this template right for?

A small brand with few products and a strong point of view. Ceramics, textiles, candles, coffee, stationery, anything where a maker story is part of the value and the catalog fits on one page comfortably.

It also suits a launch page for a single collection, where the goal is a drop rather than a permanent catalog. Strip the account area, keep the story and the grid, and the template becomes a focused campaign page.

It suits a large catalog badly. A shop with hundreds of products needs search, filters, categories and inventory management, and that is a platform rather than a storefront. Start from the multi page path instead, and read how to build an online store with AI before committing to a structure.

What are the honest limits?

Three worth naming.

The account area is a picture until it is wired. Real orders, saved items and addresses require Supabase and several edits of work, and the logic around orders is genuinely fiddly.

Inventory is not managed. Nothing decrements when an item sells, and nothing prevents overselling. For a small maker running limited batches that is often tolerable; for anything at volume it is not, and it is the first thing to build after payments.

And a complex catalog stays complex. Variants, size guides, bundles, regional tax and shipping rules: Zugo does not replace a development team on a store of that shape, and it does not replace a dedicated commerce platform either. On a small honest catalog it is faster than both.

How do you publish it?

Publishing puts the shop on an address like your-project.zugo.run in one action, and the build is verified in a sandbox first, so a store that does not render is not published quietly. A simple build takes about a minute; a multi page platform takes a few minutes.

A custom domain connects on paid plans, and for a shop that matters more than for most projects: people judge whether a storefront is real partly by its address. Google Analytics shows which products get opened, which is the fastest way to learn what your grid should lead with. GitHub export hands over the source as a real repository, and Vercel deploys to your own account.

Where should you start?

Open the gallery, filter to stores, and look at Maison next to Glow Lab, Volt, TKAN and Verdant before choosing. They differ in structure and tone, and picking the closest one saves more edits than styling ever will.

Then start with products, not with color. A grid filled with your real items and real prices tells you immediately whether the layout suits your catalog, and every styling decision made before that is a guess you will likely redo.

You can clone Maison and start filling it with your own products at zugo.dev. The starting credits are enough to see your shop with your name on it and decide whether to keep going, with no card required.

← All posts