Chris Soulaki

I'm glad I'm not the only one who looks at svelte commits just for Rich's beautiful storytelling 😂

Hit me up 👋

Wasn't webstudio built with Remix? Is this a completely separate project?

I mean yeah, in this case you need to specify that it's a painting. That's literally what they explain in the last sentence if your screenshot 😅

Why would I spend 3 seconds implementing the suggestion when I can just go to HN and complain about it?

That's one of the main official WAI recommendations, though. It's not controversial. It's the correct use of that feature. There are very few cases where you need to specify that it's a photo, and that's when you make a conscious decision to disable the warning because you know what you're doing

+page.svelte also runs on the server during SSR!

I'm with you on this. I have been muting AI-hype posts for a couple of months and it feels good

If this is what gets people to start writing semantic HTML, I don't hate it...
"Make sure to also add alt text to images so that the AI can read it!" :D

`start` is used to start up the built app. This is especially important in vite because the dev and prod bundles are quite different. I know most people probably never use `start`, but there were cases where it was useful to me to preview what the output will be without deploying it

Saw the output on my phone and was impressed by your webgl skills. Then checked the source and realised it's not even webgl. For some reason made me excited and it feels even more impressive 😆

Maybe instead of "new" it can be "v2". But if you will move it back to the root later I don't think it really matters

@emeline.dev !

I think not scrolling is way better UX. Cause there's no way you're reading it at the same speed it's coming through

what is stopping you from doing this in +layout.svelte of the parent directory of the sections?

It has a pretty cool (imo) way, and it's mentioned in the docs in "Loading data" svelte.dev/docs/kit/loa...
but if you've only done the tutorial you'll probably miss it.

I like it because it doesn't block the entire page, just the part that you want to show this data. But I get it's not so obvious

You just do a little `page.url.pathname.split('/').filter(Boolean)` and get an array of the paths 😄

Depends on what you want to do. Webflow is as close as you'll get to simple HML, CSS, and JS. If you don't care too much about having control over every little thing and just want something fast, Framer is probably the way

Ah I see. In this case what is the issue with just using Astro + Svelte? I don't know if it's a good idea for Sveltekit to try to fit into every use case when there is a highly optimized solution already

Loading data • Docs • Svelte Loading data • Svelte documentation

Are you looking for something like this?
svelte.dev/docs/kit/loa...

This will render and return the available data in the html, but any promises will be streamed down later when they're available

Not available yet in v4 unfortunately (according to docs)

It works if you do it with an array and ternaries! I use it a lot:

class={[
"text-sm other-classes",
isActive ? "text-blue" : "text-black"
]}

Why do you need it to exist if you're not using it?

Generate svelte UI with AI | svelte0 Generate beautiful Svelte 5 UI using Tailwind CSS and AI from a simple text prompt

There's an unofficial one
svelte0.com
But I don't use either of these tools so I can't compare

It may make sense to somehow ask explicitly for permission, in the app or otherwise. Personally I hate when companies put me in their newsletter just because I signed up to the product

Google's new "game-changing" model 2.0 Flash

Ohh that's nice! Thanks!

Maybe I'm missing something here, but don't hooks.server.ts achieve this?

One important thing if you're going to turn the entire article into a button: Give the button an aria-label that is a CTA. Otherwise it's very likely that screen readers will read the entire article as button text. At least that's how it works with anchor tags

You can, but only if it's muted and you allow webflow to ruin the quality 😄
You will also likely reach your bandwidth limit fast.
I just throw the video on an s3 bucket, or something like uploadthing, or Dropbox if it's easier for the client, and embed it using a custom video element