Developer tools template
Hookcatch
For developers wiring up a service that calls them back. Near black with lime highlights, a live list of requests on the left and the selected one in full on the right.
Opens the prompt in Crisp so you can change it before the build starts.
The look: Neon Night.
Electric and dark: near black, acid lime, big type and a pulse. Headings in Unbounded, text in Figtree.
- background
- surface
- foreground
- primary
- accent
- Opening
- giant type: a huge headline over a dark grid, the date, place or stat in lime, a countdown-style row of facts
- Sections
- dark sections with hairline lime rules, a speaker or lineup grid with hover reveal, a schedule as a timeline
- Motion
- a scrolling strip under the hero, reveal on sections, a slight zoom on hover on photos
- Texture
- a faint grid on the dark bands
The screens.
- 01Bins
- 02Bin view
- 03Request detail
- 04Compare
- 05Bin settings
- 06Account
Build Hookcatch, a webhook inspector for developers. You create a bin, get a unique URL, point a service at it, and watch every request arrive in real time, so you can see what a webhook actually sends before writing the handler. Data: bins (name, slug for the URL, owner, created at, the response to send back: status code, headers, body), requests (bin, method, path, query, headers, body, content type, size, source IP, received at) and replays (request, target URL, response status, sent at). Screens in order. Bins: a page header with a one-line summary, stat cards for bins, requests today and the busiest bin, then the list of bins with their URL, a copy button and the time of the last request. The bin view: a live list of requests on the left that updates without a reload, newest first with method and size, and the selected request on the right with tabs for body (pretty-printed JSON or form fields), headers, query and raw. Actions: copy as curl, replay to another URL and show the response, delete, and compare two requests side by side. A bin settings page for the canned response. Then an account page. Anyone signs up with email; bins are private to their owner, and a bin URL accepts any method. Requests are kept for seven days. Seed two bins with thirty requests that look like payment, form and code push events.Use this template
What Crisp builds from it
- Bins with unique URLs that accept any method
- A live request list that updates without a reload
- Body, headers, query and raw views for each request
- Replay, copy as curl and side by side compare
- Canned responses per bin
Change the name, the town and the details to yours before you start. How a build works.
More developer tools templates.
- Ferrule Docs
Developer docs that read like a book and search as you type
- Steadyline Status
One honest page that says what is working and what is not
- Patternbox
Test a pattern or tidy some JSON, then share it with one link