Pride Intelligence

Recent

    Tech Stack Recommendation LGBTQIA+ Venue Website (Melbourne, 2026)

    19 min read

    19 min read

    Tech Stack Recommendation: LGBTQIA+ Venue Website (Melbourne, 2026)

    Executive Summary

    For a venue site that is 70% marketing content and 30% dynamic functionality, investor-ready, and being built by a design agency (Anti-gravity) with AI-assisted backend work (Claude Code), the optimal stack is:

    • Framework: Next.js 15 (App Router)
    • CMS: Sanity (Growth plan)
    • Hosting: Vercel Pro (syd1 region)
    • Merch store: Square headless integration (Catalog + Orders + Payments APIs)

    This combination leverages the team’s existing Next.js + Railway expertise, delivers the best developer experience for Claude Code-assisted work, provides non-technical staff with the cleanest content editing UX, and ensures Australian-optimised edge performance for investors reviewing the site.

    1. Framework Recommendation: Next.js App Router

    The Case Against Astro (Despite Its Performance Edge)

    Astro is the fastest framework for static content — delivering near-perfect Lighthouse scores, LCP around 0.8s (vs Next.js 1.4s at SSG), and JavaScript bundles of 0–5KB. For a site that were 90%+ static, Astro would be the clear winner on Core Web Vitals. The venue site has 30% dynamic functionality, though: a live events calendar pulling from TryBooking, a merch checkout, function booking forms, Google Reviews integration, and an Instagram feed. Astro’s islands architecture handles this, but it introduces a conceptual mismatch — AI tools like Claude Code may need additional context to correctly implement the islands pattern, adding friction.[^1][^2]

    More decisively: the team already runs Next.js 16 on Railway for the companion dashboard. Building a second repository in a different framework creates a split mental model across codebases, and Anti-gravity’s delivered UI components will almost certainly be React-based. Consolidating on Next.js eliminates a translation layer.

    Why Next.js App Router Wins for This Project

    AI coding compatibility is excellent. Claude Code and Cursor generate Next.js App Router code with ~90% accuracy, requiring minimal manual fixes. Next.js even ships a dedicated AI agents guide (published April 2026) that tells coding agents to read bundled documentation before generating, addressing the “stale training data” problem. This directly benefits a workflow where Claude Code handles backend implementation.[^2][^3][^4]

    Rendering flexibility matches the 70/30 split. Marketing pages (homepage, about, gallery, press) are statically generated (SSG) at build time — these score 95–98 on Lighthouse. Events, reviews, and merch use Incremental Static Regeneration (ISR) or Server Components. The /book and /checkout flows use Server Actions. This per-page granularity is Next.js’s core strength.[^1]

    Third-party integration ecosystem is unmatched. Every platform the venue uses — TryBooking, Square, Xero, Google Calendar, Instagram — has community-supported Next.js integration examples and SDKs. Sanity’s best-in-class CMS integration is explicitly Next.js-first.[^5]

    SEO capability is strong. The App Router metadata API generates automatic <head> tags, Open Graph, and structured data server-side. Core Web Vitals scores of 90+ are achievable with proper use of Server Components and image optimisation. For investor due diligence, a Google PageSpeed score above 90 on mobile matters.[^6][^7]

    Framework Comparison Matrix

    CriterionNext.js App RouterAstroSvelteKitRemix/RRv7
    SEO / Core Web VitalsStrong (90+, effort required)[^6]Best out of box (98+)[^1]Strong[^8]Good[^7]
    Performance (static)1.4s LCP (SSG)[^1]0.8s LCP[^1]~1.0s LCP[^9]~1.5s LCP[^7]
    Performance (dynamic)SSR/ISR/RSC matureGood via adapters[^10]Compiled JS, fast[^9]Edge-first, JS-heavy[^7]
    Dynamic functionalityExcellent (native)Good (islands)[^11]Good[^8]Good[^7]
    Third-party integrationsBest ecosystemGood[^10]Smaller ecosystem[^12]Moderate
    AI coding (Claude Code)Excellent (~90% acc.)[^2][^4]Good[^2]Moderate[^12]Moderate
    Team familiarityHigh (existing app)NoneNoneNone
    Headless CMS optionsAll major CMS[^5]All major CMS[^13]Most major CMSMost major CMS

    Recommendation

    Use Next.js 15 (App Router) with TypeScript and Tailwind CSS. The performance gap between Next.js and Astro is real but manageable — properly configured Server Components, next/image, and ISR will deliver 90+ Lighthouse scores on marketing pages. The tradeoffs in ecosystem depth, AI tooling, team continuity, and dynamic functionality support make Next.js the correct choice for this specific brief.

    2. Headless CMS Recommendation: Sanity

    Why Sanity Fits This Project

    The content requirements have three distinct shapes: structured event records with relationships (Event → Artist → Venue → Date → TryBooking URL), media-heavy galleries and artist profiles, and ad-hoc announcements and menu updates by non-technical staff. Sanity handles all three better than any other option at the price point.

    For non-technical editors, Sanity Studio is fully configurable — which means Claude Code can build a venue-specific editor interface where “Create Event” shows exactly the fields staff need (title, date, lineup, ticket link, hero image, description) with no irrelevant CMS boilerplate. Sanity is ranked #1 out of 85 CMSes on G2. Content editors do not need to touch code or trigger deployments to update events, menus, or announcements.[^14]

    For structured content with relationships, Sanity’s GROQ query language is exceptionally powerful for querying related content — for example, fetching all upcoming events and their artists with a single query. This makes the events calendar and artist profile pages trivial to implement.[^15][^5]

    For image management, Sanity’s Content Lake includes a CDN-backed media library with automatic image optimisation, resizing, and transformation parameters in the URL. A venue site with gallery content, artist photos, and event banners will heavily benefit from this.[^15]

    Cost at small scale (under 5 editors): The free tier supports 500K API requests/month, 20GB bandwidth, and 10GB asset storage — enough for a venue site in development and early live traffic. The Growth plan at $15/project/month is negligible in a capital raise budget. There are no per-seat pricing restrictions that bite at small teams, unlike Contentful at $300/month.[^16][^5][^15]

    For the existing Next.js ecosystem, Sanity’s Next.js integration is considered best-in-class among all headless CMS options, with official starter templates for Next.js 15 + Sanity + Tailwind available on both Sanity’s and Vercel’s template directories.[^17][^18][^19][^5]

    CMS Comparison Matrix

    CriterionSanityContentfulStrapiPayload CMSKeystatic
    Non-technical editor UXGood (configurable)[^5][^14]Best out of box[^5]ModerateDeveloper-focused[^16]Minimal[^20]
    Structured relationsExcellent (GROQ)[^5]GoodGoodExcellentLimited[^21]
    Image managementExcellent (CDN + transform)[^15]GoodGoodGoodMinimal
    Cost (<5 editors)Free → $15/mo[^5]$300/mo[^15]Free (self-hosted)Free (self-hosted)[^16]Free[^21]
    Self-hosted optionNo (Content Lake)[^22]NoYesYes[^23]Yes[^21]
    Next.js integrationBest-in-class[^5]GoodGoodGoodGood
    Real-time collabYes[^5]No[^5]NoNoNo
    Setup overheadLow (managed)[^24]Low (managed)MediumHigh[^22]Low

    On Payload CMS

    Payload deserves mention given the team already runs Railway with PostgreSQL. It is entirely free when self-hosted and gives full data ownership. However, for a venue site where a non-technical bar manager needs to update the events calendar on a Friday afternoon without developer involvement, Payload’s code-first schema approach and lack of a polished out-of-box editor is a liability. The hidden cost is developer time to build and maintain a custom editor interface that Sanity provides by default. For this specific use case, Sanity’s $15/month is well spent.[^22][^23][^16]

    Recommendation

    Use Sanity on the Growth plan. Configure a venue-specific Sanity Studio with document types for: Event, Artist, Resident, Announcement, MenuCategory, MenuItem, GalleryImage, and FunctionPackage. Events have reference fields to Artists, a TryBooking URL field, and a date/time picker. This becomes the single source of truth for all venue content.

    3. Hosting Recommendation: Vercel Pro (syd1)

    The Australian Latency Problem

    This site is for a Melbourne venue, but it’s also being shown to investors who may be reviewing it from anywhere. Both audiences benefit from low-latency delivery. Cloudflare’s 300+ edge locations technically offer the most global coverage, and benchmarks show Cloudflare delivering ~50ms TTFB for EU visitors vs Vercel’s ~70ms. However, for an Australian-origin Next.js application, the decision calculus is different.[^25][^26]

    Vercel’s Sydney Region Changes Everything

    Vercel operates a dedicated Sydney compute region (syd1) available to Pro plan users. This means Next.js Server Components, API routes, and ISR revalidation all execute in Sydney — not in the US or EU. For a site whose primary audience is in Melbourne, this eliminates the latency of cross-continental function calls for any server-side rendering. Vercel’s own documentation explicitly recommends setting the function origin region to Sydney for primarily Australian audiences, noting that users get fast responses even for infrequently accessed content without international routing.[^27][^28]

    Cloudflare Pages, while faster for purely static content, requires an OpenNext adapter for proper Next.js support. This adapter adds a layer of complexity and occasionally lags behind Next.js releases. For a site being shipped by a design agency with AI-assisted coding — where predictability matters — native Vercel deployment eliminates an entire class of deployment edge cases.[^29]

    Railway is the right home for the existing dashboard app (which already runs there) but is not a CDN/edge platform. It lacks preview deployments, automatic edge caching, and the image optimisation pipeline that Vercel provides. Railway’s strength is full-stack apps with persistent processes and databases — keep it for the dashboard.[^30][^31]

    Netlify is consistently the slowest in benchmarks — at least 2x slower than Cloudflare on cold starts, and slower than Vercel on page delivery. Not recommended.[^32]

    Cost Considerations

    Vercel Pro is $20/seat/month (September 2025 pricing), with 1TB bandwidth included. For a team with 2–3 deploying members (developer + design agency), that’s $40–60/month before any overages. Given the capital raise context, this is appropriate and demonstrates professional infrastructure. The Sydney region (syd1) pricing for fast data transfer is $0.16/GB after the included 1TB.[^33][^31][^27]

    Hosting Comparison Matrix

    CriterionVercel ProCloudflare PagesNetlifyRailway
    Australian latencysyd1 compute region[^27][^28]300+ edge PoPs[^26][^34]Slower (~90ms EU)[^25]No CDN/edge[^30]
    Next.js native supportBest (made by Vercel)[^31]Via OpenNext adapter[^29]GoodGood
    Preview deploymentsExcellentGoodGoodManual
    Edge renderingYes (126 PoPs)[^35]Yes (300+ PoPs)[^26]LimitedNo
    Free tier bandwidth100GBUnlimited[^25]100GB[^25]100GB[^33]
    Cost for 2-3 devs$40-60/mo[^33]$0-20/mo$20-30/mo$55/mo[^33]
    ISR / on-demand revalidationNativeVia adapterGoodManual
    Overage riskMedium ($0.16/GB)[^27]Low (unlimited BW)[^25]MediumUsage-based[^33]

    Recommendation

    Use Vercel Pro with the function region set to syd1 (Sydney). This delivers the best combination of Next.js native support, Australian performance, preview deployments for the design agency’s review workflow, and professional-grade infrastructure for investor demos. The cost is manageable and justified by the capital raise context.

    4. Merch Store Recommendation: Square Headless Integration

    Don’t Add a New Platform

    The most important principle for the merch store component is to avoid introducing a fourth commerce platform when Square is already the venue’s POS. Every additional platform creates an inventory reconciliation problem: if a “Black Out Club” hoodie sells at the bar on Saturday night via Square POS, but the online store is powered by Shopify, those are two separate inventory records until a sync job runs. For a small venue selling limited-edition merch, that’s an operational headache and a potential oversell.

    Square’s Headless Commerce APIs Are Production-Ready

    Square provides a full suite of headless commerce APIs:[^36][^37]

    • Catalog API — manage products, variants, pricing, categories[^37]
    • Inventory API — real-time stock levels, shared with POS[^37]
    • Orders API — cart management and order creation[^37]
    • Payments API + Web Payments SDK — PCI-compliant checkout in-page[^38][^36]
    • Checkout API — shareable payment links for simpler flows[^36]

    Because Square is already the POS, inventory is already in Square Catalog. Building a headless storefront against Square APIs means online merch sales automatically decrement the same inventory record that the bar staff see on their Square terminal. Xero already receives Square transactions — so online sales flow into the same accounting pipeline without any additional integration work.[^39]

    Snipcart and Shopify Ruled Out

    Snipcart is developer-friendly and works well on headless Jamstack sites, but it natively integrates with Stripe and PayPal — not Square. Connecting Snipcart to Square requires custom webhook handling and manual reconciliation. Given that Square is already handling thousands of in-venue transactions per week, this is an unnecessary detour.[^40][^41]

    Shopify Storefront API is powerful but overkill for venue merch. A small venue selling 8–15 SKUs (tees, hoodies, caps, vinyl) does not need Shopify’s inventory management, metafields, or multi-channel selling. It also requires a $27/month Shopify subscription on top of Shopify’s transaction fees, plus engineering time to sync Shopify ↔ Square inventory. The operational overhead is not justified.[^42][^43]

    Square Online (Square’s own ecommerce platform) is an option for non-technical teams but produces a generic storefront that cannot be customised to match the venue’s visual identity — exactly the opposite of what a “world-class” investor-facing site requires.

    Implementation Approach

    Build a lightweight merch section within the Next.js site using Square’s Catalog and Payments APIs. Claude Code can scaffold this against Square’s well-documented REST API. Product data can optionally be enriched in Sanity (for editorial descriptions, lookbook photography, and styled content) while inventory and pricing always come live from Square Catalog API. Checkout uses Square’s Web Payments SDK embedded in the Next.js site for PCI compliance without a redirect.

    The data flow:

    1. Staff add new merch to Square Catalog (same workflow as adding POS items)
    2. Next.js site fetches live product data from Square Catalog API at build time (ISR, revalidated on webhook from Square)
    3. Customer adds to cart (client-side state, persisted to Square Orders API)
    4. Checkout renders Square Web Payments SDK in-page
    5. Order confirmed → Square handles fulfilment tracking, Xero receives transaction automatically

    5. Integration Architecture

    TryBooking (Events & Ticketing)

    TryBooking provides a REST API and webhook system (called “Notify URL”). The recommended integration is:[^44][^45]

    • Event display: Pull event listings from TryBooking API at build time via ISR. Sanity stores editorial content (artist bios, event descriptions, gallery images); TryBooking is the system of record for ticket availability and pricing.
    • Ticket availability: Use a server-side API route to fetch live availability, so “Sold Out” indicators are real-time without rebuilding.
    • Ticket purchase: Deep-link to TryBooking’s hosted checkout. Do not attempt to build a custom ticketing checkout — TryBooking’s payment compliance is not worth replicating.
    • Reconciliation: TryBooking webhooks notify a Next.js API route on each booking, which can update Supabase in the existing dashboard app for reporting.

    Google Reviews

    Embed via the Google Places API (Places API — New). Fetch recent reviews server-side in a Next.js Server Component and render them statically. Cache with next/cache and revalidate hourly. This avoids the performance cost of a client-side widget and gives full design control over the review display.

    Instagram Feed

    Use the Instagram Basic Display API or Graph API to fetch recent posts server-side. Render as a static gallery section with ISR revalidation every 15 minutes. Avoid third-party Instagram embed scripts — they add JavaScript payload and potential privacy/tracking concerns.

    Google Calendar (Function Bookings)

    For function/private event bookings, embed a form that integrates with Google Calendar API. A Next.js Server Action can create a Calendar event and send a confirmation email on form submission. This mirrors the pattern used in existing booking system implementations.[^46][^47]

    6. Full Stack Architecture Summary

    ┌─────────────────────────────────────────────────────┐
