On my way to The Big Apple for @jamstackconf which offers up some fruit-based puns for sure. So it's better that @futuregerald will MC-ing this. He has more restraint than me.
Very excited to talk to the lively #JAMstack community.
@gerwitz Ha! Yeah.... it builds once a minute. The build and deploy takes approximately 25-30 seconds to complete, so I set the time 30 seconds into the future.
I’m a dirty cheat.
* http://setyourwatchby.netlify.com should not be used for timing Olympic track and field events.
I’m a dirty cheat.
* http://setyourwatchby.netlify.com should not be used for timing Olympic track and field events.
"we are now paying the price for a referendum that was dominated by falsehoods"
Very good stuff from Betty Boothroyd https://twitter.com/Banbury4Europe/status/1114063310163468288
Very good stuff from Betty Boothroyd https://twitter.com/Banbury4Europe/status/1114063310163468288
@zachleat @eleven_ty @opencollect My greatest contribution to open source, ever:
https://twitter.com/philhawksworth/status/999068891870527488
https://twitter.com/philhawksworth/status/999068891870527488
I use @eleven_ty a lot both personally & professionally, getting great value from it.
@zachleat builds & maintains it for free. So supporting him by contributing the equivalent of the pint of beer I'd want to give him each month, was an easy decision.
https://opencollective.com/11ty
@zachleat builds & maintains it for free. So supporting him by contributing the equivalent of the pint of beer I'd want to give him each month, was an easy decision.
https://opencollective.com/11ty
@garethr Heh!
Depending on how many of these files change with each build, subsequent deployments should speed up. (Since behind the scenes only modified assets are propagated to the CDN).
Of course, your site generation speed will be more in the hands of whatever you are doing there.
Depending on how many of these files change with each build, subsequent deployments should speed up. (Since behind the scenes only modified assets are propagated to the CDN).
Of course, your site generation speed will be more in the hands of whatever you are doing there.
@brad_frost 10 PRINT "Phil is cool"
(Followed by...)
20 GOTO 10
...on every BBC Micro I could find on display in the shop.
(Followed by...)
20 GOTO 10
...on every BBC Micro I could find on display in the shop.
@HenriHelvetica @Netlify @jllord Nice! That talk by @jllord is excellent. And this technique is handy. I've used it in a number of places.
@Kajrietberg or... could that call and page population happen at build time when you generate the page, instead of in the browser? That would mean that you'd not hit API rate limits if *gazillions* of people requested your page (since you'd only get the data at build time, not request time)
@Kajrietberg Instead you might want to proxy that JS call via an API in a serverless function. Netlify Functions can help you with that by adding your API key (they have env var access) and proxying to that opendata endpoint.
@Kajrietberg Careful. It looks like you are conflating what you are trying to do at build time, and what you want to run in the client. Env vars are only available to the server.
If you need that JS to run client-side, you'd not want to populate it with your API secret. It would be exposed.
If you need that JS to run client-side, you'd not want to populate it with your API secret. It would be exposed.
@raymondcamden @Netlify 🎉
Names for things are hard. And the cognitive baggage that comes with the word "static" is a big part of why another term is useful.
I'm less worried about the word we use, and more excited by the potential in...
- JAMstack
- Static
- StaticFirst
- Pre-rendered
- ShortStack
Names for things are hard. And the cognitive baggage that comes with the word "static" is a big part of why another term is useful.
I'm less worried about the word we use, and more excited by the potential in...
- JAMstack
- Static
- StaticFirst
- Pre-rendered
- ShortStack