• hawksworx
  • blog
  • speaking
  • about
  • search

Notes - page 108

  • Newest
  • Previous
  • Next
  • Oldest

The archive of what I posted on Twitter, which I now self host due to a lack of trust in Twitter and some other reasons.

I'll soon begin refelcting all my Mastodon posts here too. I'm happier self-hosting or maintaining an archive of my content on URLs that I can own.

There are tools to help you do this too. Such as this one from the makers of Eleventy.

A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 20th 2021 replying to this from @sarah_edo
@sarah_edo Turn this battle into an HBO series that we can all enjoy watching from the comfort of our living rooms?
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 20th 2021 replying to this from @0xKlaudiusz
@kdembler_ @Netlify @NetlifySupport This is helpful feedback.

Also makes me wonder if socialising the permalink to the specific deploy in the PR in additional to the main deploy preview URL might be useful in general.

I'll pass it all along.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 20th 2021 replying to this from @martinbean
@martinbean @Netlify Ooh sorry if you received many emails. This will be related to the new collaborative deploy previews feature.

Info on the feature:
https://www.netlify.com/products/deploy-previews/

More info here on those permissions:
https://answers.netlify.com/t/netlify-github-app-permission-updates-with-collaborative-deploy-previews/37872
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 20th 2021 replying to this from @0xKlaudiusz
@kdembler_ @Netlify @NetlifySupport This is not currently configurable (although I'll pass along the feedback, so thanks!).

However this is only added to the preview deploys so you can always see every deploy without it by visiting the permalink for any deploy (or any branch deploy URL)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021 replying to this from @Bradamante
@Bradamante @Netlify @NetlifySupport Oh!
That is very unexpected and suggests some other issue. I think that the support team will want to help out. They might ask for details.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021 replying to this from @Bradamante
@Bradamante @Netlify @NetlifySupport Extra builds?

This should not have resulted in any extra builds. It should add the UI for commenting only to the preview deploys which you create as a result of making a pull request on you site's repo.

Are you seeing something different?
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021 replying to this from @johnson_brad
@johnson_brad @featurepeek @Netlify SHOUT IT FROM THE ROOFTOPS!
So thrilled to be working with you, Brad!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021 replying to this from @_developit
@_developit @biilmann That's an interesting idea.
I expect that this would play into the discussions around making this as discoverable as we can with the least friction possible. But I'll happily feed the suggestion back to the team.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021 replying to this from @isaaczara_
@isaaczara_ @Netlify @biilmann Thanks!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021 replying to this from @_developit
@_developit @biilmann Branch deploys should have you covered for that. You can watch and build unlimited branches which don't get this feature and the branch deploy URL always track the head of that branch.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021 replying to this from @eduardoboucas
@eduardoboucas @DavidDarnes @Netlify I think I know

https://twitter.com/Netlify/status/1394968854997213186
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 19th 2021
I was already excited before I even saw this shocking pun and the bonus photo of @jlengstorf.

Why would you NOT join?

http://ntl.fyi/product-reveal https://twitter.com/Netlify/status/1394968854997213186
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 18th 2021 replying to this from @DavidDarnes
@DavidDarnes @futuregerald It starts getting awkward at around the 3 minute mark.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 16th 2021 replying to this from @zachleat
@zachleat White Screen of Death.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 16th 2021 replying to this from @dizzyd
@dizzyd @sarah_edo You’re both very much in my thoughts.
Love and strength to you. ❤️
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 16th 2021 replying to this from @kmelve
@kmelve Hadn’t realised how close I am to doing this each time.

Adopting it as my new default.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @bdougieYO
@bdougieYO Class
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @Robb0wen
@Robb0wen I see you taking my picture.
Don't you dare put that shit on twi...
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @ianand
@ianand @Netlify Yeah.

And the more widely available the support, the better for everyone.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @ianand
@ianand Oh good. I'm glad that came across. The tricky line to walk is in making this potential advancement both compelling yet faithful, while also keeping it suitable for wider adoption and avoiding a tight coupling to either vendor or framework.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @webstandards
@webstandards 🙂

That's the right form. With more info on our pro account support for open source projects here:

https://www.netlify.com/legal/open-source-policy/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @philhawksworth
@ianand This is also the intent behind the DPR RFC.

By describing in detail the model/flow it would enable, the hope is that any vendor/ssg could strive to support it. The more the merrier. And it optionally expands, rather than undermines the core attributes of Jamstack
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @ianand
@ianand A valuable point. I think as the category matures, capabilities will/should get added if they are in keeping. Ideally in a non-proprietary way.

Edge-based redirects is an example. Many vendors support this feature which extends the original core simplicity of Jamstack
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @DavidDarnes
@DavidDarnes @zachleat (chairman of the)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • May 14th 2021 replying to this from @zachleat
@zachleat I think the Queen keeps an eye on Twitter for the #NeedsAKnighthood hashtag
  • Permalink
  • |
  • Twitter
  • Newest
  • Previous
  • Next
  • Oldest

The source code of this site is available on GitHub and is hosted and updated by Netlify automatically after each code commit

Other than where specified, the content on this site is published under a Creative Commons Attribution 3.0 licence.

Subscribe to a feed of blog posts on this site.