Add dynamic workshop sales pages backed by Builder events - #19
Draft
zacjones93 wants to merge 2 commits into
Draft
Add dynamic workshop sales pages backed by Builder events#19zacjones93 wants to merge 2 commits into
zacjones93 wants to merge 2 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
What changed
/workshopsindex and dynamic/workshops/[slug]sales pagesWhy
Builder should remain the control plane for Egghead events while the main web app provides the public discovery and sales experience. This connects the existing event/product data to the standalone web app without moving Stripe or Inngest writer ownership into Phase 0.
Commerce findings
Paid event creation already creates and associates CourseBuilder Product/Price records and Stripe Product/Price objects.
The remaining AI Hero parity work is intentionally separate:
This PR reads and displays configured offer data but sends registration through the Builder-managed URL so the web app stays read-only.
Validation
pnpm check/workshopsroute returns 200Note
Add dynamic workshop sales pages backed by Builder events
/workshopsindex page listing upcoming workshops and/workshops/[slug]detail pages with hero, Markdown content, and a sticky offer card showing pricing and registration CTA.workshop.tsthat queries event-type content resources, joins product/price/coupon rows, and normalizes them into typedWorkshopandWorkshopOfferobjects.registrationUrlandctaLabelfields to the Builder admin event editor andEventSchemaso editors can configure outbound registration links and button copy./workshopsplus dynamic workshop slugs in the sitemap.📊 Macroscope summarized d0cfe73. 10 files reviewed, 0 issues evaluated, 0 issues filtered, 0 comments posted
🗂️ Filtered Issues
No issues evaluated.