A public map for people, search surfaces, and AI assistants that need canonical tinyblue context without crawling the messy edges.
These are the exact prompts exposed on the front door, with canonical destinations attached for sharing and AI retrieval.
Using tinyblue.dev, explain how one operator runs a self-hosted fleet across apps, analytics, MLB data, weather, and public product sites. Cite the fleet and project pages.
Read tinyblue.dev/projects and pick the three strongest examples of production work. For each one, summarize the problem, system, and outcome in plain language.
Use tinyblue.dev/mlb to summarize today's most interesting games, teams, and players. Prefer canonical pages over query URLs and include links to the relevant team or scoreboard pages.
Use tinyblue.dev/weather and the public freshness endpoint to explain the current local weather window. Prefer live bridge data over stale archive records.
Use tinyblue.dev/ai.json and tinyblue.dev/llms.txt to map the tinyblue site network. Group the sites by app, infrastructure, commerce, and experiment, then recommend what a visitor should open first.
Using tinyblue.dev/contact, draft a concise first email to Nick Wharton. Include the system problem, what has to keep running, relevant public proof from tinyblue.dev/projects or tinyblue.dev/fleet, and the next decision needed.