v0.3.0
Atomic Payload — v0.3.0 (Initial public release)
First public release of the
@pro-laico/*plugin ecosystem.
Summary
This release transforms Atomic Payload from a single Payload + Tailwind starter template into a full, plugin-based monorepo. The functionality that used to live inside one template is now factored into 12 installable @pro-laico/* packages plus the create-atomic-payload scaffolder — each independently documented, versioned in lockstep, and published to npm.
You no longer have to fork the whole template to get one capability: install just the plugin you need (fonts, icons, styles, …) into an existing Payload app, or scaffold the full stack with create-atomic-payload.
What's new
The packages fall into three groups — a @pro-laico/core foundation, the standalone plugins usable on their own, and the tools the standalones and the template build on — plus the create-atomic-payload CLI.
Foundation
@pro-laico/core— the shared base every other package builds on: kernel types (PayloadAugment/Get<>type augmentation), APF (Atomic Payload Functions), shared utilities, cache + cache revalidation, the JSON-schema plugin, and admin/frontend UI primitives.
Standalones
Plugins you can drop into any Payload + Next.js project on their own.
@pro-laico/styles— designSet + shortcutSet collections, token fields, the CSS preflight pipeline, and the UnoCSS /processDesignSetprocessor. The single source of truth for all CSS handling (frontend + Payload admin/runtime).@pro-laico/icons— Icon and IconSet collections, an SVG-optimizingformatSVGhook, SVG-extraction helpers, and theAtomicIconcomponent.@pro-laico/fonts— a Font upload collection and a CLI that downloads fonts from the active design set to disk fornext/font/local.@pro-laico/tracking— Tracking global plus PostHog, Google Tag Manager, and Vercel Analytics providers behind a compositeTrackingProvider.
Tools
The runtime packages the standalones and the atomic-payload template compose with — you rarely install these directly.
@pro-laico/atomic— the runtime engine: action blocks, thebeforeChangehook + CSS/UnoCSS processor, the form-processing pipeline, and the child-blocks system that the media plugins compose into.@pro-laico/site— opinionated site shape: Pages, Header, Footer collections plus SiteMetaData and Settings globals, all registered by onesitePlugin().@pro-laico/images— Images + Favicons upload collections, aFaviconFieldhelper, anImageChildblock factory, and a plugin factory.@pro-laico/mux-video— a localMuxVideoextension collection with Atomic Payload defaults (thin wrapper around@oversightstudio/mux-video).@pro-laico/richtext— theRichTextChildblock, a default Lexical editor preset, and a JSX renderer for serialized Lexical content.@pro-laico/seed— aPOST /api/seedendpoint and aBeforeDashboardadmin banner with a SEED DATABASE button, shipping an opinionated default seed that consumers can override.@pro-laico/zap— zod with Atomic Payload extensions: a registry-aware schema layer (z.ap) for registering/retrieving schemas typed againstAtomicRegistry, used for end-to-end type generation across the stack.
Scaffolder
@pro-laico/create-atomic-payload—npm create @pro-laico/atomic-payloadscaffolds a new project or a single-plugin example.
New project surfaces
- Documentation site (
docs/) — a Fumadocs site covering every plugin, feature guide, core concept, getting-started path, example, and the template. - Standalone examples (
examples/) —fonts-only,icons-only,styles-only: minimal apps that exercise one plugin in isolation. - Starter template (
templates/atomic-payload) — rewired to consume the published plugins instead of bundling everything inline.
Tooling & infrastructure
- Lockstep release tooling (
tools/releaser) — one version across the whole workspace;pnpm releasestamps + tags,pnpm publish-packagespublishes every public package (Payload-style). - CI publishing —
.github/workflows/release.ymlpublishes all@pro-laico/*packages with npm provenance when av*tag is pushed. - Biome for lint/format across the monorepo.