Blog

Indigo Engineering's team was sharing AI-generated HTML as Slack screenshots. Here's how they moved the whole workflow to display.dev – rendered, versioned, commentable pages for the whole team.

Export a Jupyter notebook to one self-contained HTML file, then publish it behind your company's Google or Microsoft login. No public link, no nbviewer, no JupyterHub to run.

Playwright's default HTML report is a folder you can't just send. Generate one self-contained report file, then publish it behind company auth so the team opens a link instead of unzipping an artifact.

Render a Quarto or R Markdown report to one self-contained HTML file, then publish it behind your company's Google or Microsoft login. No RPubs, no public Quarto Pub link, no Posit Connect server.

DocSend can't render an interactive HTML file. It flattens every upload into page images, so charts and scripts die. Here's what to use instead for live HTML, split by whether your audience is your own company or outside prospects.

A plain link can't tell you if anyone opened it, and a click counter can't tell you who. Here's how to actually know who opened a shared page, by verified identity, plus where link shorteners and tracking pixels still fit.

There are two different things people mean by 'HTML password protection,' and the common one is just obfuscation. Here's how each works, when a password is enough, and why identity-based company auth is the stronger answer for anything confidential.

An AI-generated report is interactive HTML, and email plus PDF flattens it. Here's how to share an AI report with stakeholders as a clean, permanent link behind company auth, when to send a PDF instead, and how to automate recurring reports.

You built a prototype in v0, Bolt, or Lovable and now you need the team to see it, not the whole internet. Here's how to share an AI prototype behind company auth, with no developer and no Vercel account for the people viewing it.

ChatGPT Canvas gives you interactive HTML, but no clean way to send just that artifact to your team. Here's how to share a Canvas as a permanent link behind company auth, so the right people see the work and not the whole conversation.

AI agents don't browse wikis. An agent-native knowledge platform stores information in formats agents can query directly – not formats built for human browsers.

AI agents generate polished HTML reports and docs – and then there's no good way to share them internally. Here's why standard tools all fail.

Azure Static Web Apps only supports Microsoft Entra, not Google Workspace. Here's what teams on Google SSO use instead for internal HTML hosting.

Claude Code output sits in a local file. Here's how to turn it into a company-gated URL your whole team can open in one command, 15 seconds.

How to add display.dev as an MCP tool in Claude Desktop so you can publish any artifact to your team in one conversation turn, no terminal and no GitHub.

Claude's Publish button creates a public URL anyone can see, with no access control. Here's how to share Claude artifacts behind your company login instead.

Cloudflare Access charges per seat to gate static files. Here's how teams get authenticated internal HTML hosting without the per-seat pricing.

We tested 7 names for this category before landing on gated publishing. Here's what each got wrong and why the definition matters.

Google Drive, Slack, Dropbox – none render HTML files for teammates. Here's what happens with each sharing method and what actually works instead.

Public hosting gives you a URL anyone can see. Gated publishing restricts it to your company. Here's the difference and when to use each.

GitBook charges per reader for visitor authentication. display.dev gates HTML and Markdown behind company SSO for a flat monthly fee. Here's how they compare.

GitHub Actions produces HTML reports. Here's how to publish them behind company auth automatically – one step in your workflow, no manual upload.

Private GitHub Pages requires Enterprise at $21/user/month, and every viewer needs a GitHub account. Here's what teams use instead for internal HTML sharing.

Imgur became the default image host because uploading was instant. Gated publishing is the missing equivalent for engineering teams sharing HTML internally.

AI agents can now publish their own output via MCP. Here's how MCP publish tools work and why they change how teams receive AI-generated content.

MkDocs builds a static HTML site. Here's how to share it with teammates who don't have GitHub, behind company auth, without any new infrastructure.

Per-seat pricing makes sense for active users. For content shared with passive viewers – PMs, execs, clients – it punishes you for having a larger audience.

S3 + Cognito + CloudFront is the DIY version of gated publishing. Here's an honest build vs. buy breakdown: time, cost, and maintenance.

D3, Mermaid, and Excalidraw export interactive HTML. Screenshots lose the interactivity. Here's how to share architecture diagrams with your team in full fidelity.

PMs and analysts use Claude too. Here's how to share Claude artifacts with your whole team, including people without Claude access, no terminal needed.

Claude Code writes HTML to your local filesystem. Here's how to share those artifacts with your whole team, including non-engineers, in one command.

There are 7 ways engineers share HTML files internally. Screenshots, Slack uploads, PDFs, Google Docs – six destroy the interactivity. One works.

Confluence is overkill for a Markdown spec or HTML report. Here's how to share internal docs behind company auth without a wiki or per-seat pricing.

Plotly and Dash export interactive HTML. Publishing them behind company login so stakeholders can view without a Python environment takes one command.

Sharing internal HTML via public URLs or open S3 buckets creates audit findings. Here's the compliance case for managed gated publishing and SOC 2.

Swagger UI and Redoc export standalone HTML. Here's how to host internal API docs behind company SSO without Cloudflare Access or a new server.

Tiiny.host is fast for public HTML. For internal content you need company SSO, not a shared password. Here's what teams use when viewers shouldn't need accounts.

Vercel requires a full deployment pipeline to serve an HTML file. display.dev skips the pipeline – drop any file, get a company-gated URL in 15 seconds.

Gated publishing: serving HTML or Markdown behind company identity – no public URL, no GitHub, no IT ticket. Here's how it works and when to use it.