DEVELOPMENT NOTES
Building the
competition gallery.
A place for Alexander Yang’s competition recordings.
A calm place to watch
The selected design pairs a traditional dojo illustration with warm parchment surfaces and cedar-brown accents. Goku and Vegeta bring a playful judo scene to the banner, while the headline stays readable as live text over the image. A four-column desktop gallery keeps the recordings at the centre of the experience. On smaller screens, the grid adjusts to two columns and then one.
One application, a focused stack
Next.js, React, and TypeScript form the application foundation. Cloudflare Stream hosts the recordings and provides the player and thumbnails. The Greatness Witnessed visit counter is designed to use Supabase PostgreSQL for persistent storage. Sign-in, likes, and comments are deferred. GitHub and Vercel are the intended source-control and deployment workflow.
Building with Codex
I built this site with Codex while using a ChatGPT Plus membership that was available to me free for one month. I used only the 6.1 Sol model, switching between Medium and High effort throughout the project.
I described the gallery I wanted, chose the technology stack, and refined the design through the browser preview. I could point to a specific part of the page and ask Codex to change a title, move a control, or adjust the layout. Codex handled the implementation while I reviewed the results and made the design decisions.
Plugins for services such as Cloudflare, Supabase, GitHub, and Vercel connect that coding workflow to the tools used to run a site. They give Codex a way to work with hosted videos and the database, push source code to GitHub, and manage deployments on Vercel. This makes it possible to carry work from the application code into its supporting services within the same workflow.
My competition videos were already uploaded to Cloudflare Stream. Codex inspected the existing library and collected the video IDs, playback URLs, and thumbnail URLs for all 25 recordings, then saved them in a local inventory for the gallery. The thumbnails use those image URLs, and selecting a card opens the corresponding Cloudflare player in the modal. During that setup, the Cloudflare plugin’s operations were not available in the chat, so Codex retrieved the information through the signed-in Cloudflare dashboard.
For this gallery, Codex has created and verified the Supabase tables and database function behind Greatness Witnessed. The experience has been a practical way to turn my ideas into a working site while learning about the decisions behind it.
Load thumbnails as visitors scroll
The gallery separates loading a thumbnail from loading a video. Each thumbnail uses the Next.js Image component, which defaults to lazy loading. The browser starts fetching images as they approach the viewport—the visible part of the page—rather than downloading every thumbnail immediately. Starting slightly before an image comes into view helps keep scrolling smooth.
The cards reserve space for their thumbnails with a fixed aspect ratio, so loading an image does not push the surrounding content around. The large dojo banner is prioritised because it is visible when the page first opens.
The Cloudflare video player is only created after a visitor selects a card. Scrolling through the gallery does not create video players or start video playback. Closing the modal removes the player. All 25 titles, dates, and other card metadata are included in the initial page; only the heavier thumbnail requests are deferred until needed.
For this collection, lazy-loaded thumbnails and on-demand players keep the approach simple. If the library grows substantially, pagination or an explicit “Load more videos” button could fetch additional batches of card metadata. That would be a separate improvement from image lazy loading, and would let visitors control loading while keeping the footer reachable.
Static pages where content changes infrequently
About, the Blog listing, individual articles, and Contact are statically rendered in the production build. Next.js generates their HTML at build time because they do not need information from an incoming request. Their content can be served without rendering those pages again for every visitor; edits to the content become available with the next deployment.
The Contact form does not require server-side page rendering. The page contains a normal HTML form that submits to Formspree when a visitor sends a message. Displaying the form and processing its submission are separate concerns.
Server rendering for the searchable Home page
Home currently uses server-side rendering (SSR). In src/app/page.tsx, it reads the incoming searchParams value so a search URL can render the matching recordings. Reading that request-specific API is what makes the page dynamic; an async function alone does not require SSR.
The video inventory still comes from the reviewed local snapshot. SSR does not automatically synchronise it with Cloudflare. Sport filters, date sorting, and opening a modal are interactive features handled in the browser after the initial page loads.
Both static rendering and SSR produce HTML that search engines can read. SSR is not inherently better for SEO. This split keeps infrequently changing pages static while supporting request-based search on Home. Next.js determines the rendering mode from the APIs each route uses; the npm run build summary confirms which routes are static and which render on demand.
A live counter on otherwise static pages
Greatness Witnessed is a small client component in the shared footer. After the page loads, it calls the counter endpoint to record an eligible visit and display the total. The endpoint uses Supabase for persistent storage, while local and preview visits are excluded. This independent request lets the counter update without making About, Blog, or Contact server-rendered pages.
Accessibility as part of the foundation
The interface is being developed toward WCAG 2.1 AA, including keyboard navigation, visible focus, labeled controls, and responsive layouts. Captions and audio description have been deferred for the initial release, so full-site WCAG conformance is not claimed.
Where the build stands
The first application version uses a read-only inventory of the uploaded recordings. Videos play in a modal so visitors stay in the collection. This release focuses on deploying the frontend with a production-only visit counter; authentication, likes, and comments are deferred.