Here's another from my "work" this morning. You can fill in the blanks 😆

Haha! I'm sorry.

Prepped a few slides for HackBarna and this was an asset intended up with 🫣

The Deck product is very new to me. Feels more like a solution for a product manager, instructing a team to build various features - or trying to build the same feature in different ways - simultaneously.

I think it's worth giving it a try.

Housekeeping will appreciate that. They've only just finished mopping down and repainting after the last guest

What other changes are you making to your docs to make them more accessible to LLMs and developers targeting their use?

Should we have a dedicated llms.txt under /docs?

Our OpenAPI spec is pretty big, so should we create dedicated .md versions for each endpoint? Or do you think we should focus on improving the related product docs with more examples?

1. Copy for LLM: copies a markdown version of the current doc to the clipboard
2. View as Markdown: view any docs page as markdown with a ".md" extension
3. llms.txt at the root of the website: Covers docs and other content that sits outside of docs

See the blog for examples: hookdeck.com/blog/transf...

🙌

@speakeasy.com followed with a great session on MCPs and their new product, Gram.

Join the Gram waitlist getgram.ai

I spoke about scaling webhook infrastructure and how Hookdeck helps with the hard parts.

Webhooks at Scale: Best Practices and Lessons Learned
(A written version of my talk)
hookdeck.com/blog/webhook...