This repository holds code samples that demonstrate how to implement the various features offered by the Bloomreach product
| Name | Tech stack | Preview |
|---|---|---|
| Search & search usecases | TypeScript, Tailwind CSS, Limitless UI, Discovery Web SDK, React |  |
| Autosuggest | TypeScript, Tailwind CSS, Limitless UI, Discovery Web SDK, React | |
| Recommendations | JavaScript, Tailwind CSS, Discovery Web SDK, React | |
| Facets | JavaScript, Tailwind CSS, Limitless UI, Discovery Web SDK, React | |
| Categories | JavaScript, Tailwind CSS, Discovery Web SDK, React | |
| Dynamic grouping | JavaScript, Tailwind CSS, Discovery Web SDK, React | |
| Relevance by segment | JavaScript, Tailwind CSS, Discovery Web SDK, React | |
| Visual search | JavaScript, Tailwind CSS, Next.js, Limitless UI, React | |
| Multi-language | JavaScript, Tailwind CSS, Discovery Web SDK, React | |
| Storefront with pixel instrumentation | JavaScript, Tailwind CSS, Next.js, Limitless UI, Discovery Web SDK, React |  |
- The code should be optimized to be run in an online code editor, launched with one click from the repository and be able to interactively edit code and run it
- The code should be generic, so you can plug in configuration of any account and they should work.
- The code sample should run with a sample input on load and should not require any user interaction or setup to run it. For example, if it’s a search input, add a default query text in the input, if it is visual search, setup a sample image on load and have some sample images in the sample code directory. This might not be possible in all cases, but try to minimize user setup to run the code sample
- The code sample should be concise. Balance code readability with robustness. The intention of the code samples is to educate about product features, demonstrate it's usage, enable rapid prototyping and not to write production grade code.
- Do not make a code sample that is too complex or has too many dependencies. Keep in mind long term maintenance of a code sample, as the underlying APIs and the libraries are updated over time.
- If a code sample stops working, it should be removed.
Contributions are welcome. Please read the guidelines above and open a pull request and one of our team members will help get it reviewed and merged