Skip to content

⚡ Next.js storefront for high-performance eCommerce with AI features and one-click deployment

License

Notifications You must be signed in to change notification settings

Blazity/enterprise-commerce

Repository files navigation

HERO

GitHub Actions Workflow Status GitHub License GitHub contributors Discord Blazity Blazity

🚀 Launch your high-performance Shopify storefront in minutes, not weeks, with this Next.js commerce starter. Leverage the power of Vector Search and AI to deliver a superior online shopping experience without the development headaches.

Run this command and let our CLI do the job or see our documentation for manual setup instruction.

$ yarn create commerce

See the live demo or deploy it straight to Vercel:

Deploy with Vercel

Note: To enable all features, ensure required environment variables are set in your .env.local

Features

  • Next.js App Router & Turborepo
  • React Server Components (RSCs), Suspense and Streaming
  • Server Actions
  • Dynamic OG Images
  • AI Vector Search
  • Lightning fast search & filtering
  • Designed with v0
  • Vercel Toolbar (feature flags, comments, deployment sharing, etc.)
  • AI Image captioning
  • Perfect Performance & SEO
  • Extremely strict TypeScript
  • Draft Mode
  • A/B Tests
  • Shadcn UI
  • TailwindCSS
  • Analytics (GTM, Vercel)
  • Highly Scalable SEO Redirects (Bloom Filters)
  • Complete and fast CI/CD pipelines
  • Platform agnostic (integrated with Shopify by default)
  • Easy migration - migrate your existing solution in minutes
  • Conventional commits git hook
  • Playwright - write end-to-end tests like a pro
  • Storybook - create, test, and showcase your components
  • T3 Env - manage your environment variables with ease
  • Patch-package - fix external dependencies without losing your mind
  • Components coupling and cohesion graph - a tool for managing component relationships
  • Category Landing Page detached from Product Listing for fast SEO indexing & better performance
  • Reviews & Ratings with Judge.me

Architecture

In Enterprise Commerce high-level architecture, Meilisearch serves as the primary source for all product data and potentially other types of data in the future. The system is designed to easily integrate AI personalization tools without needing to modify any frontend code. While we are integrated with Shopify by default, we are not tightly bound to it, and you can use any system that works with Meilisearch and can adapt data to our format.

From a structural viewpoint, we use a monorepo (Turborepo) to manage packages, even though we currently have only one Next.js app. We chose this setup because it prepares us for future developments, which will include additional apps. This arrangement helps keep the packages well-separated and self-contained.

architecture diagram

Performance

At Blazity, we prioritize speed. Enterprise Commerce is meticulously crafted to deliver top-notch performance for your online store.

Lighthouse scores offer a valuable comparison tool, but they don’t directly translate to SEO or user experience (UX). For a true picture, prioritize real user data. Tools like CrUX or Vercel Speed Insights provide user-based performance metrics, ensuring your online store delivers a seamless experience for your customers.

performance diagram

🤝 Contribution

Contributions are always welcome! To contribute, please follow these steps:

  1. Fork the repository.
  2. Create a new branch with a descriptive name.
  3. Make your changes, and commit them using the Conventional Commits format.
  4. Push your changes to the forked repository.
  5. Create a pull request, and we'll review your changes.

Support

If you're looking for help or simply want to share your thoughts about the project, we encourage you to join our Discord community. Here's the link: https://blazity.com/discord. It's a space where we exchange ideas and help one another. Everyone's input is appreciated, and we look forward to welcoming you.


Blazity Discord Banner

📜 License

This project is licensed under the MIT License. For more information, see the LICENSE file.