If there was an #HTML element that changes it's content when users interact with other elements on the page, what name would it have?
PLEASE NOTE: I am not suggesting that this element needs to exist; I am only asking what it would be called. I'm building a CustomElement, I just want it to have a name that makes sense.
Vote and suggest others in replies. Please boost for reach!
This is a bit of a long shot, but if there are any #Svelte developers out there interested in mapping who would be willing to spend a bit of time helping a novice (me) out in some experiments to improve UX in web apps for sustainable transport planning, please get in touch. #GeoSpatial#DataScience
It's where I experiment with all things web, like #html#css#javascript esp. #svelte and #svg most often in the context of #dataviz or similar forms of visual storytelling.
Every time I try to use component scoped styles in #Svelte I wimp out on it and go global instead. Anyone have good examples of (somewhat) complex apps (like a small ui library even) that make good use of component scoped styling I can take a peak at?
I tend to get lost at the "but what about the bits I want to share" part.
The light from the #stars travels for years (and years) until it reaches your eyes. This #interactive#map of the night sky shows you for each star what happened on Earth when the light started traveling from the star to you. That way, any star has a story to tell you. You can zoom in, move around and hover all the stars to reveal the historical events they are connected to.
Working on my PHP side project, feeling an intense pull to migrate it to SvelteKit. But I know this is the biggest trap every coder with a side project can relate to - working on architectural changes instead of features. On the other hand, I love #SvelteKit and can make this thing way better with Svelte & SvelteKit than I ever will be able to with PHP. #Svelte + #PHP might be the way, except I lose the server-side rendering. Send help pls. :blob_dizzy_face:
I’ve spent the last few months crafting my own home on the Web, and I wanted to make sure it presented me as a human, not defined solely by my work as a #DesignEngineer / #WebDev.
This has also been a great opportunity to finally use #Svelte & #SvelteKit in a project. I love how easy it was to learn and how intuitive it is, as someone who started with vanilla HTML and CSS
Migrating from CodeIgniter #PHP to #SvelteKit is so easy and pleasant.
By building the site 15 years ago, and modernizing it today, I skipped over the awkward middle stage of making an API & fetching data to render it in the browser.
SvelteKit's form actions let you build a fast site that even works without #JavaScript, which means I'm going from server-side rendering with links & forms, to server-side rendering with links & forms. Except now I have the power of #Svelte to make it way nicer!
Spent some time upgrading emoji-picker-element to #Svelte v4. The most painful part was dealing with Jest and ES Modules (classic problem; I really just need to switch away from Jest). Everything else about the upgrade was pretty smooth.
I also tried upgrading to Svelte v5. It works, but sadly the bundle size has increased ~20%, with no runtime perf benefit I can see, so I'm wondering if it makes more sense to just convert to a vanilla web component instead. https://github.com/nolanlawson/emoji-picker-element/pull/376
I think it's time to update my portfolio site after 5 years of neglect.. going to use #svelte / #sveltekit as a bit of a learning exercise. Any recommendations for a simple clean customisable "portfolio" starter template/repo? I'd also like to add an experiments/sketches section too. Thx!
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
Yo #developers, #dev bubble, i need your thoughts. If got an older #Vue Project that needs some refactoring. Should i try to fix it, or rebuild the whole thing in #Svelte? I mean, it will be a ton of work, but it sounds like a lot of fun 🤔
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.
2023-09-04: Organise, Research & Document - Weekly Guild Report for Sprint #2 (discuss.coding.social)
2023-09-04: Organise, Research & Document...