│                NEXT.JS 15 (App Router)               │
│                  Vercel Pro – syd1                   │
├──────────────┬──────────────────┬───────────────────┤
│  Static/ISR  │  Server Components  │  Server Actions  │
│  (marketing) │  (events, reviews)  │  (forms, cart)   │
└──────┬───────┴────────┬────────┴───────────┬────────┘
       │                │                    │
  Sanity CMS      TryBooking API       Square APIs
  (Content Lake)  (events, tickets)   (catalog, orders,
       │                │              payments)
  Artist profiles  Live availability  Merch inventory
  Event content    Ticket deep-links  Checkout (Web SDK)
  Menus, announcements                Xero auto-sync
       │
  Sanity Studio
  (staff-editable UI)
       │
  Non-technical staff update
  events, menus, artists without
  deploying code

    Supporting services:

    • Google Places API → Review display (server-side, cached)
    • Instagram Graph API → Feed gallery (ISR, 15min refresh)
    • Google Calendar API → Function booking confirmations
    • Railway (existing) → Dashboard/analytics app, unchanged

    7. Investor-Readiness Considerations

    Several decisions above are specifically shaped by the capital raise context:

    Performance signals: Vercel’s syd1 region + Next.js SSG for marketing pages + Sanity’s CDN-backed image delivery will produce Lighthouse scores above 90 on mobile. This is a visible, measurable signal of engineering maturity.[^27]

    Design agency compatibility: Vercel’s preview deployment URLs (one per pull request, shareable) give Anti-gravity a review-and-iterate workflow that matches agency expectations. Every branch push creates a live preview URL at a stable domain.

    Content freshness: Sanity’s Instant Content API means events can be updated without a rebuild. Investors visiting the site will see current events, not stale content from a static build.

    Scalability narrative: The architecture is genuinely scalable — from a single venue to a multi-venue brand. Sanity supports multiple projects; Square APIs scale with transaction volume; Vercel auto-scales compute. This stack is the same architecture used by enterprise event companies, not a hacked-together startup setup.

    No single vendor lock-in: Content is owned in Sanity’s Content Lake (exportable). Commerce logic runs against Square’s open API. The Next.js framework is open-source. Vercel can be swapped for Cloudflare Pages with an OpenNext adapter if cost becomes a concern at scale.

    References

    1. Astro vs Next.js (2026): Pros, Cons & Popularity Compared | Senorit - Astro is 2-3x faster and 50-80% cheaper to host for content sites, while Next.js has more built-in f…

    2. Next.js vs Astro: Complete 2026 Comparison for AI Development - Next.js vs Astro comparison based on production experience. Real performance data, AI compatibility,…

    3. I built a production-ready Next.js app using Claude Code (Here’s … - Gen AI apps are built with MongoDB Atlas. MongoDB Atlas is the developer-friendly database for build…

    4. Guides: AI Coding Agents - Next.js - Learn how to configure your Next.js project so AI coding agents use up-to-date documentation instead…

    5. Sanity vs Contentful (2026): Schema in Code or Enterprise? - 13Labs - Sanity defines schemas in code with real-time collaboration. Contentful has better non-technical edi…

    6. Next.js vs Astro: Choosing the Right Framework for Your Project - Winner for SEO: Astro has a clear advantage for pure performance metrics and Core Web Vitals. Next.j…

    7. Next.js vs Remix vs Astro in 2025: Who Wins the SEO + … - Best Framework for SEO 2025. Here’s the truth: Next.js has grown into a reliable SEO platform. It ha…

    8. Sveltekit vs. Next.js: A side-by-side comparison | Hygraph - SvelteKit and Next.js are two leading frameworks that offer distinct advantages for web development…

    9. SvelteKit vs Next.js in 2026: Why the Underdog is Winning (A … - Why the huge difference? SvelteKit compiles to vanilla JS at build time, eliminating React’s runtime…

    10. Astro vs Next.js Comparison for Modern Web Apps - Tailkits - Which is better for SEO? Astro often outperforms on static content; Next.js excels when you need fre…

    11. Astro vs Next.js: Which Framework Should You Use in 2026? - Astro is better for static, content-focused websites where performance and minimal JavaScript matter…

    12. Next.js vs SvelteKit: Which Framework to Choose in 2025? - LinkedIn - … JS Built-in reactive state management using Svelte’s stores Ideal for performance-focused and SE…

    13. Sanity CMS Integration: Streamline content to live website publishing - This Skill automates the integration of Sanity CMS with an Astro-based website, enabling seamless co…

    14. Event Management CMS | Power Event Content at Scale - Sanity - Sanity is the Content Operating System for events. Manage speakers, schedules, and sponsor content f…

    15. Best Headless CMS in 2026: Cosmic vs Contentful vs Sanity vs Strapi - We compared Cosmic, Contentful, Sanity, Strapi, and Prismic across API speed, pricing, AI features, …

    16. Sanity vs Payload (2026) - CMS - 13Labs - Choosing Between Them. Choose Sanity when your content team needs a polished editing experience and …

    17. Next.js Starters - Spin Up a Next Site in 2 Minutes - Sanity - A Next.js website template and boilerplate crafted for Startup, SaaS, and Business websites. It come…

    18. Sanity templates: get up and running in minutes - Quick setup, lasting impact. A fully customizable Next.js and Sanity starter template with Tailwind …

    19. Sanity starter templates and themes - Vercel - Discover free curated Sanity templates, starters, and themes to jumpstart your website development p…

    20. Keystatic - A tool that makes Markdown, JSON and YAML content in your codebase editable by humans. Live edit con…

    21. Thinkmill/keystatic: First class CMS experience, TypeScript … - First-class CMS experience, TypeScript API, Markdown & YAML/JSON based, no DB. Built with DNA from K…

    22. Sanity vs Payload: Ultimate Hosted vs Self-Hosted CMS Guide - Compare Sanity’s Content Lake vs Payload’s self-hosted database for Next.js projects—pricing, securi…

    23. Compare Payload to Sanity | Sanity Alternatives - As a fully open-source solution, Payload provides complete data control that can be self-hosted, whi…

    24. Payload CMS vs. Sanity: Choose your Fighter! - Brightscout - Self-hosted solutions like Payload require more technical investment but provide complete control, w…

    25. Cloudflare vs Vercel vs Netlify for engineering websites in 2026 - Comparative benchmarks from 2026 put Cloudflare Pages ahead on EU-specific latency. … Cloudflare P…

    26. Vercel vs Netlify vs Cloudflare Pages: 2025 Comparison for … - Netlify: Provides serverless functions with a straightforward pricing model, but performance may lag…

    27. Sydney, Australia (syd1) pricing - Vercel - The table below shows Managed Infrastructure products with pricing specific to the Sydney, Australia…

    28. Vercel’s framework-defined approach to caching (Luba Kravchenko) - … vercel.com/blog/framework-defined-infrastructure • Explore caching on Vercel’s Edge Network: htt…

    29. Setting up my personal prototyping environment with Claude Code - First, I created a basic Next.js application. I adopted a simple directory structure using the Pages…

    30. Vercel vs Netlify vs Railway: Deployment Platforms - 13Labs - For frontend-only deployments, Vercel and Netlify are comparably priced. For full-stack applications…

    31. 10 Best Next.js Hosting Providers in 2026 - MakerKit - Compare the best Next.js hosting providers in 2026. Vercel, Cloudflare, Railway, AWS, and self-hosti…

    32. I measured Vercel vs Netlify vs Cloudflare cold start timings … - Reddit - Alright, some findings first: Cloudflare is the fastest overall with minimal cold start impact. Netl…

    33. Next.js Hosting Costs 2026: Vercel vs Railway vs Self … - Temps - Next.js deployment costs range from $7/month self-hosted to $505+/month on Vercel Pro, depending on …

    34. BunnyCDN vs Cloudflare: Why Australian Routing Matters - When someone in Australia visits your website, they should connect to a local edge server: Expected …

    35. Global network and regions - Vercel - View the list of regions supported by Vercel’s CDN and learn about our global infrastructure.

    36. eCommerce API Guide: Build Custom Integrations - Square Developer - Developers can integrate Square features into their eCommerce solutions by calling RESTful Square AP…

    37. Commerce API: Sell, Process, Manage, and Book - Sellers can use Square commerce and eCommerce APIs to process orders, manage catalogs, track invento…

    38. POS API for Developers | Square - Square’s powerful Point of Sale (POS) API makes it easy for developers to create your own custom, PC…

    39. Integrating Square API with Existing E-commerce Platforms - The Square Developer Platform provides APIs for you to integrate Square payments into your applicati…

    40. Shopify vs Snipcart: Which Ecommerce Platform Should You Choose? - Shopify offers broader, more accessible customer support, which makes it a better option for general…

    41. Shopify vs Snipcart — Which One Should You Actually Use? - Shopify vs Snipcart: Compare features, pricing, performance, and use cases to find the best ecommerc…

    42. Shopify vs Square: which is better online and in store? - You could say Shopify is the go-to online store platform for retailers, while Square is the jack-of-…

    43. Headless Commerce: Next.js Storefront Dev Guide - Our eCommerce solutions service covers full headless storefront development — from API integration t…

    44. TryBooking API - It allows you to access the event and booking data and passes the requested data via API calls to an…

    45. Get attendees for a TryBooking event as an organizer through API - You are correct, the expected use case is to setup webhooks (called ‘Notify URL’ in the TryBooking) …

    46. How I Built My Own Meeting Booking System - Andrii Furmanets - My journey building a custom booking system with Next.js, React, and Google Calendar API. No more su…

    47. Build and host your own Calendy-like scheduling page using Next.js … - Once your project is created, head to APIs & Services ▷ Library and search for Gmail API and Google …

    Graph View