@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
This is a handy way to build and deploy your #JAMstack site on @Netlify directly from a Google Sheet where you manage some of your content. https://twitter.com/jmolivas/status/1112978392180113409
@rem @jaffathecake I totally agree.
Developer convenience has trumped other considerations. Which is something to be wary of. I'm using @eleven_ty to do this as it brings support for using @LeaVerou's @prismjs which I already really love.
https://github.com/11ty/eleventy-plugin-syntaxhighlight
Developer convenience has trumped other considerations. Which is something to be wary of. I'm using @eleven_ty to do this as it brings support for using @LeaVerou's @prismjs which I already really love.
https://github.com/11ty/eleventy-plugin-syntaxhighlight
@rem @jaffathecake Interesting though, that the result of your poll leans so much towards doing this client-side. I'm assuming ( 👈 danger!) that's because it feels simpler and easier for developers to do it that way.
@swyx @Benghamine *whispers*: It's my "I'm whispering something to you because you are special" pose.
@rem I do it server side at build time.
Because anything I can do ahead of time, I do ahead of time.
It doesn't add markup for me as it is done by my SSG (@eleven_ty) during the build.
One less thing to have as a client-side js dependency and on the render path.
Because anything I can do ahead of time, I do ahead of time.
It doesn't add markup for me as it is done by my SSG (@eleven_ty) during the build.
One less thing to have as a client-side js dependency and on the render path.
@MichaelWDelaney @NetlifySupport Yeah, I'd rather like this too.
We'll track it internally here. It might be possible. I'd certainly use it.
We'll track it internally here. It might be possible. I'd certainly use it.
@MichaelWDelaney @NetlifySupport Sadly, Deploy to Netlify buttons can't work with private repos due to the way the repo needs to be cloned on your behalf.
I bumped into this myself recently.
I bumped into this myself recently.
@Kajrietberg You can add environment variables via your Netlify Admin (look in your deploy settings). And you can use dotenv to safely set env vars locally too.
https://www.npmjs.com/package/dotenv
Remember to .gitignore your local .env file.
https://www.npmjs.com/package/dotenv
Remember to .gitignore your local .env file.
Unbelievably good value! https://twitter.com/csswizardry/status/1112690957743505408