Templates

Documentation scope: Guild 0.1.x pre-release builds. The exact public release version will be confirmed in the changelog before Theme Store publication.

Templates control the default sections used by each page type. Shopify manages template assignment and the theme editor's template workflow; Guild documents the sections and defaults supplied by this theme. For platform-level setup, see Shopify's templates documentation. Review templates with real store content before publishing, because product images, long titles, empty collections, and policy text can expose layout issues that sample content hides.

Home page

Use the home page to introduce the brand, highlight featured products or collections, show campaign content, and guide customers to important shopping paths. For home and decor stores, keep the first few sections focused: a clear visual lead, a route into the catalog, and one or two trust-building content areas.

Recommended sections:

• Rich content for cards, logos, testimonials, trust bars, announcement bars, and flexible content.
• Media with content for image-led storytelling.
• Columns for side-by-side content.
• Countdown banner for launch or promotion messaging.
• Newsletter form for email signup.
• FAQ accordion or Tabbed content for supporting information.

Before publishing, remove sample content and replace temporary sections with final storefront content.

Standard pages

The default page template uses Rich content with Content source set to Current page. It imports the published page title and body from Shopify Admin, renders the current page title as the main heading, and keeps the body inside a readable content measure. When the imported title is shown, its Title controls include Typography, Body-only Text style, Font weight, Font size, Uppercase, and the block alignment. Add sections before or after the main content when the page needs a richer editorial layout.

When Content source is used with a manually selected page inside another composition, that selected page remains reusable supporting content rather than becoming the main page heading.

Additional page templates are available for common page types:

• About starts with an image-led introduction, store highlights, the Team preset, and testimonials. Replace all placeholder names, roles, images, social links, and trust copy before publishing.
• Story starts with an image-led brand story, chapter cards, value highlights, and a closing call to action. Use it for origin stories, craftsmanship, materials, or editorial brand pages.
• FAQ provides prepared topic navigation, grouped accordion content, support links, and contact recovery.
• Inspiration provides an editorial room-story layout with product hotspots and supporting product discovery.

Recommended use:

• Use the default page template for simple information pages maintained in Shopify Admin.
• Edit the page title and body in Shopify Admin, then use the theme editor for layout, background, spacing, and supporting sections.
• Use About or Story when the page needs a ready-made editorial structure.
• Create a separate Shopify Page for FAQ and Inspiration, then assign the matching page.faq or page.inspiration template. Adding ?view=faq or ?view=inspiration to another Page URL only changes the template used to render that same Page resource; it does not create a separate page title, handle, or SEO identity.
• Keep FAQ content based on real support questions and replace Inspiration demo products, imagery, and links with the store's own content before publishing.

Product page

The product template uses the main product page section. Review it with products that represent the messy parts of the catalog, not only the best-looking product.

Recommended use:

• Review product media, title, price, variants, product form, description, and supporting content. In Slider gallery layout, Show arrows exposes Medium (default), Large, or Custom arrow size, Chevron (default) or Arrow icon style, icon scale, icon stroke, and Default, Oval, Full, or None border radius. Main product media and thumbnails can use independent boxed-mode styling; thumbnail boxed controls appear only for Slideshow with thumbnails enabled. In Product variants, Variant images can use a configurable image aspect ratio; Swatches fall back to available variant imagery instead of leaving an empty visual when Shopify has no swatch value; and Boxes provides plain text radio boxes for values such as Size. Visual swatch groups can optionally show the selected value in the option label and preview another visual value on pointer hover or keyboard focus without changing the selected variant. Product price can keep the compare-at price while hiding the separate savings-amount message. Purchase controls expose accelerated-checkout Layout and Border radius while normal Guild button sizing remains authoritative. When the quantity input is enabled, Show quantity input on mobile can hide the visible quantity control on mobile while keeping quantity submission active. The unbranded Shopify Buy it now button follows the current Guild button colors; branded wallet buttons such as Apple Pay, PayPal, Shop Pay, and Google Pay retain provider branding.

