NhaphoHCM Backend

This template is in BETA.

Payload Ecommerce Template

This template is in BETA.

This is the official Payload Ecommerce Template. This repo includes a fully-working backend, enterprise-grade admin panel, and a beautifully designed, production-ready ecommerce website.

This template is right for you if you are working on building an ecommerce project or shop with Payload.

Core features:

- Pre-configured Payload Config - Authentication - Access Control - Layout Builder - Draft Preview - Live Preview - On-demand Revalidation - SEO - Search & Filters - Jobs and Scheduled Publishing - Website - Products & Variants - User accounts - Carts - Guest checkout - Orders & Transactions - Stripe Payments - Currencies - Automated Tests

Quick Start

To spin up this example locally, follow these steps:

Clone

If you have not done so already, you need to have standalone copy of this repo on your machine. If you've already cloned this repo, skip to Development.

Use the create-payload-app CLI to clone this template directly to your machine:

Development

1. First clone the repo if you have not done so already 1. cd my-project && cp .env.example .env to copy the example environment variables 1. pnpm install && pnpm dev to install dependencies and start the dev server 1. open http://localhost:3000 to open the app in your browser

That's it! Changes made in ./src will be reflected in your app. Follow the on-screen instructions to login and create your first admin user. Then check out Production once you're ready to build and serve your app, and Deployment when you're ready to go live.

How it works

The Payload config is tailored specifically to the needs of most websites. It is pre-configured in the following ways:

Collections

See the Collections docs for details on how to extend this functionality.

- #### Users (Authentication)

Users are auth-enabled collections that have access to the admin panel and unpublished content. See Access Control for more details.

For additional help, see the official Auth Example or the Authentication docs.

- #### Pages

All pages are layout builder enabled so you can generate unique layouts for each page using layout-building blocks, see Layout Builder for more details. Pages are also draft-enabled so you can preview them before publishing them to your website, see Draft Preview for more details.

- #### Media

This is the uploads enabled collection used by pages, posts, and projects to contain media like images, videos, downloads, and other assets. It features pre-configured sizes, focal point and manual resizing to help you manage your pictures.

- #### Categories

A taxonomy used to group products together.

- ### Carts

Used to track user and guest carts within Payload. Added by the ecommerce plugin.

- ### Addresses

Saves user's addresses for easier checkout. Added by the ecommerce plugin.

- ### Orders

Tracks orders once a transaction successfully completes. Added by the ecommerce plugin.

- ### Transactions

Tracks transactions from initiation to completion, once completed they will have a related Order item. Added by the ecommerce plugin.

- ### Products and Variants

Primary collections for product details such as pricing per currency and optionally supports variants per product. Added by the ecommerce plugin.

Globals

See the Globals docs for details on how to extend this functionality.

- Header

The data required by the header on your front-end like nav links.

- Footer

Same as above but for the footer of your site.

Access control

Basic access control is setup to limit access to various content based based on publishing status.

- users: Users with the admin role can access the admin panel and create or edit content, users with the customer role can only access the frontend and the relevant collection items to themselves. - pages: Everyone can access published pages, but only admin users can create, update, or delete them. - products variants: Everyone can access published products, but o