Pages and Structure

Where to find: On the left of the top toolbar, the page name next to the store name (opens a menu when clicked) and the / / buttons next to it Who it's for: Those who want to add new pages (About Us, Campaigns, etc.) to their store or edit existing pages In short: Here you manage which screens your store consists of. You select, create, edit, and delete pages; you also switch to the shared Header/Footer Structure from here.

What does it do?

Your store consists of multiple pages (screens): the Home Page, the Category Page where products are listed, the Product Page that shows a single product, and the Custom Pages you can add (for example "About Us", "Contact"). There is also the Header Structure (the menu at the top) and the Footer Structure (the footer at the bottom) that appear in common on all pages.

The tools in this section let you switch between these pages and manage them.

Page Selector (dropdown menu)

On the top toolbar, next to your store name, the name of the page that is currently open is written. When you click on it, a menu opens downward.

In the menu:

1. At the very top there is a search box: Search page... If you have a large number of pages, you can quickly find one by typing its name.
2. The pages are grouped under two headings:
   • Pages — Home Page, Category, Product, and your custom pages.
   • Structure — Header Structure and Footer Structure (the shared sections).
3. A checkmark () appears next to the page that is currently open. In addition, a small amber dot appears next to the name of any page that has unsaved (unpublished) changes, so you can see at a glance which pages have pending changes.
4. When you hover over each page row, a small icon appears for editing () that page. The delete () icon appears only on Custom Pages — your store's system pages (Home, Category, Product, Brand, Tag, Search, Blog, Blog Article, Cart, Checkout, Account, Login/Register, Form, Review, 404, Error, Maintenance, Header/Footer Structure) cannot be deleted. See the Deleting a Page section below.
5. At the very bottom there is the Create New Page option.

When you click on a page, the editor switches to that page and the content of that page appears on the canvas.

You can see which pages have pending changes right in this list: an amber dot next to a page name means unsaved changes, and a blue dot means a saved but unpublished draft. The same information is listed by name when you hover the status indicator in the top bar.

Page types

When creating a new page you select a type. The types are as follows:

The (New Page) button on the toolbar starts creating a Custom Page directly; this is the most frequently added type.

Category page

The category page is now block-based as well: you arrange the breadcrumb above the product list, the heading area, the filter panel and the toolbar by dragging and dropping, just like the Home Page. There is a single template and it is used for every category; its content (category name, description, products, filters) fills in automatically based on the category the visitor opens.

The component library holds seven blocks under the Listing Blocks heading:

Of these, Category Intro appears only on the Category Page. Category Breadcrumb appears on the category, brand and tag pages, and the remaining five (Filter Panel, Toolbar, Product List, Active Filter Summary, Inline Promo) can also be used on the Search Results page; for example you cannot add the Filter Panel block to the Home Page.

In the default layout the filter panel sits in a narrow left column while the toolbar and product list fill a wide right column; this layout is built with the Grid block, so you can change the column widths and the mobile/tablet behaviour however you like. As with every other block, you can also make device-specific (desktop / tablet / mobile) adjustments; see Cihaz Bazli Ayarlar.en.

Every setting of these seven blocks is documented on its own page: Liste Sayfalari Bloklari.en — which block applies to which pages, plus pagination, sorting and inline promo settings.

Which category shows in the preview?

While you edit the category page, a preview category picker sits in the top-right corner of the canvas:

• Ready-made sample categories — three come built in: Main category (12 products, subcategories, brand and material filters), Subcategory (parent and breadcrumb filled in) and a Colour/size filtered category. These are representative data prepared by Treyza; they are not part of your catalogue and are never shown to visitors.
• Pick a category from my store… — choose one of your own categories to see the template with real data.

If you pick nothing, the editor opens with the sample category, so you can see how the page will look even while your catalogue is still empty. While sample data is shown, an explanatory strip appears above the canvas and a ÖRNEK (sample) badge appears next to the category name — you will not confuse it with your real products.

ℹThe same picker exists on eight page types (product · category · brand · tag · blog · blog article · search · form) and sample data never reaches your live site. For the full story see Tuval Ve Onizleme.en.

Brand and tag pages

