Templates are reusable website sections such as headers, footers, heroes, portfolios, contact sections, product layouts, and dynamic data sections.
powered by xwms
Terug naar overzicht
Supportgroepen
Websites
Studio websites, hosting, contentupdates en websitebeheer.
Yes. The page editor includes a template library with preview cards, collections, search, favorites, and recent usage.
Yes. Templates are grouped into collections so shop owners can browse sections by visual style or shop concept.
Yes. The template library supports search so you can find sections faster when a shop grows larger.
Yes. The template library is built around cards with images, names, descriptions, and actions to preview or use a template.
Yes. Template library preferences can keep track of favorites so frequently used templates are easier to find.
Yes. The template library tracks recent template usage to make repeat editing faster.
Yes. Shared template types such as headers and footers can be synced across pages when needed.
Yes. A shared template can be detached so one page gets its own separate version.
Yes. Templates on a page can be reordered so the section order of the website can be changed visually in the page editor.
Yes. Templates can be removed from a page, with confirmation prompts for destructive actions.
Yes. Templates can render buttons, chips, and action states that route visitors into the account connect flow.
Yes. Appointment templates can reserve a dynamic area for live appointment data while still keeping the design editable.
Yes. Event templates can be designed to show media, titles, descriptions, and tags in a structured layout.
Yes. Event row content is designed to support multiple presentational combinations as the template system grows.
Yes. Template colors can inherit from the website, inherit from the page, or override colors only for one template instance.
Yes. The template system supports product detail layouts that render store data at runtime.
Yes. The runtime can expose those record types to templates so websites can show structured business data visually.
Yes. Templates can stay local to one page so each page can have its own unique content and layout.
Yes. Shared template syncing makes it easier to keep repeated elements like headers and footers aligned across the website.
Yes. The template architecture is built so each template keeps its own styling scope and avoids conflicts with other sections.
Yes. The builder is designed so a branded site can still be assembled from flexible templates and dynamic data instead of fixed pages.
Yes. The template library is shared, but each shop still controls its own pages, colors, data, and layout decisions.
XWMS matches this intent with a template library, live page editing, autosave, and reusable sections for faster website changes.
XWMS supports product detail templates that pull store data at runtime for more maintainable shop pages.
The current starter builder uses an XWMS collection for technical test blocks and a Roots & Glow collection for the salon header import. The old public template set was removed so new templates can be added deliberately and tested one collection at a time.
The XWMS height block is a full-width technical test template with an adjustable height. It is used to test scrolling behavior, sticky headers, canvas viewport behavior, and spacing inside the builder and runtime.
The Roots & Glow header template is an imported salon navigation component with editable brand settings, navigation links, call-to-action button, sticky or static behavior, transparent-at-top behavior, scroll background, mobile menu, and mobile bottom navigation.
Yes. The Roots & Glow header exposes scoped design controls so the brand, navigation links, action button, mobile menu, bottom navigation, and general header background colors can each be edited from the element that controls them.
Yes. Catalogue cards are intended to show the desktop version of templates so the buyer or shop owner sees the full layout instead of an accidental mobile collapse.
Live support
Begin een gesprek
Je moet ingelogd zijn om een supportticket te starten.
InloggenWelkom terug. Start een ticket of laat je vraag achter.