Purchase controls keep the quantity selector compact: stock availability, in-cart quantity, and quantity-rule hints are not displayed beneath it. Configure a separate Product inventory block for visible stock information. Quantity limits and purchase validation remain active; actual purchase errors still provide feedback. Add-to-cart success is announced to assistive technology without adding visible text below the buttons.

• For variant-specific delivery copy, add Product shipping, open Show advanced options, enable Update by variant, and enter the variant metafield namespace and key. Guild reads the selected-variant value first and falls back to the configured product metafield. Leave the feature disabled when one product-level message is sufficient.
• For augmented-reality product viewing, upload a Shopify 3D model, keep Product gallery in the same Product surface, then add Buttons > Button and choose Action behavior > Shopify XR. Set the normal Button label and icon yourself; View in your space with 3D model is the recommended configuration. Place it below or close to the gallery and verify it on compatible iOS and Android devices.
• Product cards can open Quick view from product-list contexts. Quick view uses the configured full Product block surface for faster browsing and purchase, while associated-product or limited variant-data transitions can continue on the full product page as a safety fallback. Test both paths before relying on Quick view as a primary purchase surface.
• Test products with one variant, multiple variants, sold-out variants, and long descriptions.
• Add supporting sections such as Breadcrumbs, Trust and reassurance, Product specifications, FAQ accordion, Tabbed content, or Media with content when needed.
• Review the page on mobile, especially product media and add-to-cart behavior.

Collection page

The collection template uses the main collection page section for catalog browsing. Check both strong merchandising collections and sparse collections with only a few products. The section's Add block picker is intentionally focused on collection identity, Collection Hero, filters, sorting, products, empty-state/recovery content, compact merchandising, custom code, and app blocks. Add unrelated editorial modules as separate sections above or below the product grid.

Important settings:

• Products per page controls the native Shopify pagination size.
• Pagination mode can use Paginated, Load more, or Infinite scroll. Paginated is the safest default and keeps Shopify's normal pagination links. Load more keeps a native next-page link that JavaScript can enhance into appending products. Infinite scroll uses the same load-more path and stops after the configured automatic-load limit, leaving the manual button fallback available.
• Automatic loads before button fallback controls how many automatic infinite-scroll loads can happen before customers continue with the manual Load more link.
• In Collection Hero > Slide - collection > Advanced, Show slide controls whether that slide appears on the storefront. The default collection template uses When collection has an image or description, which keeps resource-driven heroes on merchandised collections while avoiding an empty hero on collections such as a bare all-products catalog.

Important behavior:

• Collection sorting uses Shopify's collection sort options and keeps active filters when possible. When Border is Bottom or Top and bottom, Show borders on mobile can remove those configured borders on mobile while keeping them on larger screens. Keep sorting visible on scroll respects the sticky Header or Main menu offset instead of overlapping it.
• Collection filters use Shopify storefront filters. Filter availability depends on Shopify Search & Discovery setup, product data, and whether the current collection has products that match the filter configuration. Active filters uses buttons for removal in the enhanced interface. Show filter name adds the group prefix, such as Availability:, and is disabled by default. Show result count adds the current result count and is enabled by default.
• List, boolean, price, swatch, and image-style filter presentations can appear when Shopify provides them.
• Collection updates are progressively enhanced with AJAX for sorting, filters, pagination, load more, and guarded infinite scroll. Clear all filters refreshes the section so the complete baseline filter-value list returns immediately when Hide inactive filters is enabled. The collection page keeps native links and form submissions as fallbacks when JavaScript is unavailable.
• Product cards use the shared product-card renderer, so Quick view and product-card behavior should be tested from collection results too.
• Collection Hero visibility conditions affect only the storefront. The Theme Editor always keeps the configured Slide - collection visible for editing and preview. If Show slide is Always and the collection has no image, Guild uses the content-only hero fallback rather than leaving an empty aspect-ratio banner.

Recommended use:

• Review collection title, description, product grid, sorting, filters, active filter removal, pagination mode, and empty collection behavior.

• Add merchandising sections above or below the product grid when needed.

• Test Paginated, Load more, and Infinite scroll with real collections that have more products than one page.

