"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.
On continue notre client en @sveltejs aujourd'hui dans le cadre du projet @ApiPlatform ! ✨
D'ailleurs, on aura également @soyuka qui viendra pendant le stream nous parler un peu de API Platofrm justement ! 🧠 Donc si vous avez des questions, venez !
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.