CSS

And so it also has some pretty good integrations.

And because it's not an open source platform, but it uses open technology, HTML, CSS and JavaScript, it's very easy for me to use AI to vibe code my own plug-ins.

that I use to improve the overall experience of Obsidian across platform for me.

So I pay four bucks a month for Obsidian Sync, which means that my vaults are going to be the same no matter what device I am on, and that is excellent.

They're using Vite for the build tooling.

They also use Tailwind CSS for the styling.

But the real secret weapon here is Playwright.

Right.

Ah, I see.

Yeah, it tries to build a perfectly robust logical hierarchy.

Kimi, on the other hand, might just map visual coordinates directly to CSS rules.

It doesn't overthink the underlying logic of the page.

That's what we're doing with technical SEO.

We're doing CSS, the cascading style sheets, HTML, JavaScript, right? Before, I'm not super technical.

I know enough to get by to be a good SEO.

But like, hey, I need to do this schema markup for a local laundromat.

Literally, their whole job is to think about that end user and make sure that there's cohesion across their experiences.

So on the surface, I could see why that would be an assumption you'd make about the roles, but- When you unpack that, when you look under the covers, the way code works, like even just something as simple, not simple, but something like CSS, right? We make a class name so that we can systematically apply styles to things, right? I mean, the underpinnings of engineering are systematic, you know? Yeah.

And so part of me wonders if there's just like, it's been, and it's true also about the background of design.

I did a session with Sparkbox.

It's solving problems.

I did some HTML and CSS back in high school.

It had changed quite a bit, I realized.

I'm also glad I didn't go into coding now, looking at how things are.

So did designers need to learn how to code or do they mainly need to understand how products are built?

I think I've for the, since I don't know if it comes from the fact that I started as a developer and had to understand basic HTML, CSS in order to construct my own designs.

But I think I've always been a big fan of designers and I've always looked for designers when I hired for my studio designers who had some sort of technical understanding.

at least they had an understanding of what is feasible.

Especially working with layout, which is a lot of work behind any new layout you should prepare.

For example, you take a CSS file from your website and you say to Cloud Code, prepare a new theme using this file this css file and boom it's done you only need make a couple of fixes or yeah and and that's it so uh it changes the way we will work with file maker we will spend more time thinking about how we want the things done but we will not code anymore I won't do this.

Yeah, I think we will.

But I mean, as FileMaker developers, when it writes script code, we'll be able to look at it, understand it, go, why did it do it that way? And then we can say, yeah, my standard is this.

But even that, the coding side has changed a lot, you know, quite a lot.

The summer of 2025, I was using it, sure, to write some snippets and CSS for me, you know, check some CSS or write some CSS or some JavaScript or PHP or whatever.

Maybe even write a little script or a little thing, you know, And I would copy and paste it.

I would still be doing most of the coding.