Based on the fetched Lana shop data, Gatsby generates a collection of pages. The Gatsby configuration accommodates the configured shop languages and will produce a multi-language page structure if the shop has additional languages set up. If there is only one language, the [language]
prefix is removed from the page paths.
Home Page
Path: [language]/
Template: src/templates/home.tsx
.
Refer to the following for more information:
homePageContentBlockHandle
in the configuration file.- Home Page content models.
Search Page
Path: [language]/search
Template: src/templates/search.tsx
.
Refer to the following for more information:
searchPageContentBlockHandle
in the configuration file.- Search Page content models.
Profile Page
Path: [language]/profile
Template: src/templates/profile.tsx
.
The Profile page contains a dynamic customer menu with multiple sub-sections. It is only used for signed-in customers. The sign-in/sign-up forms are pop-up modal dialogs.
Page
Path: [language]/pages/<handle>
Template: src/templates/page.tsx
.
Generic pages are generated for published content blocks marked with is_page
= true
.
Product
Path: [language]/products/<handle>
Template: src/templates/product.tsx
.
Product pages are only generated for published products.
Refer to the following for more information:
productPageContentBlockHandle
in the configuration file.- Product Page content models.
Category
Path: [language]/<parentCategoryHandle>/<handle>
Template: src/templates/category.tsx
.
Category pages are only generated for published categories marked with featured
= true
.
Refer to the following for more information:
NOTEFor non-featured categories, the
src/templates/categoryPlaceholder.tsx
template is used instead. This is a user-friendly placeholder. It explains that the category should be madefeatured
for it to have a proper category page generated.