> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/pim3/tutorials/example-projects/product-viewer.md). # Product viewer The product viewer is a fully featured website showing product catalogues in Struct PIM with filters, product listings, product details. ### About the project The product viewer is a website template showing product catalogues in Struct PIM with filters, product listings, product details etc. The source code for the platform is publicly available, allowing for easy branding of the site as well as customization of the standard functionality.

The project is a separate website that uses the Struct PIM API to get product data, which is then indexed to an Elastic cluster, from where it is served to the website. The integration is built as a template demonstrating how to map data from Struct PIM for use at a website, with the Struct demo data set as the foundation. The project is hosted in bitbucket and available to everyone. {% embed url="" %} See project on bitbucket {% endembed %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.struct.com/pim3/tutorials/example-projects/product-viewer.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.