@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.
@AaronGustafson @calum_ryan @GoHugo ooh!
A pattern I often use for sites built with an SSG is to have my build (gulp, or grunt, whatever):
1. Get data from APIs and stash it locally where the SSG wants it.
2. Run the SSG to generate the site and use the data in my templates.
If npm, then universal SSG support?
A pattern I often use for sites built with an SSG is to have my build (gulp, or grunt, whatever):
1. Get data from APIs and stash it locally where the SSG wants it.
2. Run the SSG to generate the site and use the data in my templates.
If npm, then universal SSG support?
@calum_ryan @AaronGustafson Happy to join the IndieWeb slack if invited. Also curious about the latest in webmentions for SSGs. Do you have an example of that I can noodle around with @AaronGustafson?
@citizen428 @middlemanapp @Netlify Delighted to hear that!
(HTTPS was working fine, but if you also force SSL, that should be instant, I think)
(HTTPS was working fine, but if you also force SSL, that should be instant, I think)
@ashishwadekar @citizen428 @middlemanapp @Netlify Hosting "static" sites from a CDN has different cost implications to keeping a server (virtual or otherwise) up, so it can be cost effective at this scale. The more involved features introduce costs when usage mounts, and other pro features/support-levels cost $
@vincpa @dav_is_dev @ianfeather The conversation from this talk "Building Resilient Frontend Systems" was about what happens if a request for JS made by a document that the browser has *already downloaded* fails. if it was critical for content display, the user is impacted.
Put content in HTML. Then enhance.
Put content in HTML. Then enhance.
@calum_ryan I hope that went well. I'd love to hear about how the discussion went.
@dav_is_dev @vincpa @ianfeather They certainly have. But there is more in play than that. That was the point of sharing this data with us. When clients connect from via mobile data plans, or on trains, or slow wifi, or under powered devices, we get to see how fragile js can be. Sadly this stat is not unique.