
@Chr_Bach Lucky guess.

@Chr_Bach Yeah, we prefer you to have the place to yourself for those times you like to crank up your Best of Enya album and strut around barefoot. ⛵️👣

Phil Hawksworth
@philhawksworth •
RT @Netlify: Did you know that @Netlify can automatically optimise your site during each deployment?
Use our Post Processing service to:…
Use our Post Processing service to:…

@jimniels @Netlify I also like the idea of redirecting those requests somewhere scary looking like https://www.cisa.gov/securing-federal-networks
...and like to daydream about the dry mouth somebody might get if they take a quick look at logs of their bot's progress.
...and like to daydream about the dry mouth somebody might get if they take a quick look at logs of their bot's progress.



@samjulien @aaronfrost @esosanderelias @Tzmanics @jorgeucano @auth0 @Netlify @ScullyIO Great to see @Tzmanics caught in mid "Aaaand another thing..."

Phil Hawksworth
@philhawksworth •
RT @philhawksworth: @Netlify @osideeq @neoziro @gatsbyjs A nice thing about these templates is that with a button click you can:
- clone t…
- clone t…

@Netlify @osideeq @neoziro @gatsbyjs A nice thing about these templates is that with a button click you can:
- clone the template repo
- deploy your new site on @Netlify
- get a ready-made CI/CD workflow
- enjoy free hosting with https from @letsencrypt
📖 Thanks, DeployToNetlify button!
https://docs.netlify.com/site-deploys/create-deploys/?utm_source=twitter&utm_medium=jamtemplates-dtn-pnh&utm_campaign=devex#deploy-to-netlify-button
- clone the template repo
- deploy your new site on @Netlify
- get a ready-made CI/CD workflow
- enjoy free hosting with https from @letsencrypt
📖 Thanks, DeployToNetlify button!
https://docs.netlify.com/site-deploys/create-deploys/?utm_source=twitter&utm_medium=jamtemplates-dtn-pnh&utm_campaign=devex#deploy-to-netlify-button

Phil Hawksworth
@philhawksworth •
RT @WIRED: Welcome to the upside-down. Or, rather, just what a photographer can do with a drone, 3-D rendering, and Photoshop. Here's how:…

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