...
Page bases are templates into which either your product content from BigCommerce or Styla content from the Editor will be inserted. The basic idea behind bases is that all pages need to share the same header and footer which, in turn, consist of multiple modules. Product details and category pages generated based on data from the BigCommerce API APIs and Styla content created with the Editor will be displayed by Styla Frontend between these header and footer. You can see that on the diagrams on this page.
Depending on page type, the content comes from different data sources and is managed in different places. The diagrams below discuss this in details.
A standard page created in the Editor:
...
A product details page:
...
A category page:
...
Two levels of bases and inheritance
Styla Frontend uses two levels of page bases:
...
Alternatively, you can click the Save button top left and not trigger the re-rendering process.
All the events triggering page re-rendering
These are just some of the events that trigger re-rendering of the .html files. The full list is as follows:
account settings (including CSS) updated in Styla Admin → all pages re-rendered,
page base (template) updated in Styla Editor → all pages using this base re-rendered,
modular content updated in Styla Editor → all pages with this content re-rendered,
a new version of a page published in Styla Editor → only this page re-rendered,
product data in the “headless“ shop updated → pages for products and. categories affected re-rendered,
category data in the “headless” shop updated → only this category page re-rendered,
clicking the “re-index“ button in Styla Admin → all category and product pages re-rendered.
Page path patterns
The view with all your bases above displays a path pattern for each of them. This field defines on what location in your website all pages using a specific base will be create.
...