-
Notifications
You must be signed in to change notification settings - Fork 359
Share Your Feedback on Vibes Components in Catalyst #2001
Hey devs!
As we continue refining Catalyst, we’d love your input on how the Vibes components are shaping your development experience. Your insights will help us improve usability, extensibility, and overall efficiency.
A few quick questions for you:
💥How has your experience been working with Vibes components so far? (Any frustrations or wins?)
💥How has your implementation approach changed since adopting Vibes components? (Easier? More restrictive? More flexible?)
💥How does this abstraction layer impact your ability to extend and customize components for your needs?
Your feedback is invaluable—drop your thoughts on this discussion!
Looking forward to your insights!
All reactions
-
😄 1 -
🚀 1
Replies: 1 comment 5 replies
The introduction of Vibes components has certainly improved our performance. However, our biggest challenge has been tracking the breaking changes on Catalyst and synchronizing them with our modified version. We immediately began creating our own Vibes components and kept the core in sync with the Catalyst canary, but it felt like it came out of nowhere before the full v1.0 release. We've been working hard to keep up, resulting in the creation of many fallback components 😄
All reactions
What has been your strategy for creating your own catalyst theme? Have you taken the Vibes Soul and altered it for your own requirements? I'd be really interested on what you or anyone else is doing with Vibes as the documentation is thin on this.
All reactions
we decided to keep core intact. added catalyst as remote ref. added new folder inside vibes and add new alias to direct soul components to our custom ones.
All reactions
Thanks for the reply! That kinda sounds like what I was thinking which was to create a duplicate soul theme and altering that accordingly. Are you just updating selected components in your new alias, altering the catalyst side to use the new alias and leaving the rest to be handled by soul?
All reactions
i just duplicated the soul. kept it intact. but added alias for our theme. it little confusing but it does the job. i think if they use paths like @/vibes/current it would be much better. but for now i added alias to direct souls to our components path "@/vibes/souls": ["./vibes/opt7"],
All reactions
-
👍 2
Thanks again!