We build display.dev — a tool that publishes HTML and Markdown behind company auth (Google/MS SSO out of the box, in-line comments for collaboration).
Indigo Engineering (data tools for progressive organizers) was sharing AI-generated artifacts in Slack. HTML artifacts had to be pasted as screenshots since Slack can't render them. Comments lived in the thread, not on the work. Versioning was a mess.
They moved to display.dev. Their CEO Max Wood: "Before display.dev, we were sharing artifact files with each other in Slack and putting our comments there. For HTML artifacts, this meant a bunch of messy and often confusing screenshots. It also meant several conversations were mushed
into the same thread, versioning was a nightmare."
Two unexpected wins: faster iteration on a major redesign they'd been mired in, and dropping Google Docs (their docs are now markdown-native, and converting them was a chore).
Indigo Engineering (data tools for progressive organizers) was sharing AI-generated artifacts in Slack. HTML artifacts had to be pasted as screenshots since Slack can't render them. Comments lived in the thread, not on the work. Versioning was a mess.
They moved to display.dev. Their CEO Max Wood: "Before display.dev, we were sharing artifact files with each other in Slack and putting our comments there. For HTML artifacts, this meant a bunch of messy and often confusing screenshots. It also meant several conversations were mushed into the same thread, versioning was a nightmare."
Two unexpected wins: faster iteration on a major redesign they'd been mired in, and dropping Google Docs (their docs are now markdown-native, and converting them was a chore).
Full case study: https://display.dev/customers/indigo-engineering