• Check product images, product titles, pricing, Quick view behavior, filter drawer behavior, and spacing on mobile.

• Cart line details use one utility list. Unit prices, when available, appear as supporting details in that list before line discounts. Line discounts remain the final items, and the list owns spacing and AJAX replacement.

Cart

The cart template uses the main Cart section for carts with items and a separate Cart - empty section for the empty state. The default full-page layout is assembled from cart-specific layout blocks, so cart-only blocks stay inside the Cart section instead of appearing in normal page sections. Customers can review line items, adjust quantities, see line totals and summary totals, use cart notes or optional cart attributes where enabled, and continue to checkout from the summary area. The full Cart section picker is intentionally focused on cart data and actions, contextual layouts, compact trust or navigation content, product recommendations, payment methods, custom code, and app blocks. Add Blog, Hero, form, or broad editorial modules as separate sections.

Guild also includes an optional Slide-out cart in the Popups section group. Its section visibility controls the feature: when enabled, supported Add to cart actions and the Header cart link open the drawer after the AJAX cart update; when disabled, Add to cart keeps the customer on the current page and shows the theme's standard success alert. The native /cart page remains the direct and no-JavaScript fallback. The drawer's Add block picker is intentionally focused on Cart blocks, compact content, product recommendations, payment methods, custom code, and app blocks; add full editorial galleries, blog lists, collection showcases, or Hero content as separate page sections instead.

Important behavior:

• Quantity controls update the cart automatically when JavaScript is available. Line totals, summary totals, discounts, optional free-shipping progress, and cart count can refresh without requiring a separate Update click.
• Unit prices do not animate as changing values when only quantity changes; the line total is the value that changes.
• Cart note and enabled cart attribute changes also save automatically when JavaScript is available.
• The cart keeps a native form fallback. If JavaScript is unavailable, the Update control remains available for quantity, note, and attribute changes.
• Line items can show variant details, public line item properties from the product form, selling-plan names, unit prices, discounts, upload links, stock or quantity messages, and remove/Undo behavior. Private properties whose names start with _ and internal Shopify properties are hidden.
• Quantity validation messages appear below the quantity and price controls so they do not interrupt the main quantity/price row.
• When the cart has no visible price adjustment and the item subtotal matches the cart total, the summary shows one Estimated total row instead of repeating the same amount as Subtotal and Total. When discounts, the optional estimated-tax row, or another cart-total difference needs explanation, the summary shows both Subtotal and Total. The Checkout button block can optionally append the current cart total to its label, and that amount refreshes with AJAX cart updates. The same block can show Shopify accelerated checkout wallet buttons, set their desktop layout to Inline or Stacked, and control the gap between the standard and accelerated checkout areas. Wallet buttons always stack on mobile. Merchants can add, remove, hide, and reorder summary blocks such as Checkout button, Order notes, Terms checkbox, and Divider. Guild does not provide a manual cart-level discount code field; discount validation remains handled by Shopify checkout and Shopify discount rules. In the theme editor, Cart attributes can show sample attribute rows when the current cart has no public attributes, so merchants can style the block before real attributes exist.
• Cart free shipping text and Free shipping bar use Theme settings > Cart > Free shipping threshold. A value above 0 enables their storefront output; 0 disables it. The theme editor can show a 100-unit design preview while the global threshold is disabled, so configure the real threshold before checking the live storefront. Checkout shipping rules remain the source of truth.
• Required Order notes or Terms checkbox blocks gate standard checkout. Accelerated checkout inside Checkout button is suppressed while either visible field is required because dynamic checkout providers cannot be reliably gated by the theme.
• Free-shipping messaging is optional and disabled when the theme threshold is set to 0. Enable it only when the store actually offers the configured threshold. Shopify checkout shipping rules and discounts remain the source of truth.
• The Cart - empty default composition is intentionally simple: heading, text, and buttons. Merchants can add relevant product, collection, media, form, Custom HTML, or Custom Liquid content when the recovery path needs more context.

Recommended use:

