Repository navigation
hello-retail-v1.17.0
Added
pages-developersets up Pages for API use, where the customer's own frontend renders the products. It indexes the fields the caller filters on, configures design filters and sorting to match the storefront, and leaves the page config without product conditions, with no template work.
Changed
pages-developerestablishes the integration mode (client-side, API with HTML, API with JSON) before touching a design, and warns that an INPUT product filter makes its value mandatory, so requests that don't send that field fail.pages-developernames new designs after the domain alone (<domain>, or<domain> (API)for API setups), without "Pages", since a Pages design only exists in Pages.hello-retail-knowledgeand the skills that read the Viskan platform notes now includecategoryUUIDfor Viskan NG shops: the feed maps it, it gets indexed with the_idfields, and it is added as a filter. Streamline shops are unchanged.hello-retail-knowledgedescribes the Search setup for Viskan shops that call the Search API themselves: a config without a design, the same filters and sorting as Pages, and a category engine when a category feed exists.
Plugin hello-retail version 1.17.0. Update: /plugin marketplace update helloretail then /reload-plugins.
What's Changed
- feat(pages-developer): set up Pages for API use by @hugokrantz in #53
- docs(wiki): add categoryUUID and Search (API) to the Viskan page by @hugokrantz in #56
Full Changelog: hello-retail-v1.16.0...hello-retail-v1.17.0