Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start using UI component library #325

Open
arkid15r opened this issue Jan 1, 2025 · 4 comments
Open

Start using UI component library #325

arkid15r opened this issue Jan 1, 2025 · 4 comments
Assignees

Comments

@arkid15r
Copy link
Collaborator

arkid15r commented Jan 1, 2025

Is your feature request related to a problem? Please describe.
Similar to #8 where we've researched and picked frontend framewords to work with we need to make a decision on what we want to use as our UI components library.

Describe the solution you'd like
Assess pros and cons of:

  • Shadcn
  • Tailwind UI
  • Material UI
  • Chakra UI
  • React-Bootstrap
  • other option
    and decide on the optimal solution for OWASP Nest.
@nitinawari
Copy link
Collaborator

@arkid15r Shadcn is going to be a good option because we are already using Tailwind CSS, which allows us to highly customize components. Additionally, it is widely adaptable with React and TypeScript.

@TenzDelek
Copy link
Collaborator

I wanted to share some thoughts regarding this . While the proposal to adopt a UI component library like shadcn has its merits, I believe we should consider developing our own custom design system instead. A custom design system would allow us to create unique, on-brand experiences while maintaining flexibility in our design choices. It would also enable us to optimize our UI components for our specific use cases, potentially improving user experience and performance. I'm confident that investing in a custom design system will yield long-term benefits for our organization, empowering us to create distinctive and efficient user interfaces that can evolve with our product and brand.
I'd be happy to discuss this with the team regarding this. cc @arkid15r

@TenzDelek
Copy link
Collaborator

I wanted to share some thoughts regarding this . While the proposal to adopt a UI component library like shadcn has its merits, I believe we should consider developing our own custom design system instead. A custom design system would allow us to create unique, on-brand experiences while maintaining flexibility in our design choices. It would also enable us to optimize our UI components for our specific use cases, potentially improving user experience and performance. I'm confident that investing in a custom design system will yield long-term benefits for our organization, empowering us to create distinctive and efficient user interfaces that can evolve with our product and brand. I'd be happy to discuss this with the team regarding this. cc @arkid15r

also want to add that, if we are opting for shipping faster, then definitely a component library would be a better option, but for long term, I am strongly with the notion of design system.

@arkid15r
Copy link
Collaborator Author

arkid15r commented Jan 2, 2025

@TenzDelek it's great to have different perspective here. Please join the Slack discussion, let's figure that out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

3 participants