@adokce @thekitze @zeithq @Netlify Since the context itself is an env var, I often use one build script for all contexts and have conditionals. Like this:
if(process.env.CONTEXT == 'production') {
secret = http://process.env.PROD_KEY;
} else {
secret = http://process.env.DEV_KEY;
}
https://docs.netlify.com/configure-builds/environment-variables/?utm_source=twitter&utm_medium=support-pnh&utm_campaign=devex#build-metadata
@thekitze @zeithq @Netlify Contextual builds on @Netlify can help with this. You can run different builds and so pull different env vars according to context:
- production
- branch-deploy
- deploy-preview
Or according to specific branch names.
To the docs! 👉 https://docs.netlify.com/site-deploys/overview/?utm_source=twitter&utm_medium=support-pnh&utm_campaign=devex#deploy-contexts
- production
- branch-deploy
- deploy-preview
Or according to specific branch names.
To the docs! 👉 https://docs.netlify.com/site-deploys/overview/?utm_source=twitter&utm_medium=support-pnh&utm_campaign=devex#deploy-contexts
@chrisbiscardi @adactio I think this gets more complicated than JS on or off. I've had "just html" go unresponsive on some devices after it was rendered because my device was blocked while it unpacked, parsed and executed a big JS bundle.
Less so on my >$1000 phone and 4G or with JS disabled.
Less so on my >$1000 phone and 4G or with JS disabled.
@chrisbiscardi @adactio Yeah. I think it depends on how we use the frameworks not just what the frameworks give us.
Deciding on the baseline from which we'll enhance is key, and depends so much on what experience and capabilities we are building.
Deciding on the baseline from which we'll enhance is key, and depends so much on what experience and capabilities we are building.
RT @eduardoboucas: 📢 If you’re using a headless CMS to feed data into a static site, I’d love to know how you do it.
- Plugins made for y…
- Plugins made for y…
@richhiggins @adactio And I prefer not to think of the baseline/fallback as being something akin to "SEO" markup. But as delivering the baseline of capabilities to all users. That was leads to the widest possible support for people, devices, and conditions by default. (+ that valuable SEO juice too)
@richhiggins @adactio I've found that providing a fallback shows the best of intentions, but becomes difficult to execute well, and often falls by the wayside over time. Where as planning an approach which enhances from a sensible baseline (the "it depends" moment for each project) was more successful
This from @adactio captures my own perspective perfectly.
To me, Progressive Enhancement feels as fundamental as spellchecking our content, and I don’t see why we’d discard it.
But misunderstandings about what PE means seem to be on the increase.
https://adactio.com/journal/16404
To me, Progressive Enhancement feels as fundamental as spellchecking our content, and I don’t see why we’d discard it.
But misunderstandings about what PE means seem to be on the increase.
https://adactio.com/journal/16404
📣 London calling (for your jamstack proposals) https://twitter.com/Netlify/status/1225481803424829440
RT @jamstackconf: Calling all JAMstack community! The JAMstack Conf Call for Papers for London is now open!
📣http://bit.ly/londonCFP 📣
W…
📣http://bit.ly/londonCFP 📣
W…
@nhoizey @zachleat @Netlify @eleven_ty @chriscoyier Exactly right.
@Netlify caches all the dependencies declaired in package.json between builds to speed things up. Only reinstalling when package.json changes.
npx doesn’t stash things locally either on your machine or in @Netlify.
To speed builds up - install and run via npm
@Netlify caches all the dependencies declaired in package.json between builds to speed things up. Only reinstalling when package.json changes.
npx doesn’t stash things locally either on your machine or in @Netlify.
To speed builds up - install and run via npm
RT @Netlify: More from @sarah_edo about generating a site from WordPress content APIs here in this detailed walkthrough.
👉 Headless WordPr…
👉 Headless WordPr…
RT @MrAhmadAwais: 🔥 For every retweet, I'll donate USD 149 http://VSCode.pro masterclass to students!
Instead of wasting 💰 on market…
Instead of wasting 💰 on market…
@AshlynnPolini @Netlify SO excited that you're part of the team!
@jamstackconf is going to go from strength to strength!
@jamstackconf is going to go from strength to strength!