"This means that the design of the framework is largely settled, with no anticipated breaking changes between now and the stable release, and that the most egregious bugs have been stomped.
"It doesn't mean that it's ready for production, or that nothing will change between now and 5.0. But if you've held off on dabbling with Svelte 5 during the public beta phase, now is a great time to try it out."
I'm following the ARIA authoring practices from the W3 for web components I'm writing for a #Svelte app.
I've been experimenting with lots of companies' web sites and component libraries.
It's disappointing how much variation there is in support (even from big companies). Many have wrongly applied anti-patterns and have failed to cover even 25% of the documented patterns.
A lot of component libraries do the minimum and still claim #a11y. 🤬 Trust these after verification.
𝗗𝘂 𝗕𝗼𝗶𝘀 𝗗𝗮𝘁𝗮 𝗩𝗶𝘀𝘂𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗦𝗼𝗰𝗶𝗲𝘁𝘆 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 - 𝗪𝗲𝗲𝗸 𝟵/𝟭𝟬. My re-creation of Du Bois' poster no. 51 implemented with D3 & Svelte. Once more close to the original and responsive.
Du Bois Data Visualization Society Challenge - Week 7/10: My recreation of Du Bois' poster no.47, done with D3 & Svelte. Again I tried to recreate it as close to the original as possible, make it responsive and added a pattern fill to match the hand-painted look.
Du Bois Data Visualization Society Challenge - Week 6/10: My recreation of Du Bois' poster no. 54, done with D3, Svelte. Again I tried to recreate it as close to the original as possible and make it responsive.
Du Bois Data Visualization Society Challenge - Week 5/10: My recreation of Du Bois' poster no. 13, done with D3, Svelte. Added a pattern fill to match the hand-painted look & transitions on load.
Discussed my current painpoints with #Twig a bit in Craft Discord. Coming from a #Svelte Components perspective, the Developer Experience is just not as good currently. Things take much more effort to set up, you need to understand Includes vs. Embeds vs. Macros. This is a general PHP CMS challenge of course. 🤷 On the other hand: You get SSR easily without wild cloud setups in PHP 😉 🤓 #craftcms
I broke a little with #SvelteKit idioms here insofar as I have Pages merely pass a context object into a #Svelte component.
This in turn allows me to utilise #Storybook to describe the interface in different configurations (I have tests in place as well).
It's still early days but we tackle one page at a time to build up this #Federated#Forge (F2 for short).
In case you are interested in translating, hit me up. Be warned that things might move around or get dropped. I prefer early feedback to easily correct course if needed.
Working on Svelte is so rewarding as a long time vanilla JS developer. All the accumulated web knowledge over the years just instantly available to you, while enjoying the augmented DX.
I have to say that's the best thing happened to the web. Imagine you don't need to throw away everything in order to progress, instead just enjoy the compounding benefits of your existing web knowledge.
I’m starting to fall in love with #svelte@sveltejs I finally have a change to work with Svelte within real production codebase and it's nothing but a pleasure. For a newbie with long React background this feels like - «OMG, it actually could be just that simple!»
It's still early days, and I'm only scratching the surface but so far it feels really good.
Ah, yes that works. I was just wondering if the distance between the 4 lines (or ticks) is slightly uneven? But maybe that's just my brain being misled by the different widths of the black chart element...
Matthias Stahl started a beginner friendly video series, where he goes through nice little mini-projects and explains how to make responsive #dataviz with the perfect combo of svelte and d3 :)
Part of the reason for updating was taking advantage of the new read helper in SvelteKit 2.4. I wrote a quick blog post yesterday on how that simplifies things: https://geoffrich.net/posts/sveltekit-read/
New blog post: #SvelteKit 2.4 added a new read method that simplifies reading assets on the server. I did a quick writeup on how it simplifies retrieving raw font data in one of my old #Svelte social image demos.
I asked a frontend friend what framework he would recommend if he was starting a new project today. He said #svelte, so I spent the afternoon walking through their online tutorial and playing around with #sveltekit.
I've got to say, as someone with fairly rudimentary JS skills, it was a great experience. It feels a lot closer to HTML/CSS and a lot simpler than a lot of the other JS frameworks.
hello happy (belated) new year! I've been wanting to learn #svelte for a while and figured today is as good a day as any and I'm already so delighting in their tutorial it's so good 😊
🎉 New blog post! For a few months now I've been toying with an idea for a new #Svelte framework for #datavisualization -- heavily inspired by the great Observable Plot. Very curious to hear what you think about this.
Got reason to look into svelte-check, the #linting tool for #Svelte projects, and I must say – their approach is intriguing.
It’s essentially invoking Language Service (#lsp) diagnostics for all the files and using the diagnostics output from the TypeScript, HTML and CSS language services to determine if there's an error or not.
In other words: Mimicking how eg. VSCode does to report errors and warnings in its UI.
This is a very interesting approach compared to eg. @eslint parsers
