Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Gatsby + Elastic Path Commerce Cloud demo storefront with Algolia search, MIT licensed.
Elastic Path Commerce Cloud Gatsby Starter is an open-source Gatsby ecommerce starter that demonstrates how to build a storefront on Elastic Path Commerce Cloud, the headless commerce API formerly known as Moltin. The repository, published by Elastic Path, powers a live demo store and includes Algolia search and Algolia Places integration.
The Elastic Path Commerce Cloud Gatsby Starter is a demo storefront built with the Gatsby static site generator, connecting to Elastic Path Commerce Cloud as its ecommerce backend. It takes product and transaction data from Elastic Path's API and renders it as a static React site, with Algolia providing search and Algolia Places handling address autocomplete. The project is maintained by Elastic Path, the company behind Elastic Path Commerce Cloud, and is released under the MIT License.
Developers who want a reference implementation for building Gatsby storefronts with a headless commerce backend can use this starter as a learning resource. Teams evaluating Elastic Path Commerce Cloud can test its features through the live demo store rather than building from scratch. Front-end engineers looking for a starting point for ecommerce projects can fork this MIT-licensed starter and replace the sample data with their own Elastic Path setup.
Yes, the starter is licensed under the MIT License, so you can use, modify, and distribute it freely, including for commercial projects.
It provides a working Gatsby storefront for Elastic Path Commerce Cloud, demonstrating how to build an ecommerce front end on top of headless commerce APIs with integrated Algolia search.
Yes, the storefront is designed to work with Elastic Path Commerce Cloud, so you'll need an Elastic Path account (or sandbox) to fully run the store with real product and checkout data. The repository links to Elastic Path documentation for setup.
The repository labels itself as a work in progress and encourages contributions, so it's best considered a reference implementation rather than a battle-tested production store. Use it as a starting point and adapt it for your requirements.
