This open-source coaching app uses Payload CMS and Next.js for coach-managed training plans, with a CONTRIBUTING guide and pull-request template.
The extension I propose is straightforward: A source-owned landing or program block can demonstrate a repeatable Payload content-extension path without touching the workout domain model.
I maintain Payload Components, an MIT registry and CLI for Payload v3 + Next.js. Its typed blocks install as source, and the CLI handles collection registration, renderer mapping, generated types, and the admin import map.
I’ve scoped the first contribution to one source-owned block that follows the repository’s current conventions and leaves unrelated application behavior untouched. That gives adopters a repeatable extension pattern without a runtime package or hidden abstraction.
Point me to the preferred example or documentation location, and I’ll send the focused patch.
This open-source coaching app uses Payload CMS and Next.js for coach-managed training plans, with a CONTRIBUTING guide and pull-request template.
The extension I propose is straightforward: A source-owned landing or program block can demonstrate a repeatable Payload content-extension path without touching the workout domain model.
I maintain Payload Components, an MIT registry and CLI for Payload v3 + Next.js. Its typed blocks install as source, and the CLI handles collection registration, renderer mapping, generated types, and the admin import map.
I’ve scoped the first contribution to one source-owned block that follows the repository’s current conventions and leaves unrelated application behavior untouched. That gives adopters a repeatable extension pattern without a runtime package or hidden abstraction.
Point me to the preferred example or documentation location, and I’ll send the focused patch.