About Store Finder

Store Finder is a demo application built with the CMS visual page builder. It demonstrates how data-connected Puck components can fetch and display content from CMS content types at render time.

The StoreList widget on the homepage is a custom Puck component that fetches store entries from the delivery API. Content editors can drag it onto any page and configure it — setting limits, enabling search, filtering by category, and choosing between grid and list layouts.

Reusable Blocks (like the promo banner and newsletter signup) are Puck content snippets stored as a content type. They can be embedded in any page via the BlockEmbed component, ensuring consistent branding across the site.

Store Finder is a demo application built with the CMS visual page builder. It demonstrates how data-connected Puck components can fetch and display content from CMS content types at render time.

How It Works

Create a content type — Define your data model (e.g., Store with name, address, hours, category).
Add entries — Create and publish store entries through the CMS admin.
Build pages visually — Use the Puck editor to drag in a StoreList component and configure its settings.
Server-side data resolution — At render time, the data resolution layer fetches store entries from the delivery API and injects them into the component.
Reusable blocks — Create once, embed everywhere. Blocks keep shared content (banners, CTAs) consistent across pages.

Create a content type — Define your data model (e.g., Store with name, address, hours, category).
Add entries — Create and publish store entries through the CMS admin.
Build pages visually — Use the Puck editor to drag in a StoreList component and configure its settings.
Server-side data resolution — At render time, the data resolution layer fetches store entries from the delivery API and injects them into the component.
Reusable blocks — Create once, embed everywhere. Blocks keep shared content (banners, CTAs) consistent across pages.