🦋david.click retweeted
EmDash 1.5 is here, with collaborative editing.
Your team can now write together in real time. Revisions keep every version you save, new sites stay out of search until launch, and moving from WordPress is smoother.
Here's what's new 🧵

ALT EmDash 1.5 release card. The EmDash logo with "1.5" and "Write together, in real time." sit in a white glow, ringed by rows of grey text lines with a few in collaborators' colors, name flags for Noah, Matt and Maya at line ends, and Ana's cursor just after the tagline. The corners read "New release, November 13, 2026" and "34 community contributors".
🦋david.click retweeted
you can mess around with 'em here ↓
jhey.dev/prototypes/2026/seg…
🦋david.click retweeted
Animated img carousel 🤙
Use CSS trig functions to get radius and layout images as a cylinder 🤓
Use scroll animation to rotate the cylinder 📜
:root {
--a: calc((360 / var(--total)) * 1deg);
--r: calc((var(--item-width) / sin(var(--a))) * -1);
}
Explained 👇
Replying to @jh3yy
@jh3yy Demo request! This image strip, but in pure CSS:
codepen.io/trusktr/pen/Pogrr…
🦋david.click retweeted
Lenis v2 is in development.
We're looking for sponsors to help fund the next chapters. In return: visibility on the Lenis website (25K+ monthly visitors) and GitHub readme (15k+ monthly visitors).
If you sell templates, tools, or services to developers and designers who care about scroll craft — this is a huge opportunity to get in front of that audience.
🦋david.click retweeted
Pica is a fully native app for managing your fonts on MacOS.
Organize into collections, test color themes and logos, watch folders, manage what's installed, and much more.
Available for free at pica.joshpuckett.me/
🚨 WooCommerce Subscriptions has been silently breaking renewals since 2017. This is a must-read if you use the plugin.
@SybreWaaijer found $43k in lost revenue
@adampreiser estimates $100k lost on one of his smallest stores
Check the thread for queries to run on your own site
100,000+ stores run this WooCommerce plugin. I doubt any of them know their payments are broken. Any store with $1M ARR could be missing $700k+ in revenue. If you run WooCommerce Subscriptions, check your store.
Yesterday, I reported a bug to WooCommerce that silently broke subscription payments after a product switch. Then I got worried: if they missed something this obvious, what else did they get wrong? So I started auditing. Within hours, I had found three more bugs. There were 121 affected subscriptions, and $43,274 in lost revenue.
Here's what I found.
WooCommerce Subscriptions has an internal flag that controls whether a subscription charges the customer automatically or waits for them to pay manually. When a customer checks out with (for example) Stripe or PayPal, this flag should be set to "automatic." If it isn't, subscription renewals silently stop working: no charge is attempted, no failure email is sent, and the subscription goes on hold until the customer notices and pays manually, or doesn't and churns.
Bug 1 (stale cache): After saving subscription dates, the order cache was never cleared. Subsequent saves could serve a stale object with the flag still set to its default: manual. Fixed in subscriptions-core 6.9.0.
Bug 2 (broken HPOS backfill): Missing getter/setter methods prevented subscription metadata from being properly synced to postmeta in HPOS when data sync is enabled. Fixed in subscriptions-core 6.5.0.
Bug 3 (unnecessary re-fetch): wcs_create_subscription() returned a freshly fetched instance from cache/DB instead of the already-configured object. Any unsaved state, including the corrected flag, was silently discarded. Fixed in subscriptions-core 7.1.0.
These three combined accounted for roughly 7% of all subscriptions created at checkout that were silently born broken, despite the customer paying successfully. For 7+ years (we have data from 2017–2024). Automatic payments NEVER fired for these subscriptions. Users never got renewal emails, either. The only way to know they were broken was if the customer noticed they lost access and contacted support, or if the merchant audited their database manually.
Bug 4 (switch): When a customer upgrades or downgrades their subscription, the switcher flags the subscription as manual renewal; it only corrects the flag if the payment gateway changes. A customer switching plans while keeping the same gateway (e.g. Stripe to Stripe) cements the flag stuck on manual. I discovered this two days ago, when I found a happy customer in the store overview that I had just helped upgrade, with multiple valid cards on file, put "On Hold" because of a missed payment.
For years, I've offered to help WooCommerce improve its code quality and performance. I dry-run code: I find bugs by reading. All four of these bugs are clearly visible in the source without needing to use the software. They could have been caught early. They weren't. The incompetence is immeasurable (well, actually, with the diagnostic queries in my next post, it might be measurable). Our store is small. WooCommerce Subscriptions powers hundreds of thousands of stores. If 7% of subscriptions were silently broken across even a fraction of them, we're looking at potentially millions of dollars in spoiled revenue industry-wide that could have been prevented. Perhaps even billions.
None of this was disclosed well or at all. No admin notice. No email. No advisory.
The fixes shipped under vague changelog lines like "Make sure we always clear the subscription object from cache after updating dates" and "Ensure proper backfilling of subscription metadata." One fix was labeled "Dev" instead of "Fix." Two don't appear in the GitHub release notes at all. No remediation tool or diagnostic query was provided. Store owners have NO way to know they're affected unless they manually audit their database. The woocommerce-subscriptions-core repo was archived in May 2025 after the code was absorbed into WooCommerce core — making the fix history harder to trace.
If you run WooCommerce Subscriptions and used HPOS before mid-2024, check your store. Queries are linked in the tweet below.
🦋david.click retweeted
This is really neat but it’s not a design tool as much as it’s a design _production_ tool.
The practice of design is mostly about what comes before production.
There’s no doubt in my mind that all parts of software production will become automated very soon. Writing code, making web pages, putting pieces of a design system together etc.
And that’s fine. I think few people actually enjoy this kind of production work. Wouldn’t it be better if we spent our precious time in life on what is more meaningful?!
At the core, the practice of design is methodical; like architecture, not like art. In a nutshell: We find constraints, form comprehension of the whole and propose solutions that honor those constraints. First after that do we enter some form of production phase, usually prototypes first, learn about some constraints that were hidden before, loop back, prototype and then build the production-grade “final” artifact.
These last few tasks are quickly losing value because AI tools can do it much faster (not yet better though) than humans. It’s simply just what has the best RoI for a business.
Some companies and individuals will continue to spend human time on certain parts of the “production line” as a market differentiator, but it will cost them a relatively high price compared to competitors.
Anyhow, I still haven’t seen a tool better than Figma that supports the actually-interesting part of the design process.
I wouldn’t be surprised if Figma focused their products on that, maybe separating “products for production” of “products for ideation & exploration.” The latter would obviously still leverage AI, but not to do the work for me but rather to support my efforts the way a therapist helps me live a better life (not living my life for me.)
Neat! I can see this being very useful for shape() related things (think clipping masks and border-shape)
Updated my SVG-to-CSS converter to support multiple path elements. An easy way to convert complex SVG shapes into CSS.
css-generators.com/svg-to-cs…
It's a single-element implementation with a single shape() value!
You can also have the border-only version using border-shape.
🚨SOMEONE REINVENTED HOW TEXT RENDERS ON THE WEB AND ITS ABSOLUTELY INSANE.
the goated dev behind react, reasonML, and midjourney’s frontend, just dropped Pretext. a tiny typescript library that measures and lays out text 500x faster than the DOM.
he trained models against real browser rendering for weeks until the output matched safari, chrome, and firefox exactly.
the demos are insane!! hundreds of thousands of text boxes at 120fps. magazine layouts and chat bubbles that actually wrap right.
engineers from Vercel, Remix, Figma, and shadcn all cosigned. this is the kind of open source that makes you want to be a better dev.
here are some cool demos in the past 24hrs👇
My dear front-end developers (and anyone who’s interested in the future of interfaces):
I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept):
Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
🦋david.click retweeted
My dear front-end developers (and anyone who’s interested in the future of interfaces):
I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept):
Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
✨ We built WP Composer — an independent, open source Composer repository for WordPress plugins and themes, with 17x faster cold resolves than WPackagist
wp-composer.com/
🦋david.click retweeted
This is hands down the best vector pack I’ve ever made… and it’s out now! Graphic designers check the thread 🤘
`border-shape` can handle both insets and outsets, so you can do effects like this chevron nav (corner-shape can't do both).
This means you get a perfectly-wrapping focus ring without needing to manage z-index or having it partially covered due to overlap.
We're finally solving the tooltip arrow usecase with a new CSS property called `border-shape`
⚠️ WIP early-stage API, timeline TBD on this one, more info coming soon
But it brings a lil tear to my eye to see this working, border and all 🥲
This demo uses anchored container queries + border-shape + a little animation
🦋david.click retweeted
a solid CSS technique for morphing surfaces 🧑🍳
anchor() + @starting-style 💫
a powerful #CSS transition technique enters the ring:
Anchor Interpolated Morphing (AIM)
nerdy.dev/anchor-interpolate…




























