@Marcus_Noble_ @Netlify @benotist @eleven_ty Headless CMS often allow you to call a web hook automatically when content changes. Which can trigger a build and ingestion. For services that we don’t I often use @IFTTT or @zapier.
As an example:
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
(My SSG has changed, but the mechanics are the same)
As an example:
https://www.hawksworx.com/blog/keeping-a-jamstack-site-feeling-fresh-with-recent-tweets/
(My SSG has changed, but the mechanics are the same)
@Marcus_Noble_ @Netlify @benotist This is how I pull content from elsewhere into my little @eleven_ty scaffold which I often use as a project starting point
https://github.com/philhawksworth/eleventyone/tree/master/src/site/_data/prod
https://github.com/philhawksworth/eleventyone/tree/master/src/site/_data/prod
@Marcus_Noble_ @Netlify Ah. I was referring to services external to @Netlify. And using that terms as a catch all for many things.
Many tools found at http://headlesscms.org output structured content over feeds this way, and I use feeds from Twitter, Instagram and @benotist in the same way.
Many tools found at http://headlesscms.org output structured content over feeds this way, and I use feeds from Twitter, Instagram and @benotist in the same way.
@martynhoyer @UXOxford It's not officially announced yet. But if you are interested, I'd save the date!
Thanks to all at #ogn49 for listening to me enthuse about #jamstack. You can get my slides to see at a more leisurely pace.
👓 http://Findthat.at/ognjam
👓 http://Findthat.at/ognjam
Looking forward to Oxford Geek Night tonight.
By 'eck, it's been a while!
http://oxford.geeknights.net/ogn49
By 'eck, it's been a while!
http://oxford.geeknights.net/ogn49
@kevinwolfcr @jamesqquick @Netlify Netlify Functions currently support JavaScript or Go.
And async functions are supported.
Here's a growing list of examples and resources:
https://functions.netlify.com/
And async functions are supported.
Here's a growing list of examples and resources:
https://functions.netlify.com/
@twwilliams @Netlify No need to remove that. It will just give you an added layer of filtering and do no harm.
https://www.netlify.com/docs/form-handling/#spam-filtering
https://www.netlify.com/docs/form-handling/#spam-filtering
Delighted to see this feature ship!
Yay @netlify team! ❤️🌈🔥🍾 https://twitter.com/Netlify/status/1095395213881888768
Yay @netlify team! ❤️🌈🔥🍾 https://twitter.com/Netlify/status/1095395213881888768
The wonderful @Dr_Black on @BBCRadio4 right now. Talking about her path to the world of computing. Always relatable and inspirational.
@imandyie @scotch_io @_ooade @Netlify @Cloudflare You could indeed. The enabler here is the integrated CI for automated, frictionless, and high-confidence deploys. And the automatic cache invalidation across a global CDN that you need never need care about managing yourself. (Which is what @Netlify brings).
@jesslynnrose - @FronteersConf and @fronteers
- @coldfrontconf
- @fronttrends
- @ffconf
All lovely and very well worth a look.
- @coldfrontconf
- @fronttrends
- @ffconf
All lovely and very well worth a look.
@RowdyRabouw Hmm... That looks right to me. About to get on a plane so not in a good place to experiment and troubleshoot.
Although, where in your target url are you using :version?
Although, where in your target url are you using :version?
I love the pull request template we use at Netlify. But I'm a sucker for a picture of a cute animal. https://twitter.com/calavera/status/1093536140823474177