Let's set the room on fire 🔥🔥🔥🔥 "The best @webflow devs do not use Client-first"

@masterflowmaker @webflow btw why webflowers invented a separate css system instead of using Tailwind? :D

@masterflowmaker @webflow What do you use?

@masterflowmaker @webflow The best Webflow devs can work with any tool, as long as they get the job done 🔥

@masterflowmaker @webflow > Makes a clickbait post > Doesn’t elaborate > Vanishes Truly peak Webflow community experience

@masterflowmaker @webflow What’s your take on Lumos in that case? 😆

@masterflowmaker @webflow Matías Pitters: Use what works best for you Also Matías Pitters: Best dEvS dOnT use client first! That’s like me saying “the best music listeners don’t listen to Taylor Swift!” just because I don’t listen to her 😂 how about just let people use what they prefer?

@masterflowmaker @webflow MAST is the MVP @NoCodeSupplyCo

@masterflowmaker @webflow Never used it. Have read the docs and could not find a single reason to use it despite it being glorified. It’s mega bloat to one’s process IMO. So far I used my own structuring but I’m diving deep into Lumos.

@masterflowmaker @webflow Lumos 🐐🪄

@masterflowmaker @webflow I don’t use any of those. “Div Block 66” serves me well🤡

@masterflowmaker @webflow Fellow MAST user and advocate here 👋 made with love from the folks at @NoCodeSupplyCo

@masterflowmaker @webflow

@masterflowmaker @webflow Idk how devs use Client First. I have my own, or MAST is my go to if using a framework

@masterflowmaker @webflow You aint wrong

I have a “client first inspired” approach in how I name classes and whatnot, but I definitely do not like the rigidity of frameworks in general. Especially when they try to put how to space and layout. I would rather have one element with special styling instead of adding a “spacer div”, etc.

@masterflowmaker @webflow 🥶

@masterflowmaker @webflow Div Block 31 😂

@masterflowmaker @webflow In agreement!

@masterflowmaker @webflow

@masterflowmaker @webflow

@masterflowmaker Well, the main reason to use client-first is "Don't deep stack classes" which is completely irrelevant in Webstudio (you can safely deep stack tokens and change them at any time).

@masterflowmaker @webflow i'm trying to make my switch to Lumos but I'm just too used to Client-first :( And also using Relume components

@masterflowmaker @webflow Fully agree. We use Lumos instead.

@masterflowmaker @webflow Okay, someone said it.

@masterflowmaker @webflow jep. been saying this for a while. you can spot pros from a mile.