From 80e48001d9af0d1ce8fd9d5ee994608401f3411b Mon Sep 17 00:00:00 2001 From: Michele Riva Date: Fri, 27 Oct 2023 04:17:58 +0200 Subject: [PATCH] docs: adds Orama integration into the readme file (#1221) --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 838cd1a04..2623a7a4c 100644 --- a/README.md +++ b/README.md @@ -36,6 +36,14 @@ Vercel is happy to partner and work with any commerce provider to help them get > Note: Providers, if you are looking to use similar products for your demo, you can [download these assets](https://drive.google.com/file/d/1q_bKerjrwZgHwCw0ovfUMW6He9VtepO_/view?usp=sharing). +## Integrations + +Integrations enable upgraded or additional functionality for Next.js Commerce + +- [Orama](https://github.com/oramasearch/nextjs-commerce) ([Demo](https://vercel-commerce.oramasearch.com/)) + - Upgrades search to include typeahead with dynamic re-rendering, vector-based similarity search, and JS-based configuration. + - Search runs entirely in the browser for smaller catalogs or on a CDN for larger. + ## Running locally You will need to use the environment variables [defined in `.env.example`](.env.example) to run Next.js Commerce. It's recommended you use [Vercel Environment Variables](https://vercel.com/docs/concepts/projects/environment-variables) for this, but a `.env` file is all that is necessary.