Adding a process for briefing changes to the website team

[joethreepwood]

Changes

• Closes Website: Creating new slides for product pages #13228

Content here may be useful for @cleo-pleurodon and @SaraMiteva too

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
posthog	Ready	Preview	Oct 20, 2025 1:33pm

💡 Enable Vercel Agent with $100 free credit for automated AI reviews

[greptile-apps]

_{2 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

[corywatilo]

As mentioned in Lisbon a couple times when discussing process, I don't think we're at the point where we should be adding more process like this where website is a dependency like the artwork process. We should be more collaborative in working together, to the point we don't even need a new process because we're already in communication/in sync earlier in the process. At some point maybe we'll need something like this, but I don't think this is the right approach for our team size and where we're at right now.

[joethreepwood]

Definitely heard on the process point, and have tried to keep this as light as possible there. Intent was just to create a way to enable that collaboration you describe.

Only thing I feel strongly about is having a clear direction and avoiding things getting lost in Google Docs and Slack DMs, etc.

To move this to a yes and mode, do you have a way you'd prefer this to work?