• hawksworx
  • blog
  • speaking
  • about
  • search

Notes - page 452

  • 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 • December 21st 2017 replying to this from @mrmrs_
@mrmrs_ Oh no!

So sorry to hear that. What a lovely looking, and happy moggie. No shortage of love.

x
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 21st 2017 replying to this from @chriscoyier
@chriscoyier Love that response.

I often suspect that people expect CSS to be easy, and when it requires some effort, they get frustrated.

That's not the same as it being bad.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 21st 2017 replying to this from @pixelastic
@pixelastic @DirtyF @Netlify #shipit
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 21st 2017 replying to this from @budparr
@budparr @robmuh @marcusnielsen @eggheadio @_oliverjam @gatsbyjs @Netlify @github @surge_sh @awscloud This is great! Reminds me very much of the drum I was banging around the same time!

https://speakerdeck.com/philhawksworth/dynamic-static-site-strategies
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 21st 2017 replying to this from @
@DirtyF @Netlify @pixelastic Ha ha ha. Love this!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 21st 2017 replying to this from @rwxrob
@robmuh @marcusnielsen @eggheadio @_oliverjam @gatsbyjs @Netlify @github @surge_sh @awscloud Excellent!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 21st 2017
After 10 years of reading @24ways, I'm rather happy to have now written for them.

On deployment:

1. Make it scripted
2. Make it automated
3. Make it real
4. Make it first

https://twitter.com/24ways/status/943632412302565376
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 21st 2017
RT @24ways: Day 21: Knowing the Future - Tips for a Happy Launch Day by Phil Hawksworth @philhawksworth https://buff.ly/2oVDf6g
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 20th 2017 replying to this from @HenrikJoreteg
@HenrikJoreteg @Netlify Hmm. That's odd. The team will be keen to figure out what was going on there! Glad to hear that your deployed site was not effected. If you were to share the site name/url you were working on, we could investigate a little more (perhaps DM it to me, or chat with support whenever)
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 20th 2017 replying to this from @
@m1sp Ah that's likely. I believe though that if the assets don't change, subsequent deploys should be fast as atomic changes are pushed rather than repeatedly pushing identical assets.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 20th 2017 replying to this from @HenrikJoreteg
@HenrikJoreteg @Netlify Hey Henrik! Long time no see!

I'm not aware of any issues on platform at the moment. Have builds been succeding ok previously? Builds that include scripts which run and run should eventually time out. (15mins I think)

The support team will have better visibility which may help
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 20th 2017 replying to this from @rwxrob
@robmuh @marcusnielsen @eggheadio @_oliverjam @gatsbyjs @Netlify @github @surge_sh @awscloud That's a nice benefit of a #JAMstack site... you can host it most anywhere. I like avoid getting locked in due to technology choices.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 20th 2017 replying to this from @jensimmons
@jensimmons @jamiemchale I recently moved my site to @GoHugoIO on @Netlify, so now my iterations are speedy, but it's time for me to add a little CMS fun.

1. Starting 28th Dec
2. Add @NetlifyCMS to my @GoHugoIO site
3. Deadline for a realtime and customised CMS editor experience: 5th Jan

#newwwyear
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 20th 2017 replying to this from @
@m1sp Cool!
How big is big?

I'm curious about good strategies for using SSGs for sites with many hundreds of thousands of pages.

Netlify deploys are atomic and only files which change get pushed to the CDNs, so building should be a bigger overhead than deploying.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 20th 2017
Trying to make domain management a little easier. Netlify's improved DNS admin. https://twitter.com/Netlify/status/943178985969631232
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 19th 2017 replying to this from @
@erquhart @bdougieYO He was probably fact-checking @ry_boflavin.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 19th 2017 replying to this from @benpbarnett
@benpbarnett Ha ha. Brilliant.
As it happens, I was in the room to enjoy the whiskey and take that photo.

It's just all the fun that has happened since then that I have to dial in for.
*sob sob*
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 19th 2017 replying to this from @paulrobertlloyd
@paulrobertlloyd Ugh.
How? Why?
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 19th 2017 replying to this from @patrickhamann
@patrickhamann @Shopify That's an excellent list. One or two I've not seen... but will eagerly watch.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 19th 2017 replying to this from @a_alfredo
@a_alfredo @jaffathecake Are there cars to beat up in that too?
– The Qashqai of Sauron?
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 19th 2017 replying to this from @BenjaminEHowe
@BenjaminEHowe @Netlify We're not actually limited to AWS regions. Our build infrastructure is distributed over many cloud providers (for resilience) and the output published to CDN nodes all around the world (also not limited to a single provider).

Is there a region you are particularly targeting?
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 19th 2017
And then, just before lunch at Netlify, there was an impromptu whisk(e)y tasting. http://ift.tt/2klg1lk
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 18th 2017
Nice walkthrough from @DavidWells on how @goserverless use @Phenomic_app (a React SSG ) and @Netlify for their site. https://serverless.com/blog/how-built-static-serverless-website-netlify/

#jamstack #serverless
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 18th 2017
Rather enjoying the simple png rotations via css - which yield this result from @oneplus
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • December 18th 2017 replying to this from @philhawksworth
@DavidDarnes #typotastic
  • 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.