Release-gated continuous delivery: follows a registry image channel and redeploys the product safely, with backup, health check and rollback
An image captcha the product draws itself, with digits read out for whoever cannot see it, no keys and no third party, as the provider of captcha
REST API v1 and v2 of the datasets and their files, out of dataset: fine token scopes, public reads of what is published, tokens limited to some datasets, versioned schemas and the audit trail of every write; v2 with public ids, cursor pages, problem+json, ETags and publication as a resource
The page of a hub's search: /explore, /api/v1/search with its declared schema and the header search box, over the public sources the features register in the framework's search registry (a hub's datasets and files, their facets and orders), which the search feature browses with Elasticsearch or in memory. It names no kind of material, so another hub explores its own.
Each person's folder in the browser: list, resumable upload, download as file or zip, preview, folders, rename, move and delete, done as the folder's owner by filesd, a standard-library server; where the folder is comes from whichever feature keeps folders
The icons every page draws: Lucide and brand logos from simple-icons, installed with npm, drawn by the server with icon()
Public landing page with the unauthenticated home route
Product-wide search over whatever the installed features declare searchable, with the owning feature deciding at request time who may see each hit, and a faceted browse of the public sources (words as they are typed, facets with their counts, orders, pages) answered from Elasticsearch when the product has it and from the sources' documents in memory when it does not