Brand (/brand/...) and tag (/tag/...) pages are block-based too and use the same listing blocks as the category page: category breadcrumb, filter panel, toolbar, product list, active filter summary and inline promo. Each has a single template; the content (brand name, logo, description, the tag's products, filters) fills in automatically based on the brand/tag the visitor opens.

In addition to the listing blocks, the component library holds three blocks under the Brand & Tag Page heading:

The Curated Strip can be used on both the brand and tag pages; the other three appear only on their own page type. In the brand page's default layout the brand filter is turned off in the filter panel (you are already inside a single brand); you can turn it back on from the block's settings.

Blog pages

The blog is two separate page types: the Blog Page (/blog) where posts are listed, and the Blog Article Page (/blog/post-address) where a single post is read. They look nothing alike, so they are designed separately; both have a single template and the content (posts, tags, author, cover image) is filled automatically from the blog records you publish. You write your posts on the Content → Blog screen; the editor only controls the look.

The component library has seven blocks under the Blog Page heading:

Featured Post and Topic Navigation appear only on the Blog Page; Table of Contents, Reading & Sharing, Author Box and Article To Product Bridge only on the Blog Article Page. Post Card can be used on both: it renders every post on the list and the related posts on the article page. As with every other block you can also make device based (desktop / tablet / mobile) settings; see Device-Specific Settings (Desktop / Tablet / Mobile).

ℹThe post itself cannot be removed. On the article page the cover image, title, tags and the post text are a fixed area; it is not added as a block and cannot be removed. The blocks you add are placed around that text: if the position setting of the Table of Contents block is side it sits in a sticky column to the right of the text, if top it sits above it. The position setting of the Author Box and Article To Product Bridge blocks likewise decides whether the block is drawn above or below the text (and, for the product bridge, inside it).

Search results page

When a visitor searches your store, the Search Results page (/search) opens. It is block-based too and uses the same listing blocks as the category page: filter panel, toolbar, product list, active filter summary and inline promo. There is a single template; the results fill in according to whatever word was searched.

In addition to the listing blocks, the component library holds two blocks under the Search Page heading:

The search page has no required blocks; you may remove any block and add any other.

The search page can use five of the listing blocks too: the filter panel, toolbar, product list, Active Filter Summary and Inline Promo. For all of their settings see Liste Sayfalari Bloklari.en.

ℹTurkish character note. Search does not currently fold Turkish accents: a visitor typing "ayakkabi" will not find "ayakkabı" products. This has nothing to do with the page design; a well-prepared No Results State block (recommended products + popular categories) rescues that visitor.

Cart page

The cart page is block based too: you arrange the product rows, order summary, coupon field and warnings by dragging and dropping, just like the Home Page. There is a single template; the content (the products in the visitor's cart, quantities, totals, shipping and discounts) fills in automatically.

The component library has eight blocks under the Cart Page heading:

Cart blocks appear only on the Cart Page; for example you cannot add the Order Summary block to the Home Page. In the default layout the product rows sit in a wide column on the left, while the coupon and order summary sit in a narrow, sticky column on the right; this layout is built with the Grid block, so you can change the column widths and the mobile/tablet behaviour however you like. As with every other block you can also make device based (desktop / tablet / mobile) settings; see Device-Specific Settings (Desktop / Tablet / Mobile).

ℹWhen are the shipping threshold and saved items visible? The Free Shipping Progress block is drawn when a free shipping threshold is defined in your shipping settings; if none is defined it hides itself (with the default setting). The Save for Later block appears in stores where the favourites feature is on, and only to signed in visitors; saved products are written to the visitor's favourites.

Checkout page

The screen where the visitor enters their address, pays and completes the order after the cart. Three addresses are drawn from a single template: the delivery step (/checkout/address), the payment step (/checkout/payment) and the order-complete screen (/checkout/success). Each block knows which step it belongs to; you design one template and the visitor only sees the blocks of the step they are on.

The component library holds twelve blocks under the Checkout Page heading:

In the default layout the header and stepper sit at the top, the forms fill a wide left column and the order summary sits in a narrow, sticky right column; this layout is built with the Grid block. You can change the column widths and the mobile/tablet behaviour; see Cihaz Bazli Ayarlar.en.

Account pages

The account area a member sees after signing in. One template, twelve addresses: dashboard (/account), orders, order detail, profile, favourites, addresses, returns, return detail, my reviews and support tickets (list · new · detail). All of them go through the same themed shell; the account menu and the page frame are shared across every one.

The component library holds nineteen blocks under the Account Page heading. The eleven that draw the dashboard, orders, profile and favourites screens are listed below; the eight blocks that draw the address, return, review and support screens are documented on their own page: Hesabim Sayfasi Bloklari.en.

All twelve addresses now carry blocks. The content bodies of the addresses, returns, my reviews and support ticket screens became blocks too, each with its own variants and settings. For all eight of them see Hesabim Sayfasi Bloklari.en.

ℹSome settings have no counterpart yet. You can change Shipment Tracking → Delivery estimate, Profile Form → Birth date and Marketing consent, Favourites → Notify me when back in stock, and Address Form → Show Address Title Field and Show Zip Code Field, but nothing changes on screen.

Login and register pages

The membership screens are block-based too: sign-in (/login), registration (/register) and password reset (/forgot-password) are drawn from a single template. Each block knows which screen it belongs to — the login form appears only on sign-in, the register form only on registration. You design once and all three take the same look.

The component library holds nine blocks under the Login / Register Page heading:

ℹSome settings have no counterpart yet. The Remember me option is drawn but the session lasts 30 days regardless; the Marketing consent field is not stored yet; the remaining attempts and lockout countdown numbers do not arrive from the server, so no number appears.

Form page

The forms you create under Left menu → Forms are published in your store at /form/form-address. You define the form's fields there and its appearance here — there is a single template and it is used for all of your forms. See Genel Bakis.en.

The component library holds two blocks for this page under the Form & Review heading:

Review page

The link in the review invitation email you send after an order is delivered lands on this page (/review/...). The customer rates with stars, writes their comment and uploads photos if allowed. There is a single template and it is used for every invitation.

ℹThe reward coupon and photo limit depend on store settings. Even with Show reward coupon switched on, no coupon appears if Give a reward discount code is off under Store Settings → Reviews (see Degerlendirme Ayarlari.en). Likewise raising the Photo limit above 5 has no effect; the system accepts at most 5 photos per review.

Utility pages (404 · Error · Maintenance)

These three pages are created automatically with ready-made default content when your store is set up; on stores created earlier they are added the first time you open the editor. They appear among the other pages in the page menu and are edited and published exactly like the Home Page.

Each has its own block: Not Found, Error Message, Maintenance Notice. These blocks live under the Utility Pages heading in the component library and appear only on their own page type — you cannot, for example, add the Maintenance Notice block to the Home Page. The block's Layout setting switches between minimal and richer variants, and you can change the headings and button labels. Device-specific (desktop / tablet / mobile) settings work here just like on any other block; see Cihaz Bazli Ayarlar.en.

Creating a New Page

When you press the New Page () button or Create New Page in the page menu, the Create New Page window opens. Step by step:

1. Page Name — Give your page a name (e.g. "About Us"). This name is used in the page menu and generally to recognize the page.
2. URL Slug — The last part of the page's web address (e.g. hakkimizda). It is generated automatically from the page name; if you want to change it, click the Edit link next to it, and press Close when you're done. Below it, the full version of the address is shown as Storefront URL.
   • The slug should only contain lowercase letters and hyphens (-); Turkish characters and spaces are not recommended. Example: "Sıkça Sorulanlar" → sikca-sorulanlar.
3. Description — (Optional) A short note about what the page is about. Placeholder: Page description (optional).
4. The SEO Settings section (for search engines). This section now appears for every page type:
   • SEO Title — The title that will appear in search engines like Google and in the browser tab. The character counter shows the limit with {number}/60.
   • SEO Description — The short description that appears under the title in search results. The counter shows the {number}/160 limit.
   • Below the fields, the SEO keys belonging to that page type are listed as chips. See SEO keys.
5. The Structure Settings section:
   • Use Header Structure (on/off) — If on, the shared Header Structure (header/menu) appears on this page. Its description: Include the header and top components. (Default: on.)
   • Use Footer Structure (on/off) — If on, the shared Footer Structure (footer) appears on this page. Its description: Include the footer and bottom components. (Default: on.)
6. Press the Create button. (While the operation is in progress it says Creating....) The page is created and the editor automatically switches to the new page.

Editing a Page

To change a page's name, address, and SEO information:

• Press the (Edit Page) button on the toolbar, or
• Hover over that page in the page menu and click the edit () icon.

In the Edit Page window that opens, you can change the following:

Press the Save button (while the operation is in progress it says Saving...). If something goes wrong, you will see a Save failed warning; try again.

SEO keys (fields that fill in per page type)

Pages such as Category, Product, Brand, Tag and Blog are drawn from a single template but open at thousands of different addresses: /urun/ceramic-mug, /urun/linen-shirt, /category/kitchen… That is why writing a fixed text into the SEO title of those pages does not work — every product would get the same title.

The answer is keys. A key is a placeholder you write in curly braces; when the page opens it is replaced with the real information of that product / category.

Example. If you write this into the Product Page template's SEO Title field:

{urun} | {marka} | {magaza}

then when a visitor opens the "Ceramic Mug" product, the browser tab and Google show:

Ceramic Mug | Atölye Mira | Mira Boutique

How do I insert a key?

Just click the chips below the SEO field — the key is inserted at the cursor. You do not have to memorise anything. Hover over a chip to see what it means and an example value.

Which keys does each page have?

If you write a key that does not exist on that page type, nothing is printed (it is cleaned away, not left as {...} in the text).

What happens to a key with no value?

A key with an empty value is silently removed, along with the separator next to it. So a template that says {urun} | {marka} produces, on a product with no brand:

• Ceramic Mug,
• not a half-finished Ceramic Mug | .

Priority — which title wins?

1. The product's / category's own SEO. If you wrote a product-specific SEO title in the catalogue, it is always used; the template does not override it.
2. Template SEO (with keys). If the entity's own SEO is empty, the key-based template here takes over.
3. Default. If both are empty, the product/category name is used.

So template SEO is a bulk default generator: it gives a sensible title to the thousands of pages you did not write one for, and stays out of the way of the ones you did.

ℹSome of these pages are already closed to search engines. The Checkout, Account, Login/Register, Review and Search Results pages tell Google not to list their addresses. Writing an SEO Title is still useful: that title appears in the browser tab. On these pages, use keys such as {sorgu} to make the tab title meaningful.

Deleting a Page

Only Custom Pages can be deleted. Your store's system pages — Home, Category, Product, Brand, Tag, Search Results, Blog, Blog Article, Cart, Checkout, Account, Login/Register, Form, Review, Not Found (404), Error, Maintenance, Header Structure and Footer Structure — cannot be deleted. They are required for your store to work; even if you deleted one, the system would recreate it immediately. That is why the delete button never appears on them.

To remove a Custom Page:

• Press the (Delete Page) button on the toolbar, or
• Hover over that page in the page menu and click the delete () icon.

The Delete Page confirmation window opens: "Are you sure you want to delete the page '{page name}'? This operation cannot be undone." You are offered the Cancel or Delete option.

Reset to Default

On system pages, a ↺ Reset to default button sits where the delete button would be (on the toolbar, next to the button).

It loads that page's built-in Treyza default layout: the current blocks are removed and the page returns to the factory block arrangement.

1. Press the button.
2. The confirmation window tells you how many blocks will change.
3. Press Reset to default.

Reversible. This is not saved immediately. If you don't like the result, use Undo (↶) or Discard changes in the ⋮ menu to get your old layout back. The new layout only reaches visitors after you press Save + Publish.

The button appears only on pages that have a built-in default: Product, Category, Brand, Tag, Search Results, Blog, Blog Article, Cart, Login/Register, Form, 404, Error, Maintenance. The Home Page, Header Structure and Footer Structure are entirely yours, so they have no such default.

Required blocks — "why can't I publish?"

Some pages carry a job that cannot be skipped: the visitor pays there, signs in there, or reviews their order there. On those pages certain blocks must be switched on. If a required block is missing — or has been turned off with the visibility switch — the page cannot be published.

The rule in one sentence: A page without its required blocks may sit as a draft, but it cannot reach visitors.

Pages that are not in the list (Home, Category, Brand, Tag, Search Results, Blog, Custom Pages, 404/Error/Maintenance, Header/Footer Structure) have no required blocks.

When do you see the warning?

If a block is missing, a dialog titled "Required page blocks are missing" opens when you press Save or Publish and lists exactly which blocks are missing. Your options:

• Add missing blocks — appends the blocks to the end of the template; you can move them afterwards.
• Save anyway — appears on Save only. Your draft is stored, but it cannot be published as is.
• Cancel — closes the dialog and changes nothing.

A "{count} required blocks missing" badge also appears in the top bar; hover it to see the names of the missing blocks.

Pages with a fixed block set (visual editing only)

On some pages you cannot add or delete blocks — you can only change how the existing blocks look, in which order they appear and whether they are visible. The reason is safety: these pages drive the purchase and membership flow, and removing a block could stop a visitor from completing their order.

Today this rule applies to three pages: Checkout, Account and Review.

When you open such a page:

• In place of the component library on the left you see a short explanation; no block list and no search box.
• No trash icon appears in the block pool or on the canvas; there is a lock icon with a tooltip explaining why.
• The ↺ Reset to default button is hidden (it would rebuild the blocks from scratch).
• Containers (Grid / Tabs / Slides) do not offer an add component button.

What you can do on these pages:

"I don't want this block, but I can't delete it" — what now?

Use the visibility switch instead of deleting. You turn the block off from the block pool (or by hovering it on the canvas); the block stays in the template but is not drawn for visitors. You can switch it back on any time — unlike deleting, it is easy to undo.

Header Structure and Footer Structure (shared sections)

The Header Structure and Footer Structure are sections that appear in common across all your pages:

• Header Structure (Header): The top section, such as logo, menu, search, cart.
• Footer Structure (Footer): The bottom section, such as links, contact info, social media, payment icons.

To edit them, select Header Structure or Footer Structure under the Structure heading in the page menu. Just like editing a page, you add components inside them and set them up. The difference: a change you make here is reflected on every page.

If you don't want the Header or Footer Structure to appear on a page, you can turn off the Show Header Structure / Show Footer Structure switches from that page's edit window (for example for a simple landing page).

Frequently asked questions

Q: On one page the component library does not open, there is an explanation instead. A: That page has a fixed block set (Checkout, Account, Review). You cannot add or delete blocks, but you can change visual settings such as colour, spacing and typography, reorder the blocks and switch them on or off. See Pages with a fixed block set.

Q: Why can't I delete this block? There is no trash icon. A: You are on the Checkout, Account or Review page. These three run the order and membership flow; a block disappearing could stop a visitor from paying. Instead of deleting, turn the block off — it stays in the template, is not shown to visitors, and you can switch it back on whenever you like. Details.

Q: I press Publish and it says "required blocks are missing". A: One of that page's essential blocks is missing or has been switched off. The dialog names them. On ordinary pages pressing Add missing blocks is enough; on the Checkout / Account / Review pages, find the block in the block pool and switch its visibility back on. Which blocks are required on which page: Required blocks.

Q: My menu and footer are missing on the checkout page. A: That is deliberate. The Hide Site Menu setting of the Checkout Header block is on by default so the visitor is not distracted during payment. Turn it off if you want the menu back.

Q: I edited the Account page but nothing changed on the addresses / returns screen. A: Five of the twelve account addresses carry blocks; on the other seven, only the account menu and the page frame come from the theme editor today. Your colour, typography and spacing settings still apply to those screens. Details.

Q: The "OTP Verification Step" block I added to the login page doesn't show on my site. A: This block is drawn in the editor preview only today; the storefront sign-in has no email-code step yet. You may prepare its design in advance, but do not expect a change in your store.

Q: I applied a ready-made theme and my Checkout and Account pages did not change. A: Expected behaviour. Ready-made themes work by installing blocks into pages; since blocks cannot be installed on those three pages, they are skipped. The theme's colours and fonts are applied store-wide, including those pages.

Q: I want to delete the Home Page but there's no delete button. A: The Home Page is a protected page and cannot be deleted (your store must have an entry page). You can change the content of the Home Page, but you cannot remove the page itself.

Q: I changed my menu but it only changed on one page. A: Most likely you put the menu inside a page as a separate component. For a shared menu on all pages, you should edit the menu in the Header Structure.

Q: What do the SEO Title and SEO Description do? A: These determine how your store will appear in search engines like Google. A well-written SEO title and description make it easier for people to find you in search and click. If you leave them blank, the system uses reasonable defaults, but filling them in is recommended.

Q: I want to delete the Category page but there's no delete button. A: Every page other than Custom Pages (Category, Product, Brand, Tag, Search, Blog, Cart, Checkout, Account, Login/Register, Form, Review and the utility pages) is one of your store's system pages and cannot be deleted. Even if you deleted one, the system would recreate it immediately. You can change the page's content freely, and ↺ Reset to default takes it back to the factory layout.

Q: The text I wrote in the SEO Title comes out the same on every product. A: You wrote fixed text. The Product Page serves every product from a single template; for a different title on each product you must use a key — for example {urun} | {marka}. Click the chips below the field to insert one.

Q: I wrote a product-specific SEO title but the key-based template title shows / doesn't show. A: The product's own SEO title in the catalogue always wins. The key-based template title only kicks in for products whose own SEO is empty.

Q: The store name appears twice in the title. A: The title template under Theme Settings → Site already appends the store name. Remove the {magaza} key from the SEO Title.

Q: The products I see in the category editor are not mine. A: You have not picked a category yet, so the editor opened with sample data. Use Pick a category from my store… in the top-right selector. Sample data is never shown to visitors.