Getting Started

Atomic Payload is a website builder designed to simplify the development process without introducing roadblocks to implementing functionality. It enables solo developers and agencies to produce higher-quality websites with less friction.

To achieve this, Atomic Payload separates client services from infrastructure development. When working on a client’s site, all changes are made within the Payload CMS admin dashboard, without touching the underlying code.

The reason for this is we want a single point of failure when working on client sites. Meaning if what your working on doesn't work, the problem is located in one place, not 10 different possible places. The benefits include reduced debugging time, lower domain knowledge requirements, and easier project handoffs.

That single point of failure is Tailwind. In terms of simplicity, flexibility, and adoption, Tailwind is the only viable choice for a web builder like this. Combined with a recursive atomic block structure and a basic understanding of HTML, you can build virtually anything directly within the Payload admin UI.

The Atomic Payload Github repository has the most up to date instructions on getting a working version started. The process should take less than 15 minutes and includes a website example seed.

Apologies for the incomplete documentation, but much of the actual Atomic Payload functionality can be intuited with a basic understanding of html and tailwind. It was determined making Atomic Payload available, then filling out documentation, made the most sense.

The main thing to know when getting started with Atomic Payload is the Atomic Block. Which is a child block used in several collections to allow for a recursive block structure. The Atomic Block has several variants, which each handle different functionality.

Its recommended you explore the seeded website you established in the setup steps to determine how the atomic block functions. The provided "testing" page, and header contain all of the Atomic Blocks use cases.