• Test with one item, multiple items, discounts, and different product types.
• Test quantity changes with JavaScript enabled and with JavaScript disabled.
• Test products with variants, selling plans, unit prices, and line item properties if the store uses them.
• Make sure cart messaging, checkout terms, payment icons, accelerated checkout visibility, and links support the store's checkout flow.
• Review the Cart - empty section separately. It can stay focused on a clear return path or use richer content blocks, product lists, collection links, media, forms, Custom HTML, or Custom Liquid when the empty-cart page needs more context. Guild renders only the cart state that matches the current cart.

Blog and article

In Shopify, the Blog template is the article-list or journal page, while the Article template is the individual blog post page. Guild uses the same article-data blocks across Blog cards and the Article page so titles, excerpts, details, tags, media, and actions keep a consistent setup.

The Blog template uses Blog posts inside the main blog section. It can show the current blog's articles with an editable article-card composition, an optional Featured blog item lead card, Blog item cards for the remaining articles, and native pagination. Pagination appears last in the list block's Add block order and its Separator defaults to None. The same default applies to Pagination used by Product list, Collection list, and Search results.

The Article template uses the main Article section. That section uses the same section shell and layout controls as Rich content, including section width, background width, content width and position, height, boxed content, color scheme, spacing, borders, background content, reveal settings, and advanced layout controls.

The default Article composition includes Breadcrumbs, Article tags, one Article heading in Article Hero, Article excerpt, Article details, Article media, Article content, Related articles, and a Newsletter form. Article Hero owns the page h1; the Article content block hides its repeated title heading by default and renders the body created in Shopify Admin. Supporting section headings use h2, while Related article card titles use h3.

In Article Hero > Slide - article > Advanced, Show slide can keep the slide Always visible on the storefront or require the article image, excerpt, either one, or both. The condition is evaluated only on the storefront; the Theme Editor keeps the slide visible so it remains editable even when the current article does not satisfy the selected condition.

Recommended use:

• Use Blog pages for editorial indexes, announcements, guides, journals, or stories. Use Article pages for each individual post.
• Review the Blog template with a real blog that has more articles than one page, so pagination, card spacing, mobile layout, and tag wrapping are visible.
• Use Article thumb for article-card images and optional card-overlay content inside Blog post list. Use Attach to media on Article tags only when tags should sit directly over the card image. On the Article page, use Article media for the primary image.
• Use Row - article, Column - article, and Box - article when the Article page needs multi-column content, a sidebar, framed content, or nested Article blocks. These contextual layout blocks use the same layout controls as the standard Row, Column, and Box blocks while retaining the current article data.
• Inside Article details, add an Article detail child and select Type: Date, Author, Reading time, or Summary. Summary builds an automatic linked table of contents from headings inside Article content, omits the post title, and supports optional item numbers.
• For Type: Date, choose Published date or Updated date and enable Show label when the visible output should identify the selected date. Add two Date-type children when both values are needed.
• For Type: Author, enable Show avatar to use the Shopify author account image. An optional author title can be added manually or through a compatible dynamic source. Use Article excerpt > Author bio for the Shopify author bio.
• Add Article buttons for Previous article, Current blog, Next article, Article details, or Author homepage actions. The default preset uses All articles plus Next article: [title]; boundary links are omitted when no destination exists.
• Add a generic Buttons > Button and set Action behavior to Share current page for native device sharing with a Copy link fallback. Provider-specific sharing widgets can still be supplied by an app.
• Comments require comments to be enabled for the Shopify blog and Show comments to be enabled in the Article section.
• App blocks are supported in the Article section and its approved Article layout containers.
• Start merchant-authored Article content headings at h2; use h3 for subsections and do not add another h1 inside the article body.
• Check Article content with headings, images, lists, quotes, links, tables, embeds, long URLs, and realistic mobile widths before publishing.
• Use consistent image sizes for article cards and primary Article images.

Default Blog template

The default Blog template is an editorial composition with a compact masthead, manually configured category links, Featured stories, Start here, a Newsletter form, and Latest articles. Each Blog post list chooses Blog, Selected articles, or Related articles as its source. Blog is the default; on Article pages a blank Blog picker can use the current article's blog.

