Repository navigation
@payload/ui needs documentation #9489
Replies: 5 comments 3 replies
|
I agree! |
|
A lot of the individual components (inputs, buttons, etc) aren't too difficult to figure out but things like Pulling in other UI libraries feels wrong but is infinitely easier to do at the moment than pull in anything from |
|
For a platform that prides itself on customizability, it's definitely a chore to find some of these features and components. You'd think clear documentation would be a top priority. Unfortunately, to figure out some things to you have to reverse engineer existing code or ask in the discord. |
|
I've gone ahead and started a PR for this! Not much documented yet, so please feel free to help out! #11469 |
|
Appreciate everyone's patience here—and I'm happy to report a PR has just been approved to address this gap! I took a first pass through our many components and built a new block for our docs so you can see the component, see the CSS it uses (how to target it) and read through the necessary docs + props for each component. I've already started on the 4.0 variant for this initial work and that will come as a fast follow. ui-components-preview.mp4 |
Uh oh!
There was an error while loading. Please reload this page.
The problem: As i make many customisations to the admin backend (adding new fields, views and so on) i find it hard to find the right components from payload that are already there. Its also particularily hard to find out how they work. I have to dig into the repository all the time especially if my goal is that these custom changes integrate seamless in the UI of the existing admin.
The solution:
I would love to see an separate documentation of the the @payload/ui package or even an storybook with autodocs. This would help build custom features for the admin faster and easyier.
It would also boost creation of plugins i suppose as easier implementation brings mote people to actual building new stuff for the payload admin.
All reactions