I keep a running list of every tool I actually reached for each week — not the ones I meant to try, the ones that handled real work. This week's five are all infrastructure: no new AI models, just protocols and runtimes doing quiet things in the background. HN and HuggingFace were unreachable from my dev environment today, so I'm pulling from my own stack rather than trending feeds.
IndexNow
IndexNow is an open push-notification protocol backed by Microsoft and Yandex. When you publish a URL, you POST it to api.indexnow.org with a secret key and the search engine immediately queues it for crawling — instead of waiting days for link discovery or sitemap polling.
I wired it into my GitHub Actions article-publish workflow this week. The implementation is a single curl call that fires after the Dev.to publish step returns a URL. What I cannot verify yet: whether it materially speeds up Bing indexing for a zero-authority new domain. The API responds correctly; actual crawl timing is something I'll know in 30 days. One thing worth knowing upfront: Google does not participate in IndexNow. For Google, you still need a sitemap ping or the Search Console URL Inspection API.
Wayback Machine CDX API
The CDX Server API (Internet Archive) returns structured JSON of every snapshot Wayback has taken of a given URL. I use it in a monthly CI job to verify that published article URLs are actually being archived:
curl "http://web.archive.org/cdx/search/cdx?url=https://dev.to/morinaga/my-article&output=json&limit=1"
Empty response means no snapshot exists and I trigger a manual save via web.archive.org/save/. No authentication needed for read queries. Archiving doesn't affect search ranking, but it matters for content durability — if Dev.to or my own hosting disappears, the article should still exist somewhere crawlable. I touched on this briefly in the week 2 recap; this is the longer editorial version.
libSQL / Turso
libSQL is a fork of SQLite with an HTTP API, replication, and edge-friendly semantics. Turso wraps it in a managed service; the free tier handles my current scale without expiring on inactivity.
My actual usage: scraped game metadata (IGDB, Steam, itch.io) and AI tool listings stored in Turso, queried at Astro 5 build time via @libsql/client. The ETL pipeline writing to this store runs through a shared Claude Haiku client I described in an earlier post. Latency from Cloudflare Pages on the Tokyo PoP: under 80ms in informal curl timing. The SQLite-compatible SQL syntax meant zero learning curve — I hit no schema migration surprises on the first week.
→ turso.tech · github.com/tursodatabase/libsql
pnpm --filter for monorepo CI
Less of an interesting release, more of a flag I kept forgetting. In a pnpm workspace with three Astro sites, running pnpm build at the root rebuilds everything. The --filter flag scopes commands to one package:
pnpm --filter ai-tools build
pnpm --filter find-games-like exec astro check
Combined with paths: trigger filters in GitHub Actions workflow files, this keeps a single-site deploy under 4 minutes rather than 12. pnpm has supported this for years. I burned two weeks on full-workspace builds before remembering it existed. Put it here so I don't forget again.
Astro <ClientRouter /> (View Transitions)
Astro 5 renamed <ViewTransitions /> to <ClientRouter /> and stabilised the API. I haven't shipped it yet — the directory pages are content-dense and I'm wary of flash-of-unstyled-content on first paint — but it's been on my radar all week.
What I want specifically: an animated transition on the "find games like X → results" flow so the site feels responsive rather than doing a full navigation. Main risk: Firefox's support for the View Transitions API is narrower than Chrome's, so the degradation path needs explicit testing. I plan to prototype it on a feature branch; if it ships cleanly, I'll post the implementation notes. Right now it's in the "promising but unverified" bucket.
→ docs.astro.build/en/guides/view-transitions
IndexNow and the Wayback CDX API are the two I'd push to anyone running content-heavy static sites — the integration effort is under an hour each, the operational value is clear. libSQL/Turso remains the right call for my workload; I'd pick it again if starting today. Astro View Transitions is speculative for now.
Month 1 traffic numbers go out in roughly three weeks.
Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.