Skip to content

Document a source-owned block path in Tietokilta/web #880

Description

@Ducksss

Tietokilta maintains a shared Next.js and Payload platform with an existing block-based page surface for its community website. Its users already work at the point where structured Payload content has to become polished, maintainable frontend sections.

Adding one source-owned block example would shorten that last mile: teams could start from typed editor fields, retain every installed file, and avoid hand-maintaining Pages, RenderBlocks, generated types, and the admin import map.

Payload Components is an MIT registry of 67 typed components for Payload v3 + Next.js 15/16. The companion CLI installs source and applies the Payload wiring as a reviewable git diff. Source: Ducksss/payload-components.

Proposed contained patch: document one hero-basic evaluation path in the existing README or example app, including the generated wiring and both source links. No runtime dependency or opaque package is introduced.

I’ll prepare the Tietokilta/web example against the repository’s maintained integration surface; redirect me only if a different example location is canonical.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions