@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?
@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.
@jlengstorf @Netlify Aha! This is kind of what I was alluding to earlier, but more explicit. Thanks for letting me know how you got it squared away. Most helpful.
I'll loop back to our docs team to see if we can help people who may encounter this in future.
I'll loop back to our docs team to see if we can help people who may encounter this in future.
@jlengstorf @Netlify ... so my instinct is that it's a little code funny that I can't spot right now. Have you explored this reference? I cloned it and got it working immediately. Perhaps there might be a good tip in there somewhere.
https://github.com/imorente/gatsby-netlify-form-example
https://github.com/imorente/gatsby-netlify-form-example
@jlengstorf @Netlify Thanks Jason. I'm not quite in a situation where I can easily debug this right this moment, but I can ask a couple of people who know Gatsby better than I (who might have a pointer or two) when they come online. Certainly all is currently well with Netlify's form handling...
@jlengstorf @Netlify Ha! Never fear!
I'm a Gatsby duffer... will this page view be pre-rendered too, or only available when rendered vis js? I ask because Netlify will need to spot a valid form in the HTML generated in order to generate a corresponding form API to post to.
https://github.com/imorente/gatsby-netlify-form-example
I'm a Gatsby duffer... will this page view be pre-rendered too, or only available when rendered vis js? I ask because Netlify will need to spot a valid form in the HTML generated in order to generate a corresponding form API to post to.
https://github.com/imorente/gatsby-netlify-form-example
@jlengstorf @Netlify Sorry to eavesdrop... but forms are working ok for me. Wondering... is this a new form or was it working previously?
Also, are you submitting it with JavaScript or just letting the browser do what comes naturally?
Also, are you submitting it with JavaScript or just letting the browser do what comes naturally?
@jaffathecake @rem I'm ok with that level of overlording, but the fact that your birthday appears multiple times due to the multiple shared calendars in my view, well that will simply not translate into multiple gifts for you.
Or indeed any. If I'm honest.
Instead here's an early birthday kiss: x
Or indeed any. If I'm honest.
Instead here's an early birthday kiss: x
@sebastienlorber @erquhart @jamstatic_fr @Netlify @kylemathews The tough thing is in building just the chosen pages or sections instead of the entire site. There are techniques for sharding your site into more manageable chunks so that you don't need to regenerate millions of pages for each build, but it certainly does get challenging.