
Phil Hawksworth
@philhawksworth •
As time expired the team stood proudly around the scarecrow they had hurriedly assembled, despite all being aware that its stuffing was starting to fall out and it would probably slump into a pile of rags and nonsense by the morning.

@kapehe_ok @sanity_io This is next level swaggery!

Phil Hawksworth
@philhawksworth •
RT @AgilityCMS: We are super excited to announce our next workshop!
With Ekene @kenny_io from @Netlify and talk about the latest and greate…
With Ekene @kenny_io from @Netlify and talk about the latest and greate…

@dfosco @peduarte @JoshWComeau Hard to argue with that logic 🤓
And yet I also tend to adopt the conventions @JoshWComeau showed.
And yet I also tend to adopt the conventions @JoshWComeau showed.

@peduarte @JoshWComeau This is my new favourite Pedro tweet

@peduarte @JoshWComeau Alphabetical? You monster!
That's like when I once tried having my CDs organised by the colour of their spines.
That's like when I once tried having my CDs organised by the colour of their spines.

@smakinson @Netlify Yeah this looks really very good! I'm pretty excited to see @FredKSchott tell @jlengstorf all about it today on @LWJShow

Phil Hawksworth
@philhawksworth •
RT @FredKSchott: Until those are written though, I'll try to touch on some (all?) of these topics during this livestream with @jlengstorf t…

@DavidDarnes This was an odd choice of desktop wallpaper, but ok.

@heydonworks This is a tough way for his brother to find out

@FredKSchott Flabbergasted at how well this project aligns with so many of my own technical tastes. And finding great guidance on CSS strategies described in the docs.
Very much looking forward to playing with Astro to learn more.
Very much looking forward to playing with Astro to learn more.

@almost_logical @Netlify You're too kind! ❤️

Phil Hawksworth
@philhawksworth •
🤦
1. Write detailed bug report in a @GitHub issue
2. Use "Preview" to check your markdown formatting
3. Click a link in the preview mode and whoosh over to another page
4. Quickly hit the back button hoping all your work wasn't lost in the GitHub issue
5. Scream into the abyss
1. Write detailed bug report in a @GitHub issue
2. Use "Preview" to check your markdown formatting
3. Click a link in the preview mode and whoosh over to another page
4. Quickly hit the back button hoping all your work wasn't lost in the GitHub issue
5. Scream into the abyss