PostHog / PostHog/posthog.com

New website page: Desktop Canvas Gallery

Open
#20,072 0 comments 0 reactions 2 assignees View on GitHub

@ianmatson is already working on this.

Since Sep 10, 2026.

  • #20020 by @cleo-pleurodon — open
design new landing page website
Dominant language
TypeScript
Stars
1.1k
Forks
907
Avg merge
1d 16h
Merged PRs (30d)
430

Description

What do you need?

A public page at posthog.com/desktop-gallery (name TBD) collecting real canvases and artifacts generated in Desktop, with the prompt, PostHog tools, and context that produced them.

Why: Desktop is in open beta and the hardest thing to explain about it is generative UI canvases. Screenshots of a chat window don't do it. A collection of weird, specific, real use cases does the explaining for us.

Not aiming to create a template library. This is closer to a gallery / swipe file to break your frame about what's possible to do with your data model. The point is that a viewer thinks "wait, you can do that?" and then tries it themself.

Prototype

https://github.com/PostHog/posthog.com/pull/20020
Design notes and screenshots in PR description

Deadline

I'd like to get this live ASAP so we can get more usage of canvases and feedback for the product team
(thus I built a prototype instead of google doc with copy)

Technical questions for the team
  • Live vs static. Canvases are generated UI. Can we render them live view/externally shareable url, or does v1 need to be screenshots and clips? Happy to ship static first if live is a bigger lift – but flag it, because live is most of the magic.
  • I've pulled examples from our project. Anything with customer data, internal revenue numbers, or unreleased product names gets scrubbed or synthesised before it goes up. This is limited to our imaginations. ideally we could have a method for community members to submit a canvas
  • Could each canvas have a permalink and OG image to built of some use case marketing / SEO for Desktop?

References & examples

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.