The starter category links use the current blog URL when Link source is set to Current blog tag. Set Blog tag to the tag path you want to use, or leave it blank to derive the tag path from the button label. These are ordinary links, not dynamic filters, and Guild does not automatically create an active category state.

Featured stories and Start here are editorial modules, while Latest articles is the intended paginated/infinite list. Start with article applies only to Blog source; values above 1 skip earlier posts and intentionally disable native pagination for that list. Selected articles preserves the merchant-selected order. Related articles excludes the current post, prioritizes shared tags, fills from the same blog, and does not paginate. Populate the demo deliberately because separate lists can still select overlapping posts. Test tag routes, no-JavaScript pagination, direct page URLs, Infinite scroll, mobile layout, disabled Featured/Pagination blocks, and Theme Editor section reloads before publishing.

The Newsletter form subscribes the submitted email through Shopify's customer/newsletter form. Do not add optional consent wording that implies the checkbox controls subscription. Configure marketing/privacy wording according to the store's real setup and applicable advice.

Search

The search template uses the main Search section for Shopify storefront search results. Test real customer-style searches, including misspellings, broad terms, and specific product names, so empty, no-results, and mixed-result states feel intentional. The section's Add block picker is intentionally focused on Search controls and results, result-aware recovery content, collection or product suggestions, compact content, custom code, and app blocks. Add unrelated editorial, navigation, payment, or social modules as separate sections.

Important blocks and settings:

• Search tabs switch the local Products, Articles, and Pages panels. A tab shows its rendered result count when that panel contains results, for example Articles (2).
• Search visibility group is a conditional holder for the automatic Search results heading, Result count, the generic Collection list, Heading/Text/layout blocks, or other Search-safe content. Its Result visibility can show content before searching, when any results exist, when the active result type has results, or when the active result type has no results. Container maximum width can constrain the group independently; when a custom width is active, Alignment positions the group itself at the start, center, or end without changing its nested text alignment. To recreate an empty-state composition, add the generic group, select When active type has no results, and place the required Heading, Text, or links inside it.
• Search filters button, Search filters active, and Search filters use the same result-aware contract and default to When active type has results. Search filters active uses the shared Advanced > Display mode control for responsive visibility, with the additional Search-specific Sticky only mode. Result visibility and Display mode control different concerns and remain intentionally independent. Its active-filter buttons use the same markup and appearance settings as Collection: Show filter name is disabled by default, while Show result count is enabled by default. Product filters remain unavailable for Article-only and Page-only result scopes.
• Result count defaults to Result count and search term using Active result type, and can still be configured to report all results or only the selected Products, Articles, or Pages tab.
• Search results list provides independent Results per page, Grid gap, and Content gap controls for Product cards and Article/Page result cards on the Search page. Header Main search uses the separate Predictive results list, which keeps only Product layout settings relevant to predictive results and a restricted Product item composition. Its Columns setting is limited to 1-4, matching the fixed four-Product predictive maximum; Theme Editor renders four placeholder Product cards for layout styling. Main search composes predictive content through Search suggestions, Heading, Buttons, Row - search, and Column - search child blocks. Each Search suggestions block independently selects Suggestions, Collections, Brands, or Content and owns its heading plus Content-list-style presentation; Brands come from matching Product vendors and link to Shopify's vendor collection route; a Button with Action behavior: Search results receives the current predictive-search results URL at runtime. In mixed Search-page queries Shopify still paginates one combined search.results stream, so Guild uses the larger Products/Articles page-size value; type-only searches use their matching value. In the Theme Editor, separate Product item and Result item sample lists plus the shared Pagination preview remain visible for styling without relying on the current query.
• Search filters accepts generic native filter criteria plus dedicated Price filter and Color filter blocks. Their availability still depends on the filters configured in Shopify Search & Discovery and on matching product data.
• Collection list renders selected or all collection titles through the Content-list-style utility renderer. It is a generic content block, not predictive search, and can be used outside Search. To use it as pre-search suggestions, place it inside Search visibility group and select Before searching. Use Collection links instead when the suggestions should be Button or Text links.
• Pagination mode can use Paginated, Load more, or Infinite scroll. Paginated is the safest default. Load more keeps a native next-page link that JavaScript can enhance into appending more results. Infinite scroll uses the same load-more path and stops after the configured automatic-load limit, leaving the manual button fallback available.
• Automatic loads before button fallback controls how many automatic Infinite scroll loads can happen before the manual Load more results link remains as the next step.

