• hawksworx
  • blog
  • speaking
  • about
  • search

Notes - page 1381

  • 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 • February 19th 2018
Very excited to be returning to Copenhagen for @coldfrontconf again later this year. Its quality talks, friendly atmosphere, and great organisation have made it a firm favourite for me.

And there is a call for recommendations now open. Who do you want to see give a talk? https://twitter.com/coldfrontconf/status/963322097979109376
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 19th 2018 replying to this from @jamchiller
@jamchiller @Netlify Nice.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2018 replying to this from @gedaly
@Gedaly @Netlify Yes indeed! Once the redirects are deployed they should be very fast as they happen at the CDN. Not sure what a sensible max number of entries might be though.

I made a simple example which generates your redirects automatically:

https://github.com/philhawksworth/linkylinky
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2018
RT @thenewdynamic: 🔥 “Build Better Faster Websites: the New Dynamic 02/17 links and showcase” http://newsletter.thenewdynamic.org/archive/96681 with @philhawksworth…
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 17th 2018 replying to this from @
@m1sp @Kikobeats @Netlify And @ddprrt wrote a great article on how you can use Wordpress as a back-end and get content from its API into a #JAMstack build.

https://fettblog.eu/wordpress-and-jamstack-sites/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @philhawksworth
@bdougieYO @Netlify @github or good luck.
Whatever. Too upset to sepllcheck.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @bdougieYO
@bdougieYO @Netlify I can't believe that day is already here. Legend!
I hope @github know how lucky they are. Good look BeeeDougie!
Embedded image from social media
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @philhawksworth
@JordanHawker @Netlify Depending on how your site is built, this might be the information you're looking for:

https://www.netlify.com/docs/redirects/#history-pushstate-and-single-page-apps
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @AxleHellfire
@JordanHawker @Netlify Ack! I'm an idiot. I didn't spot that Intercom is for those on the paid plan. Best direct support contact without that is https://www.netlify.com/support/. Sorry for adding confusion there!

Meanwhile I'm afraid I don't quite understand the expected and actual behaviors you get
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @AxleHellfire
@JordanHawker @Netlify Hi Jordan. Would you mind asking this to support via the little intercom chat thing-a-mi-bob in https://app.netlify.com? That way the team can see your build/settings and diagnose things far more easily.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @chrisbiscardi
@chrisbiscardi @Netlify 👍
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @toddhalfpenny
@toddhalfpenny 1.5p
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @chrisbiscardi
@chrisbiscardi @Netlify Folders in your site will form the path on your site (so, yes... if I'm understanding your second example correctly).

You can also have different branches in your repo drive different subdomains domains.

Docs for that here: https://www.netlify.com/docs/custom-domains/#branch-subdomains
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 16th 2018 replying to this from @KevinGoldsmith
@KevinGoldsmith @trek That is 100% true for me too!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @brad_frost
@brad_frost Wonderful! Congratulations to you both! Beautiful.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @FrontEndLondon
@FrontEndLondon @lynchy010 \o/
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018
Live demo time!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @oliverturner
@oliverturner @Netlify Not at all! Happy to help!
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @philhawksworth
@oliverturner @Netlify Integrated data persistence is a little more involved and I've not dabbled yet.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @oliverturner
@oliverturner @Netlify You don't need to mess with the API Gateway, that is sorted for you. Each function will be reachable on a URL determined by it's file name under /.netlify/functions (the admin app will show you each function's endpoint)

The docs talk about that here:

https://functions-beta--www.netlify.com/docs/lambda-functions/#building-lambda-functions
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @ChrisFerdinandi
@ChrisFerdinandi @FrontEndLondon @Netlify That's the ambition.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @philhawksworth
@ChrisFerdinandi @FrontEndLondon What if you could manage the content directly AND through a CMS without one sanding on the toes of the other?

What might that look like?
Ooooooh.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @ChrisFerdinandi
@ChrisFerdinandi @FrontEndLondon :)

And yet that is seen as one of the barriers to adopting #jamstack. How do we help content authors work without getting them into the code?

This is an attempt to address this.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018 replying to this from @lynchy010
@lynchy010 @FrontEndLondon I'll certainly share slides. Not certain about video.
  • Permalink
  • |
  • Twitter
A photo of Phil Hawksworth's face
Phil Hawksworth @philhawksworth • February 15th 2018
Love using a CMS? Liar! Next week I'll be presenting this talk at @FrontEndLondon:

"Stealthy git - solving CMS woes with git, on the quiet"

More info at http://www.frontendlondon.co.uk/

See you there on Thursday evening?
  • 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.