DEV Community

Discussion on: Meet Webpixels 2.0

Collapse
 
robertandrews profile image
Robert Andrews • Edited

1.

As a final thought, Webpixels CSS is not a theme or a set of custom classes, but rather a more structured framework for helping us build the UI stuff we need. So, in my oppinion there is no need for custom prefixes, since we will always keep it in sync with the latest Bootstrap version. There is no desire to switch between frameworks. We'll keep Bootstrap as our foundation.

What I meant was... what if I wanted to switch between Bootstrap UI frameworks, ie. From Webpixels to another Bootstrap UI framework. Maybe useful to see that .avatar is not a standard component by calling it .wp-avatar? Or not... maybe Bootstrap introduces .avatar and then you are already ahead of the game and compatible?

I'm just a little intrigued to have a sense of how many, and which, classes are custom builds. From css/src/components/, it looks like only avatars, but maybe that's not the right place to look.

3.

Ah, I see... so the repo is the underlying CSS changes, but the Components is the mark-up for things like profile cards etc.

Anyway, it's all a lovely piece of work!

Thread Thread
 
extrabright profile image
Alexis • Edited
  1. Now I understand what you meant. Well, that could be tricky, but I think this is something we'll address in the near future. My goal for now is to provide and promote simplicity throughout the development process. Switching from one framework to another was never easy, but maybe we'll come up with a nice solution to fix that.

But as I said, we are keeping Webpixels CSS in sync with Bootstrap. And we are versioning our updates accordingly. If Bootstrap adds an avatar component, we'll update our framework and our UI library as well.

Thank you for all your nice words 🙏