@devdevcharlie The temptation to create an edit of this where the game is replaced by "my side of this video call" with well-timed statements which provoke your reactions of delight or disappointment is strong.
But that would make me a monster.

Phil Hawksworth
@philhawksworth •
Forgive me for a moment, but I don't care how smug this sounds...
I *really cannot wait* until the @Netlify all-hands off-site later this month. It's a gathering of so many people whom I adore and admire.
And spending a little time in California in January does not suck either.
I *really cannot wait* until the @Netlify all-hands off-site later this month. It's a gathering of so many people whom I adore and admire.
And spending a little time in California in January does not suck either.

@slightlylate Finally.
This is the twitter thread I came here for in the first place.
This is the twitter thread I came here for in the first place.

@szechuan @RobbieRinder A grateful nation sends its thanks.

Phil Hawksworth
@philhawksworth •

Phil Hawksworth
@philhawksworth •
I think this is spot on. Great advice here. https://twitter.com/davatron5000/status/1214246184908460032

@TrentWalton @paravelinc This is delightful!

@Paul_Kinlan @andreban You must be a pleasure to be around.

Phil Hawksworth
@philhawksworth •
Woohoo!
I hearty welcome, Laurie! 🤗 https://twitter.com/seldo/status/1214224764501254144
I hearty welcome, Laurie! 🤗 https://twitter.com/seldo/status/1214224764501254144

Phil Hawksworth
@philhawksworth •
January seems like a good time to share our thoughts and experiments using #JAMstack.
@shortdiv has been blogging **every day this year** about it.
Now, I've added some #jamuary thoughts of my own.
https://dev.to/philhawksworth/prerendering-is-the-key-to-a-tasty-jamstack-22pp
@shortdiv has been blogging **every day this year** about it.
Now, I've added some #jamuary thoughts of my own.
https://dev.to/philhawksworth/prerendering-is-the-key-to-a-tasty-jamstack-22pp


@TejasKumar_ @EmmaBostian @Netlify I'd actually recommend http://community.netlify.com as a first port of call for help like this. There are lots of helpful people there beyond the @Netlify support folks.


@lesliecdubs Yikes! That sounds nasty. Here’s to a speedy recovery.
And I hope you’re ok by the time you need to travel. I’m excited to see you later this month.
And I hope you’re ok by the time you need to travel. I’m excited to see you later this month.

@ddprrt Hang on a mo... I'll get my popcorn.

Phil Hawksworth
@philhawksworth •
Fascinated by the site setup for http://tsconf.eu.
I'd make popcorn and snuggle into a comfy armchair to read a detailed blog post about this if @ddprrt wrote it. https://twitter.com/ddprrt/status/1213062666371174402
I'd make popcorn and snuggle into a comfy armchair to read a detailed blog post about this if @ddprrt wrote it. https://twitter.com/ddprrt/status/1213062666371174402

Phil Hawksworth
@philhawksworth •
RT @devkimchi: Ever wanted to convert your existing @WordPress blog to static site like @gridsome?
@justinchronicle wrote a blog post how…
@justinchronicle wrote a blog post how…

@irreverentmike @Netlify Oh good point! Thanks for that feedback. I’ll share it with our docs team.

@irreverentmike @Netlify Aha. I see the confusion. Environment variables aren’t always necessarily secrets. They might just be contextual or made available from an environment. For instance there are a bunch of variables that Netlify exposes from the build enviroment for convenience.

@irreverentmike @Netlify Exactly. Secrets should never go into source control.

Phil Hawksworth
@philhawksworth •
I made a thing.
I made it look like a book.
It's not a book.
It's my template for making sites with @tailwindcss, PurgeCSS, UglifyJS, and @eleven_ty.
You can try it in a couple of clicks.
https://www.hawksworx.com/blog/eleventail-a-helper-for-tailwindcss-and-eleventy/
I made it look like a book.
It's not a book.
It's my template for making sites with @tailwindcss, PurgeCSS, UglifyJS, and @eleven_ty.
You can try it in a couple of clicks.
https://www.hawksworx.com/blog/eleventail-a-helper-for-tailwindcss-and-eleventy/

@irreverentmike @Netlify Try setting a different NODE_ENV value for different deploy contexts (stage | prod etc) and then programmatically accessing different env vars as a result.
if (process.env.NODE_ENV=="production") {
const secretThing = process.env.myProdSecret;
}
if (process.env.NODE_ENV=="production") {
const secretThing = process.env.myProdSecret;
}

@irreverentmike @Netlify There are a combination of things at your disposal which should get you what you need:
- Env Vars (https://docs.netlify.com/configure-builds/environment-variables/#netlify-configuration-variables)
- Deploy Contexts (https://docs.netlify.com/site-deploys/overview/#deploy-contexts)
- DotEnv (https://www.npmjs.com/package/dotenv)
- Env Vars (https://docs.netlify.com/configure-builds/environment-variables/#netlify-configuration-variables)
- Deploy Contexts (https://docs.netlify.com/site-deploys/overview/#deploy-contexts)
- DotEnv (https://www.npmjs.com/package/dotenv)

Phil Hawksworth
@philhawksworth •
OOoooh. I'll be eagerly following along as @shortdiv writes more and more about #JAMstack this #JAMuary! https://twitter.com/shortdiv/status/1212455186150699008