componentdriven / componentdriven.org Goto Github PK

I would love to nominate Stencil.js to be added to the homepage under development tools. It embodies the component driven methodologies and has a great community and documentation.

I'm not affiliated with Stencil, I am just a user who really enjoys the tooling.

Thank you for your consideration.

Hey,

First of all. Great initiative and superb design!

I thought maybe it'd make sense to add UI Playbook to either the list of tools or "learn more" section on the site?

Essentially, UI Playbook is a documented collection of common UI components, their functionality, best practices, accessibility requirements, and examples. And, it's fairly implementation agnostic, so the practices are generally applicable!

If this seems fitting, I'd gladly make a PR. If not, keep up the good work! ✌️

Hi! I found the overview in this website pretty helpful, but I think the mention of Rails could be updated. While Rails has traditionally been more domain driven than component driven, GitHub wanted to experiment with having a similar experience to React in Rails views, so they created ViewComponent. While it's technically not part of Rails itself, GitHub still uses it in production, and it's possible to render ViewComponents like you'd normally render Views in other parts of Rails (like the system test framework).

Please consider:

1. Either not mentioning Rails as a framework that doesn't support component driven reuse, or clarifying that ViewComponent can be used along with Rails
2. Adding Rails or ViewComponent as a development tool

Note: There are technically other alternatives for Rails that integrate with existing component frameworks, like React Rails. However since we already mention frontend component frameworks, I don't think we need to mention specific integrations for them.

IMO Lit should be added to the list of tools for authoring components. I know web components in general are listed, but I think Lit is an important enough framework to include on it's own.

Hi folks,

Thanks for the initiative!

I would like to propose Specify to the list of design tools.

Specify acts as a central platform that enables the continuous collection, centralization and distribution of all UI decisions (design tokens, assets and components) — from design tools to development tools.

We are still in beta but we have hundreds of teams who have been using us for more than a year, and we have lots of exciting things coming up!

My team and I would love to be part of this initiative :)

On NotComponentDriven.tsx, PHP is listed as a framework next to Rails and Django:

Backend frameworks such as Rails, Django and PHP that treat UI reuse as an afterthought and discourage widespread component reuse.

Suggestion:
List an actual PHP framework (like Laravel or Symfony?)

I've noticed there's a development entry for web components, but not standards. While not all component driven development is done with with web components, most component frameworks support web components, so I think it would be helpful to mention the standards separately.