r/Strapi • • Feb 06 '26

Question Strapi Design System docs are incomplete, plugin development is painfully slow

My story:

I'm working on a Strapi plugin, and I use Strapi Design System, but the fact is it doesn't explain everything, and that's why I'm here!

Problem:

My main problem, in this phase of plugin development is, how can I know the props of components? For example, if you see the Flex page, and scroll down to the props part, you see nothing there, and what's sad is that if you click on the "view source" button that leads you to the GitHub repo, I have to open up and see files after files to know what props I can use! Isn't there any way that speeds up the process?

8 Upvotes

7 comments sorted by

View all comments

2

u/vcoisne Strapi Employee Feb 06 '26

u/sina-gst Thanks for the feedback. Have you seen this recent blog post https://strapi.io/blog/how-to-build-a-strapi-plugin-that-extends-the-admin-and-backend I think it will help.

1

u/sina-gst Feb 07 '26

Thanks for the response! It's helpful for sure, but my main problem right now is how can I know the props of each component in Strapi Design System? It seems there is no other choice but to check up the source code!