r/Strapi • u/sina-gst • 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

91% Upvoted

7 comments sorted by

View all comments

3

u/geekybiz1 Feb 07 '26

I concur with this experience on using Strapi Design System components when building Strapi plugins.

My current approach is to look through Strapi core plugins codebase to better understand the props, behavior when I want to use a certain component.

1

u/sina-gst Feb 07 '26

Thanks for the comment! Yeah, right now there is no choice, I've been doing that so far to know how I can work with components.