Skip to content

Conversation

@joethreepwood
Copy link
Contributor

@joethreepwood joethreepwood commented Jan 19, 2026

Changes

As discussed, I've tried to level this up.

Sales isn't yet providing warehouse support fully, but still. I've snuck it in.

Still warrants some @smallbrownbike love, but I think this is better.


Note

Introduces a new /services page to replace “Professional Services,” with a full redesign (services table, process, training/migration/instrumentation/integration sections, pricing, CTAs, team profiles). Navigation and routing updated: TaskBar menu item renamed to “Services” (new icon), new /services window sizing in App context, and pricing columns gain a “But wait, there’s more…” section linking to platform packages and services. Platform packages page copy updated with in‑app billing links and cross‑link to services. Adds “BAA generator” to the Trust & Security menu. Multiple migration docs now point to /services and include minor copy/formatting tweaks.

Written by Cursor Bugbot for commit b67fb22. This will update automatically on new commits. Configure here.

@vercel
Copy link

vercel bot commented Jan 19, 2026

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

Project Deployment Review Updated (UTC)
posthog Error Error Jan 23, 2026 0:37am

Request Review

@simfish85
Copy link
Contributor

This is amazing, and definitely levels that page up. Thank you for doing it!

@joethreepwood
Copy link
Contributor Author

Thinking on this overnight, I think we should work a link to this page into other places. Three proposals below for us to consider @simfish85 @pawel-cebula @corywatilo

1. Add a link in to the pricing page.
It could pop-up as an option under certain circumstances, like high event volumes, or it could be just exist as a new section. The pricing page is uniquely handled, so I'm proposing this here rather than PRing it.

2. Add a merch store item.
We've seen a good response adding the onboarding team's option to the store. We could add something there just to give it more visibility, if you're game @simfish85 ?

3. Surface it in app
I can't see anywhere where we're doing this already, but we could use an in-app survey to mention this to users if you let me know some criteria to identify leads by @simfish85. We could set this to happen once, for admins/owners only to limit the spammy feel.

Doing all three definitely edges into "Joe is trying to add CTAs everywhere again" territory, so thought worth flagging here before spending time on the PR.

Copy link
Contributor

  1. Add a link in to the pricing page.
    It could pop-up as an option under certain circumstances, like high event volumes, or it could be just exist as a new section. The pricing page is uniquely handled, so I'm proposing this here rather than PRing it.

Makes sense to add this to the pricing page. Since it's not a billing product, it would be hard coded directly in the frontend I assume. This section could be a good spot for it IMO:

image.png

@joethreepwood
Copy link
Contributor Author

Screenshot 2026-01-20 at 10 09 13

Don't hate me for tinkering with things, @smallbrownbike <3

@corywatilo
Copy link
Collaborator

@claude Wrap the /professional-services page in the @src/components/Editor/index.tsx layout.

@joethreepwood
Copy link
Contributor Author

Ran in some changes to simplify the content after some feedback from @raquelmsmith

I think i'm about done with this for now, so from here it's over to @corywatilo and @smallbrownbike to add any further changes.

cursor[bot]

This comment was marked as outdated.

@corywatilo
Copy link
Collaborator

👀
image

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 3 potential issues.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

event=ph_event_name,
properties=properties,
timestamp=ph_timestamp
)
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Python code indentation completely removed

High Severity

All Python code examples in migration docs have lost their indentation. Function bodies, loops, and conditionals are no longer indented, making the code syntactically invalid. Python will throw IndentationError: expected an indented block when users try to run these examples. This affects all eight migration guide files with Python code samples.

Additional Locations (2)

Fix in Cursor Fix in Web

## 3. Converting GA event data to the PostHog schema and capturing

The schema of Google Analytics' exported event data is similar to PostHog's schema, but it requires conversion to work with the rest of PostHog's data. You can see details on the Google Analytics schema in [their docs](https://support.google.com/analytics/answer/7029846?hl=en) and events and properties PostHog autocaptures in [our docs](/docs/product-analytics/autocapture#autocaptured-events).
The schema of Google Analytics' exported event data is similar to PostHog's schema, but it requires conversion to work with the rest of PostHog's data. You can see details on the Google Analytics schema in [their docs](https://support.google.com/analytics/answer/7029846?hl=en) and events and properties PostHog autocaptures in [our docs](/docs/product-analytics/autocapture #autocaptured-events).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Broken markdown anchor links with spaces

High Severity

Markdown anchor links have spaces inserted before the # symbol, breaking the links. For example, /docs/product-analytics/autocapture #autocaptured-events should be /docs/product-analytics/autocapture#autocaptured-events. This affects multiple documentation links across all migration guides, preventing users from navigating to specific sections when they click these links.

Additional Locations (2)

Fix in Cursor Fix in Web


function render() {
const flagValue = posthog.isFeatureEnabled(flagKey);
const flagValue = posthog.isFeatureEnabled(flagKey) ;
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JavaScript code with unusual trailing semicolons

Low Severity

JavaScript code examples have trailing semicolons preceded by a space ( ; instead of ;). While syntactically valid, this formatting is inconsistent with JavaScript conventions and appears unintentional. Lines 249, 252, and 262 show this pattern in variable declarations and function calls.

Fix in Cursor Fix in Web

@corywatilo
Copy link
Collaborator

Updated some things in this PR and merged them into this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants