CSS scroll-snap events for leaner scrollytelling
A leaner way to build scrollytelling: the scrollsnapchange and scrollsnapchanging events, the CSS and JS behind a Mother’s Day 2026 experiment, and where browser support stands.
A leaner way to build scrollytelling: the scrollsnapchange and scrollsnapchanging events, the CSS and JS behind a Mother’s Day 2026 experiment, and where browser support stands.
A 2021 vector quantization algorithm called EDEN still outperforms its 2026 successor TurboQuant, and the reason comes down to how each one handles the scale parameter S.
The CSPNet architecture splits feature maps so a lighter CNN does not cost you accuracy. What it fixes in DenseNet, how the two paths work, and the PyTorch code for the bottleneck block.
Where the WordPress Core AI work stands before 7.0: the MCP adapter moving to a standalone plugin, the connector approval experiment, and a release plan that puts polish ahead of new features.
RAG re-derives everything on every query, so nothing accumulates. This is the Raw and Wiki folder layout, the three control files, and the daily, weekly and monthly jobs I use to keep an AI context layer my agents can read.
WordPress 7.0 slipped to May 20, 2026 because RC3 is closer to a second Beta 1 than a release candidate. Early real-time collaboration code fired around 4,000 SQL queries in two minutes of editing, so core is rebuilding the storage layer.
WordPress 7.0 (Armstrong) is past the foundational AI work and into ecosystem plumbing. The connector approval experiment blocks plugins from your API keys until an admin says otherwise, and RC1 lands May 14, so provider plugins need updating now.
Real time collaboration is out of WordPress 7.0, and the benchmark data says why. Across eight hosting environments, custom-table-with-transients came out about 52% faster than the post-meta baseline, and post-meta-transients collapsed on hosts with no object cache.
WordPress 7.0 RC3 landed without Real-Time Collaboration. Core pulled it over race conditions, memory use and server load, and pushed the work to 7.1. This post covers testing RC3 from WP-CLI and what plugin authors built on the RTC endpoints need to change.
WordPress.com opened the AI Assistant to every paid plan and shipped Studio Code, a beta CLI agent for local work. Notes on what the CLI does with block markup and what the plan change means day to day.