Important behavior:

• The search form submits a normal Shopify search query using q and keeps the options[prefix]=last search option.
• Search tabs switch panels locally and do not issue separate search queries. The automatic heading, active-type count, and every Search visibility group stay synchronized with the active tab. Without JavaScript, hidden tab panels become visible so customers can still reach every rendered result type.
• Product results use Guild's shared Product card renderer. Article and page results use the shared configurable Result card template.
• The search page distinguishes the empty-search prompt, no-results message, and successful results summary. The shipped no-results composition also provides a Browse collections recovery action.
• Search submissions, filters, and pagination are progressively enhanced with AJAX. Filter values submit immediately outside the drawer; drawer and sticky layouts use the visible Apply filters button. Incoming results use the same loading/reveal lifecycle as Collection updates. The Search section exposes section-search-loading during an active update and section-search-no-results for a completed search with no results. Native Search forms and pagination remain the fallback when JavaScript is unavailable.
• Load more and Infinite scroll append the next Search result page and update the visible tab counts. Infinite scroll is guarded and falls back to the manual button rather than creating an unlimited automatic feed.
• Search filters use the native storefront filter data Shopify provides for the current search. Availability and presentation depend on Shopify Search & Discovery configuration and product data. Guild does not add Search sorting or query-matched collection results.

Recommended use:

• Test queries that produce Product, Article, Page, mixed, and no results.
• Test Search tab switching, active state, counts, keyboard operation, and the automatic Search results heading.
• Edit the Product item, Result item, and Pagination blocks in the Theme Editor and confirm both sample lists respond independently to their column, Grid gap, Content gap, border, and media settings.
• When Shopify Search & Discovery filters are configured, test filter values, active-filter removal, Clear all, price ranges, and the no-JavaScript form path.
• Test Paginated, Load more, and Infinite scroll with a query that has more than one page of results.
• Test the search page with JavaScript enabled and disabled.
• Make sure no-results messaging and any pre-search Collection list give customers a useful next step.
• Review mobile spacing, keyboard behavior, result card readability, and Product-card Quick view behavior from Search results.

Password

The password page uses its own password layout with separate Password header and Password footer groups. The main password template contains the Password content section, so the header/footer controls stay separate from normal page content.

Recommended use:

• Use for launch, maintenance, or coming-soon pages.
• Keep the password header compact: a logo and one or two useful controls are usually enough.
• Add a clear message and make sure any signup form works as expected.
• The Password section owns Shopify's native storefront password form. Add Password field and a submit Button directly inside the section or its Password Row/Box layout blocks.
• Use Password message only when you want to show the password message configured in Shopify admin.
• Review the page on mobile before enabling password protection.

Important behavior:

• The password form uses Shopify's native storefront password flow. Test correct and incorrect passwords on a password-protected storefront before launch.
• The password header and password footer are configured in their own groups, not inside the main Password section.
• The Password section uses a focused version of the flexible content system: password-specific Row/Box layouts, Password field and message, text, buttons, media, countdown, accordion, social links, custom content, app blocks, and background controls. Large editorial, product, collection, gallery, navigation, and Hero modules are intentionally not offered inside this system-page picker.

404

The 404 template uses the main 404 section.

Recommended use:

• Provide a clear path back to shopping, such as search, collections, or the home page.
• Keep the message short and useful.

List collections

The shipped list collections template separates curated discovery from the complete catalog. Featured collections and Shop by room use selected collection lists, while the final All collections section is the canonical complete collection list with pagination or progressive loading.

Important settings:

• Show all collections
• Collections to show
• Columns
• Grid gap
• Pagination mode on the complete list

Recommended use:

