Repository navigation
feat(content): serve sheet content from the server with cache components - #42
Merged
maxitect merged 17 commits intoNov 12, 2026
Merged
Conversation
✅ Deploy Preview for clarksbowlingclub ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
maxitect
deleted the
feat/27-serve-google-sheets-content-from-the-server-with
branch
November 12, 2026 22:11
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
About, Music, Tour and Lyrics now get their Google Sheet content on the server from cached readers, so the HTML contains the content and visitors' browsers no longer call Google.
Changes
cacheComponents: true; each sheet tab is read by a cached function insrc/lib/data/content.ts(Next'sminutesprofile) that pages,sitemap.xml,llms.txtand the.mdpages shareconsole.logcalls are goneSHEET_CSV_URL(frontend)route group (ready for Payload's admin in Replace the Google Sheet with Payload for site content #33), database rules for Payload collections, thepayload-collectionskill, andINSTRUCTIONS.mdupdatesAcceptance criteria
/tourHTML contains the tour dates, not "Loading..."docs.google.comon any pagepnpm lint,pnpm typecheckandpnpm buildpassCloses
Closes #27
Notes
SHEET_CSV_URLis set on Netlify for every context (production, deploy previews, branch deploys,dev).NEXT_PUBLIC_CSV_URLcan be removed from Netlify after the merge.SHEET_CSV_URL, because pages are now prerendered from the sheet. The URL is not a secret: it was in the browser bundle asNEXT_PUBLIC_CSV_URL.text/csv, without one of the two language columns, or not within 8 seconds. At build time that fails the build rather than publishing empty pages; at run time the last good page keeps being served. A throttled sheet (as on 11 November) blocks a deploy, not the live site./tourerror, because it is read per request and has no error boundary. Recorded for a later ticket./touris partly prerendered: the title and intro are static, the dates stream in from a function on each request, so the past and upcoming split is never cached. That is one function call per/tourview against the 125,000 a month./sitemap.xmland/llms.txtare rendered on request from the cached readers (0.27 to 0.75 s on the preview).main;pnpm lintreports none./icon-4usi79.svg); nothing links the old ones.<Suspense>had left it out of every static page's HTML; README andINSTRUCTIONS.mdnameSHEET_CSV_URLand the(frontend)paths./sitemap.xmlruns a function on every request and could be cached.(frontend)route group,.claude/rules/database.md, thepayload-collectionskill and theINSTRUCTIONS.mdedits. Payload itself is not in this PR; it stays onfeat/32-spike-payload-with-neon-and-cache-components-onfor Replace the Google Sheet with Payload for site content #33.Evidence
AC1
AC2
AC3
Review fixes
AC4
AC5