@dav_is_dev @ChrisFerdinandi @vincpa @ianfeather True. Do those things. They help. The difference is that *if* your site depends on JavaScript to be functional, or to convey and render the content, then *if* that fails to load/parse, the user is left at sea.
Progressively enhancing from content in HTML can defend against this.
Progressively enhancing from content in HTML can defend against this.
Speaking of #teacherappreciationweek, huge love and respect to @yorksworths, my big brother who works tirelessly to teach and inspire. Be that in the classroom or at a music festival, he's a wonderful example and I want to be more like him when I grow up.
Thoughtful, patient, ferociously smart, and very, very thorough. @VeryThorough is the driving force behind the great documentation at @Netlify from which I learn so much. https://twitter.com/gdisf/status/994647009448644608
This from @tkadlec, is not helping my #deltavconf FOMO.
https://noti.st/tkadlec/OOXqpJ/redefining-web-performance
https://noti.st/tkadlec/OOXqpJ/redefining-web-performance
Hey @AskAtlassian! Any movement on this at all? I'm feeling bad about how many people I recommend to move from @Atlassian over to @github or @gitlab due to this issue from 2012 being stuck with no apparent movement despite such regular requests for it.
https://bitbucket.org/site/master/issues/5814/refify-pull-requests-by-making-them-a-ref
https://bitbucket.org/site/master/issues/5814/refify-pull-requests-by-making-them-a-ref
@notwaldorf @_developit @mathias WUT?
@mathias doing karaoke? That image doesn't fit in my brain.
(Although I'm sure you owned the room, @mathias!)
@mathias doing karaoke? That image doesn't fit in my brain.
(Although I'm sure you owned the room, @mathias!)
@dav_is_dev @vincpa @ianfeather Imagine if the navigation did NOT depend on JavaScript, but when/if the JavaScript loaded the navigation just got a little snazzier.
@simonw @beyond_code @jaggeree Perhaps not quite what you're looking for, but when you build microservices with Lambda via @Netlify Functions, they are atomic, immutable and their versioning and deployment is automatically linked to the rest of your site's versioning. Rollbacks, branch builds... all in sync
@schmarty @nhoizey @AaronGustafson @calum_ryan @GoHugo @jekyllrb Looks good. But I guess that means hosting some PHP on a server somewhere and hitting that resource at build time if you want to pull the content into a static site. Right?
@raymondcamden @AaronGustafson @calum_ryan @GoHugo @Real_CSS_Tricks Come to think if it, I also describe this and link to my gulp tasks in this post about showing recent tweets on my site, with a build triggered by @IFTTT monitoring my twitter.
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
@raymondcamden @AaronGustafson @calum_ryan @GoHugo It's one of the steps I use in an comments system I write about recently on @Real_CSS_Tricks
https://css-tricks.com/jamstack-comments/#article-header-id-3
But I use this step all over the place on projects, so I bet I could write-up / make a more focussed reference example.
https://css-tricks.com/jamstack-comments/#article-header-id-3
But I use this step all over the place on projects, so I bet I could write-up / make a more focussed reference example.