+1. Coincidentally, we have just been discussing this issue here: Review and consolidate components · Issue #2697 · openedx/frontend-app-authoring · GitHub
As you can read in that thread, Schema is working on a proper Figma file for Paragon.
But for now, Paragon is developed very slowly and I do wish that we had just used one of the standard React component libraries that are out there. Paragon was created to be more accessible compared to Bootstrap, but most of the modern React component libraries have handled accessibility very well, and they have larger teams that proactively maintain their a11y features, whereas Paragon struggles to get improvements planned and implemented. And since Paragon is incomplete, people often implement their own additional components that don’t follow a11y best practices. So in my opinion we now have a less accessible, less useful framework than other frontend applications.
What’s more, Paragon is currently based on an old version of bootstrap and SCSS, which are eventually going to stop working at need to be replaced with something else. Most other frameworks are built around Tailwind or similar which is much nicer to work with and has much faster builds. Brian Smith has chatted with me about replacing bootstrap with something else within Paragon as the library evolves, but that’s going to be a huge project and I’m not sure how we’ll find the developer time to make it happen - plus it means a lot of the extra components that we have created within MFEs may need to be refactored too.