Skip to content

console: remove onboarding survey, land new users on enable-region - #38085

Merged
jubrad merged 1 commit into
MaterializeInc:mainfrom
jubrad:console-remove-onboarding-survey
Aug 6, 2026
Merged

console: remove onboarding survey, land new users on enable-region#38085
jubrad merged 1 commit into
MaterializeInc:mainfrom
jubrad:console-remove-onboarding-survey

Conversation

@jubrad

@jubrad jubrad commented Aug 6, 2026

Copy link
Copy Markdown
Member

Motivation

New organizations previously had to complete (or skip) an onboarding survey before reaching the region enablement screen. This removes the survey entirely so users land directly on the enable-region page, and improves that page's copy to explain what enabling a region means.

Changes

  • Remove the onboarding-survey route from the environment-not-ready flow. The flow's catch-all now redirects to enable-region, so old survey URLs land there too.
  • Delete OnboardingSurvey.tsx (including the internal-only skip button) and onboardingSurveyOptions.ts.
  • Remove submitOnboardingSurvey, its HubSpot endpoint constant, and query key from hubspot.ts. Signup tracking is untouched.
  • Expand the enable-region welcome copy: a region is a dedicated Materialize environment in the chosen cloud provider region, and every new region starts with a default 25cc quickstart cluster that accrues a baseline cost (linked to the billing docs) from enablement until dropped.
  • The post-enablement tutorial slides are unchanged.

Tests

  • New EnvironmentNotReadyRoutes.test.tsx covers the enable-region page rendering, the new region/cost copy and billing link, and the redirects from the root and old survey paths.
  • Removed the submitOnboardingSurvey tests along with the code.
  • Updated the e2e specs to wait for the enable-region page via a new data-testid="enable-region" instead of the survey testid.

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

🤖 Generated with Claude Code

New organizations previously had to complete (or skip) an onboarding
survey before reaching the region enablement screen. Remove the survey
entirely and make enable-region the default destination of the
environment-not-ready flow. Old onboarding-survey URLs redirect there.

Also expand the welcome copy on the enable-region page to explain what
a region is: every new region starts with a default 25cc quickstart
cluster that accrues a baseline cost (linked to the billing docs) from
enablement until dropped.

Removes the survey component, its option lists, and the HubSpot survey
submission plumbing. The post-enablement tutorial slides are unchanged.

Adds EnvironmentNotReadyRoutes tests covering the enable-region page,
the new copy, and the redirects. Updates the e2e specs to wait for the
enable-region page (new data-testid) instead of the survey.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@jubrad
jubrad marked this pull request as ready for review August 6, 2026 17:48
@jubrad
jubrad requested a review from a team as a code owner August 6, 2026 17:48
@jubrad
jubrad requested a review from jdonelson August 6, 2026 17:48

@leedqin leedqin left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM!

@jubrad
jubrad merged commit 2d8c57a into MaterializeInc:main Aug 6, 2026
82 of 83 checks passed
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.

3 participants