I had the immense pleasure of sitting down with the LogRocket folks for another far-ranging discussion. This one touched on #ProgressiveEnhancement, #PWAs, #AI, and #accessibility

https://podrocket.logrocket.com/progressive-enhancement-pwa-ai-accessibility

@Riduidel The fact that it respects the base <a href /> and <form action /> tags to stick to the #ProgressiveEnhancement philosophy (« app remains usable even if I’m not here ») is already a big win over #htmx, for me. So far that’s been one of the main drawbacks and a key reason I chose Hotwire / Turbo.

#Frontend #PubQuiz:

Who remembers the significance of #WindowsXP service patch 3 in terms of failing #JS #featureDetection in #InternetExplorer 6?

#webdev #IE6 #PE #ProgressiveEnhancement #theGoodOldDays

Read-only web apps: https://adactio.com/journal/20113
You wouldn’t expect Gmail to provide Core features without JavaScript, but, you should be able to read your emails, view docs for Gdocs, etc. By @adactio
#ProgressiveEnhancement

I'm guiding the development of a web site/app design system in my 'day job'. Of course, I'm baking progressive enhancement in. When I explained what that meant to a (very experienced) colleague he said "surely those problems are all edge cases?"

He's not wrong, but handling edge cases is a lot of what developers do. Checking for nulls, out of bounds conditions, data mismatches etc.

Anyway, this deserves a blog post. Watch this space.

#ProgressiveEnhancement #WebDevelopment #programming

Just wrapped my talk “Adapting to Reality” (which is about #ProgressiveEnhancement) for @ppk’s students at @HvA

Slides: https://presentations.aaron-gustafson.com/PtnfEQ

OK, I felt like this deserved a blog post: https://blog.ltgt.net/naming-things-is-hard-spa-edition/

#SPA #MPA #CSR #SSR #ProgressiveEnhancement

I'm looking for my next opportunity as a web developer! I’m traditionally front-end-focused, but would love to work with @django and/or @getkirby. I've been doing web development for close to 20 years now.

Needs to be remote. Needs to be with folks who value #accessibility and ideally with folks who value #ProgressiveEnhancement and do their best to eschew lots of client-side #JavaScript.

Please boost!

(Thanks to @oluoluolu for the inspiration to make a post like this!)

#GetFediHired #jobs

Added some animated spinners to the few places in the app that use JavaScript to load some content without doing a complete page refresh (with #ProgressiveEnhancement). On the off chance that the data doesn't load basically immediately, that should feel a bit more responsive than seeing no change and wondering if your click/tap registered.

@tbroyer we used to call them "server side includes"

#progressiveenhancement #ssr #csr #mpa #spa

I don't know how to call "assembling parts of HTML into a full page" at edge or service-worker; it's not really "rendering" to me, so not ESR/SWSR.

From the above, this mean you can have:
• SPA+SSR: Turbolinks
• SPA+CSR: most React/Vue/Angular apps
• SPA+SSR+CSR: NextJS et al.
• MPA+SSR: most "web sites"
• MPA+SSR+PE (progressive enhancement)
• MPA+CSR: silly but I've seen it (HTML page is empty, possibly with data as JSON to be rendered client-side)

#SPA #MPA #CSR #SSR #ProgressiveEnhancement

This is good: When JavaScript Fails
https://medium.com/@jason.godesky/when-javascript-fails-52eef47e90db
#frontend #JavaScript #progressiveEnhancement

RT @jenstrickland
Here we go! We all need to reflect on #progressiveEnhancement and how it provides a better UX, accessibility, and more.

If you’re at #CSUNATC23, come to Save Our World, with progressive enhancement & accessibility to learn how it goes even beyond UX & #a11y! Friday at 4:20pm. https://twitter.com/aarongustafson/status/1635710384903450624

@thibaultamartin

Actually, now that I look at your current version of Matrix.org redesign, it looks like a good starting point for #ProgressiveEnhancement, because it has reduced motion.

Slap that `prefers-reduced-motion: no-preference` media query and experiment with animations for those who don't mind some motion (majority of users). 😉

Interesting overview of options for #ProgressiveEnhancement and #WebComponents in #ServerRendered websites.
https://www.jayfreestone.com/writing/web-component-libraries/

All I hear when you talk about your island architecture:
https://m.youtube.com/watch?v=Ny8aOB9iP3A

#javascript #islands #progressiveenhancement #web

@smitten Only @enhance_dev flavored components can SSR, but you can of course do any #progressiveEnhancement you want to do after the page loads.

Assuming a site that works with plain HTML/CSS, what are the current ways of cutting the mustard these days to ensure that if JavaScript runs, it'll run OK?

Even if transpiling to support a certain set of browsers, there's no guarantee the browser that loads the page will match the baseline set when bundling.

Bonus point if it also prevents other scripts from breaking if the syntax cannot be parsed 😃

#FrontEnd #ProgressiveEnhancement #JavaScript

@sphinxc0re If you want to adhere to the principals of #ProgressiveEnhancement, yeah, everything should be functional without #JavaScript. The way I do it is to just build the base functionality before adding any JavaScript enhancement.

Question for the #ProgressiveEnhancement crowd: I'm building an application using #SvelteKit. Should all parts of my application work without #JavaScript by default? If not, how do I determine which parts are okay to require JavaScript for?