Gareth Poole

I'm a front-end developer based in middle earth

[boris @boristane]

cloudflare workflows are truly goated

[Hono @honojs]

Hono v4.13.0 is out now!

* Performance improvement up to 1.25x
* HTTP QUERY method support
* Method Not Allowed middleware, and more

Enjoy!
https://t.co/sJnjxRgwDK

[Evan You @evanyou]

Cloudflare docs just got so much cleaner!

https://t.co/7LWaZCMtif

[brandon @burcs]

new cloudflare docs site just shipped and it's beautiful

built using nimbus (a new documentation framework built entirely on top of astro)

[James Ross @CherryJimbo]

Cloudflare is working on Drop, making deploying a temporary static site quick and easy, without authentication.

You can upload a folder/zip, preview it for one hour, then claim it to keep the deployment.

[Gareth Poole @garethpoole]

@astrodotbuild

[Theo - t3.gg @theo]

Cat's out of the bag. Cloudflare is ~3x faster for many workloads due to a series of fixes they've shipped in the last 5 days

https://t.co/SnLpLzMUnX

[Adam Wathan @adamwathan]

New Cloudflare Workers site is beautiful! ✨ Awesome work by @tjcages.

Built with Tailwind CSS v4 💅🏻

[Cloudflare @Cloudflare]

Today, Cloudflare is proud to announce support for two cornerstone frameworks in the modern web ecosystem: we’re partnering with Webflow to sponsor Astro, and with Netlify to sponsor TanStack. https://t.co/OWTQWK4kMU #BirthdayWeek

[Matthew Prince 🌥 @eastdakota]

Just getting started.

[Gareth Poole @garethpoole]

@ackriv @jdevalk @Cloudflare Any news on this? 😃

[Jessie Frazelle @jessfraz]

My contrarian opinion is that @zeddotdev is going to come out on top of these vscode fork wars when people realize what they really want is a first principles new solution, NOT vscode

[Adam Wathan @adamwathan]

Tailwind CSS v4.0 stable will be out next week 🤝🏻

[Gareth Poole @garethpoole]

@Cloudflare Purge by tag for non-enterprise when?

[Cory House @housecor]

My preferred development workflow for 2024:

1. All devs have their own DB instance so we don’t conflict with each other. The DBs run locally, and can be reset via static SQL scripts via a single command. The SQL scripts are committed to source control. This way, we can code without internet, demo the app reliably, reproduce bugs, and write fast, reliable tests.

2. Create a short-lived feature branch for each ticket. Each pushed commit runs tests on CI. CI auto-deploys a dedicated ephemeral (short-lived) environment with a unique URL for each feature branch so people can test and approve *before* merge. Thus, no separate shared environments like UAT or staging are typically required.

3. When a PR is approved, we merge to main. The CI server auto-deploys the main branch to prod. If the feature isn’t ready for public use, hide it in prod via a feature flag.

[Adam Wathan @adamwathan]

One billion 🚀

[Gareth Poole @garethpoole]

@datocms @astrodotbuild Love it!

[DatoCMS @datocms]

We've got a shiny new website 🪩

TLDR: We rebuilt our site from Next.js to @astrodotbuild for a many reasons like:

- Bringing in TS and gql.tada;
- Dogfooding juicy new Dato features;
- It was fun. Really fun.

Here's one of many posts on our journey 👇

https://t.co/TPi1PmZy2N

[Astro @astrodotbuild]

elegance. luxury. astro.
5.0 coming soon...

[Adam Wathan @adamwathan]

✨ Just published Tailwind CSS v4.0-beta.1!

⚡ Up to 5x faster builds, 100x faster rebuilds
🧰 Built-in imports, vendor prefixing, and more
🪄 Simplified, CSS-first configuration
🦾 Modern CSS features like @​starting-style and container queries
🎨 New wide-gamut color palette