@keirwhitaker @kieranmasterton @Shopify First a treat for my earholes.
Now my eyeholes too?!
Hooray!

Phil Hawksworth
@philhawksworth •
Perfect podcast listening for your commute or, if I may be so bold, to enjoy during a deep candle-lit bath. https://twitter.com/Jack_Franklin/status/1219186488514138113

Phil Hawksworth
@philhawksworth •
This talk by @seldo is brilliant! https://twitter.com/Netlify/status/1218292005920485376

Phil Hawksworth
@philhawksworth •
Worth the price of admission! https://twitter.com/smashingconf/status/1219179209769095169

@smashingmag @shortdiv It still boggles my mind that @shortdiv has been able to write an interesting post about #JAMstack *every single day* this year as she lead the charge into #jamuary!
https://dev.to/t/jamuary
https://dev.to/t/jamuary

Phil Hawksworth
@philhawksworth •
This speaks volumes about the heft of Nike's brand identity,
...but above all else, it's just cool. Want. https://twitter.com/yourmobilegeek/status/1218982471364034560
...but above all else, it's just cool. Want. https://twitter.com/yourmobilegeek/status/1218982471364034560

@stefanjudis @swyx @Netlify @zeithq That said, for the logic you are describing, the URL nerd in me would tend to prefer defining that in the path rather than putting it in a qs.
(I don't have all the context of what you're making, of course.)
(I don't have all the context of what you're making, of course.)

@stefanjudis @swyx @Netlify @zeithq I don't totally agree.
With a traditional backend, you'd not accept all and any arbitrary parameters or values. You'd have some validation and fallback rules in your logic. A GET should return a representation of content. You're just defining what you can GET at build time.
With a traditional backend, you'd not accept all and any arbitrary parameters or values. You'd have some validation and fallback rules in your logic. A GET should return a representation of content. You're just defining what you can GET at build time.

@stefanjudis @swyx @Netlify @zeithq 🥳 Perhaps a confusion about the limitations. It can't be completely dynamic and just accept any parameters. You need to tell it what params too look for and then you can scoop out the values of them if you need.

@stefanjudis @Netlify @zeithq You need to tell @Netlify's redirect API what query parameters to expect, but should it give you what you are asking for.
Docs here: https://docs.netlify.com/routing/redirects/redirect-options/#query-parameters
Docs here: https://docs.netlify.com/routing/redirects/redirect-options/#query-parameters

Phil Hawksworth
@philhawksworth •
👏 This comment wins today:
"What kind of tennis score is eleventy-love?" https://twitter.com/philhawksworth/status/1218865174171570176
"What kind of tennis score is eleventy-love?" https://twitter.com/philhawksworth/status/1218865174171570176

Phil Hawksworth
@philhawksworth •
The JS world sometimes feels like it is getting more complex & intimidating, but there are still examples of it powering sites in ways that feel approachable.
That's one of the reasons I enjoy @eleven_ty. As @chriscoyier says, "It's Just JavaScript™"
https://css-tricks.com/eleventy-love/
That's one of the reasons I enjoy @eleven_ty. As @chriscoyier says, "It's Just JavaScript™"
https://css-tricks.com/eleventy-love/

@Kosai106 @eunjae_lee GENIUS!

@hankchizljaw @zachleat @nhoizey @davatron5000 @chriscoyier This is what I do too.
You can see an example in my little @eleven_ty / @tailwindcss starter.
https://github.com/philhawksworth/eleventail/blob/master/.eleventy.js#L34-L37
You can see an example in my little @eleven_ty / @tailwindcss starter.
https://github.com/philhawksworth/eleventail/blob/master/.eleventy.js#L34-L37

@jaffathecake That’s appalling.
I want it.
I want it.

@moo9000 @Netlify Not exactly. But a couple things that might be of interest...
We offer simple post-processing to optimise your build output. This includes some image optimisation.
Our Large Media service wraps GitLM and provide edge image transforms 👉 https://docs.netlify.com/large-media/overview/?utm_source=twitter&utm_medium=nlm-pnh&utm_campaign=devex
We offer simple post-processing to optimise your build output. This includes some image optimisation.
Our Large Media service wraps GitLM and provide edge image transforms 👉 https://docs.netlify.com/large-media/overview/?utm_source=twitter&utm_medium=nlm-pnh&utm_campaign=devex

Phil Hawksworth
@philhawksworth •
RT @Netlify: Could it be? The benefits of a statically generated site without a complicated change to your @WordPress site setup?? it Could…


Phil Hawksworth
@philhawksworth •
RT @Netlify: Did you hear? We're running a webinar!
Join us for the first installment on building a kickass JAMstack site on a timeline w…
Join us for the first installment on building a kickass JAMstack site on a timeline w…

@dkruythoff touche

@dkruythoff Bless you for thinking about solutions!
Between you and me, and quality punning aside... I don't think that the url http://petlify.netlify.com scans as nicely or is as descriptive as http://petsof.netlify.com.
Also... it has now been claimed 😏
(But I'll never share this defence)
Between you and me, and quality punning aside... I don't think that the url http://petlify.netlify.com scans as nicely or is as descriptive as http://petsof.netlify.com.
Also... it has now been claimed 😏
(But I'll never share this defence)

@fabiovenni These were right out of the freezer.
Boiled. Then pan fried in some butter.
I regret nothing!
Boiled. Then pan fried in some butter.
I regret nothing!