Skip to content

Fork responsible for updating the usage of Elastic Path integration

License

Notifications You must be signed in to change notification settings

jimmy-ventura-elasticpath/nextjs-elasticpath

 
 

Repository files navigation

Next.js + Elasticpath + Builder.io example

This is a minimal example to get started with elastic path and builder.io, it renders product pages and landing pages and have theming support built-in.

Table of contents

Getting Started

Pre-requisites

This guide will assume that you have the following software installed:

  • nodejs (>=12.0.0)
  • npm or yarn
  • git

You should already have a Elasticpath account and store created before starting as well.

Introduction

After following this guide you will have

  • A Next.js app, ready to deploy to a hosting provider of your choice
  • Pulling live product information from Elaticpath
  • Powered by the Builder.io visual CMS

1: Create an account for Builder.io

Before we start, head over to Builder.io and create an account.

2: Your Builder.io private key

Head over to your organization settings page and create a private key, copy the key for the next step.

organizations drop down list

  • Click "Account" from the left hand sidebar
  • Click the edit icon for the "Private keys" row
  • Copy the value of the auto-generated key, or create a new one with a name that's meaningful to you

Example of how to get your private key

3: Clone this repository and initialize a Builder.io space

Next, we'll create a copy of the starter project, and create a new space for it's content to live in.

In the example below, replace <private-key> with the key you copied in the previous step, and change <space-name> to something that's meaningful to you -- don't worry, you can change it later!

git clone https://github.com/BuilderIO/nextjs-elasticpath.git
cd nextjs-elasticpath

npm install --global "@builder.io/cli"

builder create --key "<private-key>" --name "<space-name>" --debug

If this was a success you should be greeted with a message that includes a public API key for your newly minted Builder.io space.

Note: This command will also publish some starter builder.io cms content from the ./builder directory to your new space when it's created.

  ____            _   _       _                     _                    _   _ 
| __ )   _   _  (_) | |   __| |   ___   _ __      (_)   ___       ___  | | (_)
|  _ \  | | | | | | | |  / _` |  / _ \ | '__|     | |  / _ \     / __| | | | |
| |_) | | |_| | | | | | | (_| | |  __/ | |     _  | | | (_) |   | (__  | | | |
|____/   \__,_| |_| |_|  \__,_|  \___| |_|    (_) |_|  \___/     \___| |_| |_|

|████████████████████████████████████████| product-page: writing generic-template.json | 1/1
|████████████████████████████████████████| page: writing homepage.json | 2/2


Your new space "next.js elasticpath starter" public API Key: 012345abcdef0123456789abcdef0123

Copy the public API key ("012345abcdef0123456789abcdef0123" in the example above) for the next step.

This starter project uses dotenv files to configure environment variables. Open the files .env.development and .env.production in your favorite text editor, and set the value of BUILDER_PUBLIC_KEY to the public key you just copied. You can ignore the other variables for now, we'll set them later.

+ BUILDER_PUBLIC_KEY=012345abcdef0123456789abcdef0123
- BUILDER_PUBLIC_KEY=

4. Configure the project to talk to Easticpath

Open up .env.development and .env.production again, but this time set the Elasticpath client id.

BUILDER_PUBLIC_KEY=012345abcdef0123456789abcdef0123
+ ELASTICPATH_CLIENT_ID=xxxxx

7. Up and Running!

The hard part is over, all you have to do is start up the project now.

npm install
npm run dev

This will start a server at http://localhost:3000.

Go to your new space settings and change the site url to your localhost http://localhost:3000 for site editing.

8. Start building

Now that we have everything setup, start building and publishing pages on builder.io, for a demo on building something similar to the demo homepage, follow the steps in this short video

Deployment Options

You can deploy this code anywhere you like - you can find many deployment options for Next.js here. The following options support one click installs and are super easy to start with:

Deploy with Vercel

Deploy to Netlify

What's left?

  • functioning cart with product variations.
  • Images for products.

About

Fork responsible for updating the usage of Elastic Path integration

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • TypeScript 90.5%
  • JavaScript 5.0%
  • CSS 4.5%