Add Payload Components to component collections - #629
Open
Ducksss wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
awesome-react-components separates full Component Collections from individual controls and UI utilities.
Payload Components belongs in that collection layer for React/Next.js teams using Payload v3: 67 MIT typed blocks install as owned source, and the companion CLI handles Pages registration, renderer mapping, generated types, and the admin import map. Readers gain a production-oriented CMS block set that remains fully editable.
The patch adds one repository-and-docs line at the end of Component Collections.