Would pay cold hard cash to be in this meeting with these rather brilliant Netlifriends.
(I'd sit quietly and keep out of trouble) https://twitter.com/rafahari/status/1172178927483281408
@scottjehl @sarah_edo @Netlify @filamentgroup Branch builds, preview builds, and instant rollbacks are a heady combination. Time-travel powers++
Another great article from @jeromecoupe! This time describing a very logical approach to multi-language sites with #JAMstack.
This method of generating the site with @eleven_ty is a perfect fit for @netlify's lang/geo detection and redirects.
https://www.netlify.com/docs/redirects/#geoip-and-language-based-redirects https://twitter.com/jeromecoupe/status/1172131960438886400
This method of generating the site with @eleven_ty is a perfect fit for @netlify's lang/geo detection and redirects.
https://www.netlify.com/docs/redirects/#geoip-and-language-based-redirects https://twitter.com/jeromecoupe/status/1172131960438886400
Goodness me yes!
Having gotten used to having this capability over the last few years, I simply can't imagine being without it.
👇👇👇👇👇 https://twitter.com/sarah_edo/status/1172149941516390401
Having gotten used to having this capability over the last few years, I simply can't imagine being without it.
👇👇👇👇👇 https://twitter.com/sarah_edo/status/1172149941516390401
RT @sarah_edo: I love that @Netlify makes deploying easy, but here are some things that take it to the next level for me:
* lock a particu…
* lock a particu…
@Netlify That pro-tip post and video:
https://dev.to/philhawksworth/netlify-pro-tip-using-split-testing-to-power-private-beta-releases-a7l
https://dev.to/philhawksworth/netlify-pro-tip-using-split-testing-to-power-private-beta-releases-a7l
@svillegastweets @tachyons_css @tailwindcss @simonswiss @DotAllConf @adamwathan I know just what you mean!
I found the argument about semantics in html vs css quite compelling. And the thoughts on sustaining maintainable CSS over time (even on my personal projects) struck a chord.
Trying to be willing to explore and learn. Despite my entrenched opinions.
I found the argument about semantics in html vs css quite compelling. And the thoughts on sustaining maintainable CSS over time (even on my personal projects) struck a chord.
Trying to be willing to explore and learn. Despite my entrenched opinions.
@simonswiss @tachyons_css @tailwindcss @DotAllConf It was SO well put together. Lots of inspiration for me about both the content and the delivery.
@simonswiss 🙂 I’m going to have to experiment. I’ve considered exploring these before but was a little cautious. Your arguments landed well for me.
Looking at utility-first CSS tooling such as @tachyons_css and @tailwindcss with fresh eyes and piqued interest after watching this brilliantly constructed talk by @simonswiss from last year's @DotAllConf.
https://dotall.com/sessions/a-real-life-journey-into-the-opinionated-world-of-utility-first-css
https://dotall.com/sessions/a-real-life-journey-into-the-opinionated-world-of-utility-first-css
Did you know that you could use @Netlify's split testing feature to create a way for users to opt in to the private betas of your upcoming site releases?
Here is a short video and detailed tutorial showing how.
https://dev.to/philhawksworth/netlify-pro-tip-using-split-testing-to-power-private-beta-releases-a7l
Here is a short video and detailed tutorial showing how.
https://dev.to/philhawksworth/netlify-pro-tip-using-split-testing-to-power-private-beta-releases-a7l
@markboulton @rem @Netlify Oooft!
Being able to identify 404s is one of the things I feel is really useful in server-side analytics like @Netlify Analytics.
#ServerFreeServerSideAnalyticsForTheWin!
#BuzzwordBingo
Being able to identify 404s is one of the things I feel is really useful in server-side analytics like @Netlify Analytics.
#ServerFreeServerSideAnalyticsForTheWin!
#BuzzwordBingo
@markboulton @rem @Netlify Routing common 404s to appropriate pages is lovely with the Redirects API.
If there is still a very high volume of 404 traffic, you could cheekily use Google to save bandwidth and recover some traffic:
[[redirects]]
from = "/*"
to = "https://www.google.co.uk/search?q=site:http://yoursite.com&q=:splat"
status = 404
If there is still a very high volume of 404 traffic, you could cheekily use Google to save bandwidth and recover some traffic:
[[redirects]]
from = "/*"
to = "https://www.google.co.uk/search?q=site:http://yoursite.com&q=:splat"
status = 404
@rem @markboulton @Netlify This is excellent @Rem!
And you are spot on. @Netlify Analytics show you what file serving activities (including 404s) are happening from the CDN. So they are currently better suited to this sort of investigation than for tracking client-side user activities and events.
And you are spot on. @Netlify Analytics show you what file serving activities (including 404s) are happening from the CDN. So they are currently better suited to this sort of investigation than for tracking client-side user activities and events.
@markboulton @DavidDarnes @Netlify It does sound like a lot... but I guess you are getting lots of traffic :)
@markboulton @DavidDarnes @Netlify Assuming 10k page views per day, that's an average of 270kb per page view (if my maths is correct). Which doesn't sound outrageous if you have some images in each page.
@markboulton @aexmo @Netlify Are there lots of either un-cacheable (perhaps externally sourced and somehow deemed unique) or unoptimised (I imagine not from you, sir!) assets as part of each deploy?
@markboulton @Netlify It’s harder to diagnose when Cloudfront is infront of the Netlify CDN. Without it we can handle the logic of the caching of assets seamlessly, but with it, there are additionally layers of caching logic in front of us which we no longer control. Perf is typically better without.
@daveredfern @markboulton @Netlify They do indeed work retroactively. When you enable them, they will backfill with the previous 30 days of data.
@markboulton @Netlify Wowzer! Assuming that you don't have analytics turned on to spot any anomalies, it might be worth asking in http://community.netlify.com about that. Perhaps someone there can help diagnose any issues.