We decided to host a major CSS coding battle tournament here on Syntax with 14 of the greatest CSS engineers out there.

And then two other competitors in that competition, that being Wes and myself, competing in CSS battles.

And we've been doing a lot of CSS battles here on Fridays

and our three devs videos with CJ West and I,

but we wanted to take it one step further.

And so we built our own CSS coding battles platform.

So we're going to be talking all about how that works the stack,

how the stack works itself, what we're using for various components, why it's cool. And we're

going to be diving into some of the challenges that we had getting this thing up and running,

because let me tell you, this has been a massive sprint to build our own platform

from scratch just to use for this CSS coding tournament. My name is Scott Tolensky. I'm a developer

from Denver with me as always as West Boss. What's up Wes? Hey, excited to talk about this. This has been

very fun to work on the last, what, two weeks or so. I joined in about two weeks ago

and helped crank out issues, but it's a really cool platform. It's all local first, all

sinks. It's all fast as heck since felt really cool. Love it. Yeah, I will say it's not

local first. And I'm going to push back on that.

But I do think that's an important part of this distinction here because we'll talk about why it's not local first.

We'll talk about the tech.

It is using zero sync, which definitely was a platform that was initially described as being local first.

But they've really kind of shifted that message a little

bit because I don't think it really truly falls under that. But I think you saying at the local

first is not a bad thing, Wes. I think that is how most people might think about this and look

...