@oliverturner @Netlify Integrated data persistence is a little more involved and I've not dabbled yet.
@oliverturner @Netlify You don't need to mess with the API Gateway, that is sorted for you. Each function will be reachable on a URL determined by it's file name under /.netlify/functions (the admin app will show you each function's endpoint)
The docs talk about that here:
https://functions-beta--www.netlify.com/docs/lambda-functions/#building-lambda-functions
The docs talk about that here:
https://functions-beta--www.netlify.com/docs/lambda-functions/#building-lambda-functions
@ChrisFerdinandi @FrontEndLondon What if you could manage the content directly AND through a CMS without one sanding on the toes of the other?
What might that look like?
Ooooooh.
What might that look like?
Ooooooh.
@ChrisFerdinandi @FrontEndLondon :)
And yet that is seen as one of the barriers to adopting #jamstack. How do we help content authors work without getting them into the code?
This is an attempt to address this.
And yet that is seen as one of the barriers to adopting #jamstack. How do we help content authors work without getting them into the code?
This is an attempt to address this.
@lynchy010 @FrontEndLondon I'll certainly share slides. Not certain about video.
Love using a CMS? Liar! Next week I'll be presenting this talk at @FrontEndLondon:
"Stealthy git - solving CMS woes with git, on the quiet"
More info at http://www.frontendlondon.co.uk/
See you there on Thursday evening?
"Stealthy git - solving CMS woes with git, on the quiet"
More info at http://www.frontendlondon.co.uk/
See you there on Thursday evening?
@chriscoyier The thought of tracking scripts not available over https gives me the heebie-jeebies.
Seems like more and more of us are keen to avoid the need to manage a server (except for the lulz).
This ecosystem is getting richer.
https://github.com/anaibol/awesome-serverless
#jamstack
This ecosystem is getting richer.
https://github.com/anaibol/awesome-serverless
#jamstack