Beta of V2 components
![cord icon logo](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fcord-icon.19285d53.png&w=32&q=75)
Hi, we wanted to share an update with you all.
In the past, you’ve asked for increased customization of Cord components, and we’ve told you that we were working on something.
Well, today is the day, we’d like to share the beta of our v2 components (Thread, Message, Composer, Avatar, and constituent components) that allow for replacement.
With these new components, you can get all the behavior that you normally get but swap out any particular piece for your own component. Don’t like our Avatar hover behavior, add your own. Want to add a custom menu item to Threads, go ahead. Want the composer to brew a cup of coffee on every key press, totally doable. This is designed to increase flexibility for you to build the app you want to build. Additionally, these components now all render in your React tree without going through web components so you should no longer see things rerender on different React cycles. We are really excited about what can be done with this, and we’d love your feedback on it. We are super happy to discuss it here on https://community.cord.com. We want to make sure that what we have built really does give you the functionality and flexibility you’ve asked for.
To use this, you’ll need to install the Cord SDK at version 1.42.1 (or later). Docs for the new components are available https://docs.cord.com/components?version=2.0 .
There is more documentation at https://docs.cord.com/customization/custom-react-components about the capabilities, and a working example that shows how to turn our thread into one like github (https://docs.cord.com/customization/custom-react-components/tutorial).
Exciting to see the updates here, but curious what the future looks like for companies without React codebases. Is the intent for the React v2 components to be the future of your component library and the web components will eventually be deprecated? Or will there be a future v2 version of the web components for other framework usages as well? Would definitely be concerned if the future of Cord only included React.
![cord icon logo](/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fcord-icon.19285d53.png&w=32&q=75)
Hi @John Woodruff, we're planning to continue supporting and improving the web components for the foreseeable future. We're starting with React components for our v2 because it's by far the most-used framework by our customers and we want to enable some new features that don't fit well with web components, but we plan to continue providing web components as the option for people using any framework, and we're open to building dedicated components for other frameworks if there's sufficient demand. Definitely not planning to become React-only.