Observability page, waitlist endpoint, and Early Access nav tag - #1057
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Three related pieces that ship the /cloud/observability launch together. The page: a structural copy of the Cloud page with its own copy and art. Hero with an email capture, a four-feature section (session replay, annotations, timeline, insights) with light and dark art, and a closing waitlist CTA reusing the same form. The waitlist: POST /api/waitlist validates, rate limits, and forwards the address to Tally server side. Config via TALLY_FORM_ID and TALLY_EMAIL_FIELD; without them the route returns 503 and the UI shows an error, never a false confirmation. Tally's public API cannot create submissions, so the endpoint its own form page posts to is used instead, which also keeps Tally off the page entirely and lets the form keep the site's own design rather than an iframe's. The nav: Observability was announced as Coming soon and disabled. It is live now, so the coming-soon mechanism is generalised into a `tag` field that labels without disabling; the card links to the page and carries an Early Access chip, in the desktop dropdown and the mobile tray. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
pd-builds
force-pushed
the
observability-early-access
branch
from
August 24, 2026 08:43
bc4d769 to
9b6b9ed
Compare
pr3khar
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
/cloud/observabilitypage, a waitlist endpoint behind its email form, and makes the Observability nav entry a live link./cloud. Hero with email capture, four feature sections, closing CTA.POST /api/waitlistchecks the request came from this site and carries a plausible address, then forwards it to Tally server side. Tally's public API cannot create submissions, so the endpoint its own form page posts to is used; caveats inlib/waitlist/store.ts. Posting server side also keeps Tally off the page, so the form keeps the site's design instead of an iframe's. Success is only reported once Tally returns a submission id; missing config or an upstream failure returns 503 with a visible error. Config:TALLY_FORM_ID,TALLY_EMAIL_FIELD.tagfield labels an item without disabling it, unlikecomingSoonwhich does both. Observability gets an "Early access" chip in the dropdown and mobile tray.Verified:
next buildpasses, the page and endpoint were exercised in a production build, and a real submission through the page UI was recorded by Tally.🤖 Generated with Claude Code