Example repo using Builder.io for drag and drop page building with Shopify hydrogen
git clone https://github.com/BuilderIO/builder-shopify-hydrogen
cd builder-shopify-hydrogen; yarn
builder.init
calls with your API key: https://www.builder.io/c/docs/using-your-api-key#finding-your-public-api-keyyarn dev
page
model and change the Editing URL to http://localhost:3000
/builder/testing
http://localhost:3000/builder/testing
and see your page!Explore more in the Builder.io developer docs
Hardcoding layouts for frequently changing content bottlenecks your team and makes releases messy
Using an API-driven UI allows you to:
In Builder, content is structured in models, and customized with custom fields and targeting
Read more about how builder works here
See here for examples on how to structure a site with Builder
Requirements:
yarn
yarn dev
Remember to update shopify.config.js
with your shop's domain and Storefront API token!
To run a local preview of your Hydrogen app in an environment similar to Oxygen, build your Hydrogen app and then run yarn preview
:
yarn build
yarn preview
yarn build
Then, you can run a local server.js
using the production build with:
yarn serve
There are a lot of ways you can use Builder for your site. Some of the main questions you'll want to ask yourselves - what on your site should be in your code vs in Builder.
As a general rule, parts of your site that should be managed by non developers should probably be in Builder. Parts that are complex with a lot of code, should probably be in your codebase. Using custom components in your Builder content can help you strike a good balance here as well
Here are some examples we recommend for how to structure various pages on your site, for instance for a headless commerce site:
Builder.io gives you a ton more power and control than just page building. Check our guides on
Additional framework support:
As well as some handy power features like:
Questions? Requests? Feedback? Chat with us in our Discord!
Problems? Requests? Open an issue. We always want to hear feedback and interesting new use cases and are happy to help.