@studio_hungry

Director of Docs ▲ @vercel

🇸🇪 Örnsköldsvik, Sverige
Joined August 2018
FIVE years at Vercel today. As anyone who has worked here will tell you, those 5, feel like 10! Some highlights: - Built the docs team from the ground up - Oversaw too many IA and design iterations to count on one hand for the Vercel docs - ITG (Another one is coming!) - Learned about and dove into AEO/Agent Readability and how we can shape our content for both agents and humans - Built our internal user feedback pipeline and tracking - Built many internal tools (AEO, Evals, Feedback, and more!) - Had my fingers in many pies that are our educational content and sites - Managed and learned from some of the best people in the industry (You know who you are! And I love you all) - Grown as a manager, developer, and person - Still can't play anything decent on guitar beyond Oasis
26
1
141
6,465
Big one for not knowing how to plan next summer with registration for glasto and oasis
180
Rich Haines retweeted
This week's @vercel news revolved around the infrastructure that makes your deployments fast and secure. As usual, it was a great week for the Vercel community with new pricing options, performance improvements, and some awesome open source projects
2
6
45
1,526
I love that everyone is all of a sudden massive Oasis fans. They are amazing, and have been my fav band for near on 30 years. But I think the main reason youngsters have started loving them isn’t cos of how good they are, it’s more about the fact that there are no bands anymore.
2
169
I built a knowledge graph over our whole content estate. It’s an SQLite DB that refreshes nightly, and takes in all our docs sites (OSS inc) KB, blog, changelog etc We serve it through multiple entry points to give agents full and surrounding context around each product/features docs page, including semantically similar, and outbound and inbound links. This gives agents the full spectrum as opposed to the single doc to understand where this “thing” fits in within the Vercel ecosystem. Instead of relying on in page links only, the agent can source surrounding context too, without guessing. You can find the root graph at vercel.com/docs/graph.json , the per page graph at e.g vercel.com/docs/functions.gr… , a compact version in the docs pages markdown mirror vercel.com/docs/functions.md , and in the HTML in a collapse at the bottom of each page. I’m still tracking requests, but early data looks promising. Will share more once we have had a month in production!
5
3
1
18
2,538
I’ve not seen one person ever tuck their shirt in like this. Except from when were were about 9 and going into high school
1
241
Sign petition
Request to harnesses: I love that you now send "Accept: text/markdown`. Next thing is: Put the programming language you prefer into the Accept-Language header. Accept-Language: "en-us, python" So, I don't have to feed you the TS examples when you're looking for python.
1
2
158
I haven’t seen one codebase linked with all these tweets claiming Astra made some sick video game, or 3D model of Ancient Rome, or replications of a popular movie…. Grifters gonna grift
2
318
Who would have thunk it? Server render pages. Include all relevant info in the HTML, mirror with markdown, and get your negotiation strategy right. Lots of ideas are floating around right now, it's the wild west of engine optimizations... But the classics still remain the bedrock of human and agent understanding. Serve what you want for agents, to humans, and make it available without JS.
1
283
Rich Haines retweeted
We are open sourcing `cn`, a new engine for Tailwind class merging and conflict resolution. It is a drop-in replacement for tailwind-merge and clsx. It works with all frameworks, runs everywhere and is 30x faster. Brought to you by @aidenybai and me. github.com/shadcn-ui/cn
157
302
57
4,855
426,759
Rich Haines retweeted
Another week of great news for the @vercel community Check out the highlights ↓
4
6
45
2,167
rebuilt @bot but on @vercel infra in several hours hire teammates by asking. they message each other, run in their own sandboxes, and hand work back up the chain. built on eve ▲
10
10
114
10,165
Rich Haines retweeted
build a web or slack eve.dev agent and connect it to your favorite tools! nice launch video too... 🔥
Ship a new eve agent in one minute. From vercel.com/new/agent: 1. Add a prompt 2. Pick models & MCP connections 3. Deploy Your agent is in production, ready to chat, backed by a Git repo you own.
3
2
15
1,318
Rich Haines retweeted
Ora runs agents on live websites and traces every step. When a signup, integration, or payment stalls, teams see which step, what the agent tried, and what to change. The whole platform is built on Vercel, and Ora's own agents run on eve. vercel.com/blog/how-ora-benc…
23
6
5
97
26,685
Rich Haines retweeted
New section added to vercel.com/eve. Give it a spin and see how easy it is. Hint: you'll be amazed by how many third-party services you can connect your agent to.
2
37
2,713
My wife is currently telling off GPT voice mode
4
487
Rich Haines retweeted
AEO will get you surfaced. It doesn't mean you get chosen. Being in the answer is Discovery - necessary, and completely insufficient. Nobody stops at the first answer. The human asks a follow-up: comparing pricing, features and alternatives. Every follow-up tests whether agents can actually read you. When they can't, the answers come from third-party articles and old reviews. Someone else's framing of your product, your pricing and more - in the middle of your deal. Then the last test: can the agent act? Sign up, book, buy, complete the task. If not, the deal closes somewhere else - usually with whoever passed all three. Discovery, Access, Use. AEO covers the first. Surfaced is step one. Being accessible to agents is what gets you chosen.
3
1
9
244
Rich Haines retweeted
just redesigned: vercel.com/for/retail
39
20
3
741
56,070