A template for Payload to power websites from small to enterprise. There is a complete front-end website made explicitly for this template which can be found here.
Core features:
For details on how to get this template up and running locally, see the development section.
The Payload config is tailored specifically to the needs of most websites. It is pre-configured in the following ways:
See the collections documentation for details on how to extend this functionality.
-
Users are auth-enabled and encompass both admins and public users based on the value of their
rolesfield. Onlyadminusers can access your admin panel to manage your website's content whereasuserhas limited access to the platform, see Access Control for more details.For additional help, see the official Auth Example or the authentication docs.
-
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. They can also be nested inside of one another, for example "About > Team". See Nested Docs for more details.
-
All posts are layout-builder enabled so you can generate unique layouts for each post using layout-building blocks, see Layout Builder for more details. They can also be nested inside of one another, for example "News > World". See Nested Docs for more details.
-
This is the uploads-enabled collection used by pages and products to contain media, etc.
-
A taxonomy used to group posts together. Categories can be nested inside of one another, for example "News > World". See the official Payload Nested Docs Plugin for more details.
See the globals documentation for details on how to extend this functionality.
-
HeaderThe data required by the header on your front-end, i.e. nav links, etc.
-
FooterSame as above but for the footer of your site.
Basic role-based access control is setup to determine what users can and cannot do based on their roles, which are:
admin: They can access the Payload admin panel to manage your website. They can see all data and make all operations.user: They cannot access the Payload admin panel and have a limited access to operations based on their user (see below).
This applies to each collection in the following ways:
users: Only admins and the user themselves can access their profile. Only admins can create and delete users.pages: Everyone can see published pages but only admins can see drafts and create, update, and delete pages.posts: Same as pages.
For more details on how to extend this functionality, see the Payload Access Control docs.
To enter preview mode we format a custom URL using a preview function in the collection config. When a user clicks the "Preview" button, they are routed to this URL along with their http-only cookies and revalidation key. Your front-end can then use the payload-token and revalidation key to verify the request and enter into its own preview mode.
For more information, see the official Preview Example.
If your front-end is statically generated then you may also want to regenerate the HTML for each page as they are published, sometimes referred to as Incremental Static Regeneration. To do this, we add an afterChange hook to the collection that fires a request to your front-end in the background each time the document is updated. You can handle this request on your front-end and regenerate the HTML for your page however needed.
For more information, see the official Preview Example which includes ISR.
This template comes pre-configured with the official Payload Nested Docs Plugin so you can easily create hierarchies of pages, posts, and categories. A front-end solution for this can be found here.
Pages and posts can be built using a powerful layout builder. This allows you to create unique layouts for each page or post. This template comes pre-configured with the following layout building blocks:
- Hero
- Content
- Media
- Call To Action
- Archive
A complete front-end solution for this can be found here.
This template comes pre-configured with the official Payload SEO Plugin so you can easily manage metadata for each page of your website. A front-end solution for this can be found here.
This template comes pre-configured with the official Payload Redirects Plugin so you can properly redirect content as your website scales. A front-end solution for this can be found here.
For additional help, see the official Redirects Example.
To spin up the template locally, follow these steps:
- First clone the repo
- Then
cd YOUR_PROJECT_REPO && cp .env.example .env - Next
yarn && yarn dev(ordocker-compose up, see Docker) - Now
open http://localhost:8000/adminto access the admin panel - Create your first admin user using the form on the page
That's it! Changes made in ./src will be reflected in your app—but your database is blank. You can optionally seed the database with a few pages and posts, more details on that here.
Alternatively, you can use Docker to spin up this template locally. To do so, follow these steps:
- Follow steps 1 and 2 from above, the docker-compose file will automatically use the
.envfile in your project root - Next run
docker-compose up - Follow steps 4 and 5 from above to login and create your first admin user
That's it! The Docker instance will help you get up and running quickly while also standardizing the development environment across your teams.
To seed the database with a few pages and posts you can run yarn seed.
NOTICE: seeding the database is destructive because it drops your current database to populate a fresh one from the seed template. Only run this command if you are starting a new project or can afford to lose your current data.
To run Payload in production, you need to build and serve the Admin panel. To do so, follow these steps:
- First invoke the
payload buildscript by runningyarn buildornpm run buildin your project root. This creates a./builddirectory with a production-ready admin bundle. - Then run
yarn serveornpm run serveto run Node in production and serve Payload from the./builddirectory.
The easiest way to deploy your project is to use Payload Cloud, a one-click hosting solution to deploy production-ready instances of your Payload apps directly from your GitHub repo. You can also deploy your app manually, check out the deployment documentation for full details.