Custom Views / Component needs to be the next big focus of Payload. #3960
Replies: 2 comments 2 replies
-
|
I read everything you wrote and I agree, having spoken with members of the team in various occasions I can also tell you they're very much aware of these pain points.
Can you expand on this point for me please? What exactly are you missing or looking for when you mean searchable API documentation |
Beta Was this translation helpful? Give feedback.
-
|
Everything that is exposed by Payload (whether local API or components) should be documented online with functionality description, parameter descriptions, and usage examples. Right now Payload doesn't expose this information on the web and navigating TypeScript definitions isn't fun. For example: it took me a lot of source code reading (where I had to clone the payload source repo) to find out what |
Beta Was this translation helpful? Give feedback.
-
|
exactly one year later and all the mentioned pain points remain in the new 3.0 beta |
Beta Was this translation helpful? Give feedback.
-
|
There are definitely improvements with the new 3.0 beta, but I agree that there is a lot of room for improvement that should be considered high priority. I created a discussion recently about the RelationshipSelect field not being usably exposed, and there are others too. Each field type should have an exposed In the event that we want to completely roll our own input, helper functions used internally should also be exposed. In the case of building out a RelationshipInput, for example, utils such as Lastly, passing in types to some of the core functions should be expanded. One example is the user as unknown as User |
Beta Was this translation helpful? Give feedback.
-
Payload is great as a headless CMS - no questions about that. But most people need more than what the stock Admin UI provides, and right now, putting in custom views is an uphill battle.
I've been trying to put together a simple custom view and I ran into many problems:
<RenderFields>, you realize you might not need to reinvent as many wheels)<head>(this might be fixed when we move to Next?)I think it's fair to say most people need to customize the Admin UI beyond what's provided in stock every single day, and right now the development experience is far from great. I really hope the team makes this their next big focus because this is the last 10% that would make Payload a truly killer CMS.
Beta Was this translation helpful? Give feedback.
All reactions