• Keep the Featured and room-based lists intentionally curated rather than relying on the first collections in Shopify.
• Keep collection titles clear and short.
• Use meaningful collection featured images. Guild follows Shopify's collection featured-image fallback when an explicit collection image is unavailable.
• Review the room slider, complete-list loading, spacing, and image cropping on mobile.

Contact page

The contact page template is assembled as a full customer-support and location page. It can include a visual intro, a Shopify-native contact form, supporting contact details, a Google map, FAQ content, and a final support or showroom call to action.

Recommended use:

• Test the contact form on a real storefront or theme preview URL before publishing. Localhost preview is useful for layout checks, but live Shopify submission, success/error state, and hCaptcha behavior should be checked through Shopify.
• Keep required fields limited to what the store needs. Name, email, topic, message, and one privacy/consent checkbox are usually enough.
• Use the Google map section for showroom, studio, pickup, or appointment locations. The pre-release demo composition includes a sample Portland/Pearl District location, map, opening hours, and directions link. Treat this as demo content only and replace all sample location content with the store's own public details before publishing.
• Replace placeholder company details with the store's real public details. Do not publish unnecessary registration, bank, payment, private operational, or customer identifiers on the contact page.
• Use the FAQ area for contact-adjacent questions such as response time, order help, appointment booking, shipping support, or return guidance.
• Review the page on mobile with long email addresses, long locations, and multiline messages.

FAQ page

Create a dedicated Shopify Page such as FAQ, assign the FAQ page template, and link customers to that Page's normal URL. The prepared template includes a single page heading, topic navigation, grouped FAQ accordions, support cards, and contact/recovery paths.

Recommended use:

• Replace demo questions and answers with the store's real support content and policies.
• Keep topic links synchronized with their section anchors.
• Test long questions and answers, accordion keyboard behavior, and mobile scanning before publishing.
• Do not use another Page URL with ?view=faq as the permanent public FAQ route; that keeps the other Page resource's title and SEO identity.

Inspiration page

Create a dedicated Shopify Page such as Inspiration, assign the Inspiration page template, and link to that Page's normal URL. The prepared Home/decor demo uses room-led editorial content, product hotspots, product discovery, material guidance, and support links.

Recommended use:

• Replace demo images, hotspots, products, and copy with resources that exist in the store.
• Keep every hotspot label aligned with its product destination.
• Review both desktop and mobile hotspot layouts and make sure the page remains useful when individual products change or become unavailable.
• Do not use another Page URL with ?view=inspiration as the permanent public Inspiration route; that keeps the other Page resource's title and SEO identity.

Page

The default page template uses Rich content with a Content source block set to Current page. The page title and body come from Shopify Admin, while the section controls the layout, background, width, spacing, and supporting composition.

Recommended use:

• Use for standard information pages such as sizing, care information, delivery, returns, or other long-form content. Use the dedicated Contact, FAQ, or Inspiration template when the page needs one of those prepared experiences.
• Edit the primary page content in Shopify Admin.
• Add sections before or after the main page content when the page needs a richer layout.
• Review long-form content, wide tables, embeds, long links, and heading hierarchy on mobile.

Gift card

The Gift card template is used for issued gift card pages generated by Shopify. It is a focused system page rather than a normal JSON template that merchants assemble from general sections.

The Gift card section supports:

• remaining balance and an optional heading;
• redemption code display;
• Copy code and Print gift card actions;
• Apple Wallet when Shopify provides a pass URL;
• QR code;
• optional recipient, message, and status details;
• dedicated Gift card row and column layout blocks, including Row - gift card nested directly inside Box - gift card when a boxed composition needs a horizontal layout.

App blocks are not supported on the Gift card page. Use app output on a supported section or template unless the app provider documents a separate Shopify gift-card integration.

Recommended review:

• Test an issued card with a remaining balance and redemption code.
• Check Copy, Print, QR, and Apple Wallet when available.
• Review optional recipient, message, and status states.
• Confirm the Header and Footer visibility settings match the intended focused layout.
• Check screen and print output before publishing gift cards for customers.

Related guides

• Section guides
• Forms, popups, and advanced content
• Troubleshooting
• Updating Guild