@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.
@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.
@bruised_blood I recommend that you RUN (don't walk) to see Isle of Dogs by Wes Anderson. Every single frame belongs in a gallery. Utterly stunning. (And lots of good dogs!)
RT @coldfrontconf: ICYMI be sure to check out this post by our organizer @auchenberg about all things new for #ColdFront18 ❄️
The landscap…
The landscap…
@StuCoxMedia @ianfeather BuzzFeed have *millions* of pages, and millions of visitors. Inlining the js would mean that it can't be cached as a common resource and would inflate the weight of every single page request. It would also probably damage the performance too.
Progressive Enhancement is the way.
Progressive Enhancement is the way.
@gerrybot @nandortoth @GoHugoIO @github @Netlify @awscloud Lambda can be used to extend what you can do with a static site. When you need something to run server-side like a secret you can't have client-side, it can be handy. @Netlify makes it simple for you by letting you manage lambda functions as part of your codebase.