GitHub Search is a demonstration application built to test and showcase Cloudflare Pages caching behavior with server-side rendered Angular pages.
How Caching Works
When you navigate to a search or category page, the URL's ?page= parameter is the only query string that Cloudflare uses as part of its cache key. All other parameters (sort, order, etc.) are ignored when computing the cache entry.
This means /search/angular?page=2 and /search/angular?page=2&sort=forks resolve to the same cached response. The first request is rendered by the server and stored; subsequent requests within the TTL are served instantly from cache.
SSR + Load More
When a search page is opened directly (e.g. /angular?page=3), the server renders page 3 results in the HTML. After the page hydrates in the browser, Angular loads pages 1 through 3 in parallel and replaces the view with the full accumulated list. This means the "Load More" button can continue from page 4 without gaps.
Canonical Tags & SEO
Each page sets a canonical <link rel="canonical">: page 1 uses the clean path, pages 2+ include the ?page=N parameter. The canonical updates dynamically when additional pages are loaded via the "Load More" button.
Tech Stack
- ◈Angular 21 — Signals, linkedSignal, effect(), input(), standalone components
- ◈@ngrx/signals 21 — signalStore, withState, withComputed, withMethods, rxMethod
- ◈Tailwind CSS v4 — @theme directive, custom paper color palette
- ◈Angular SSR — Server-side rendering with RenderMode.Server for search routes
- ◈GitHub REST API — Public search API — 60 unauthenticated requests per hour
- ◈Cloudflare Pages — Static/SSR hosting with Cache Rules keyed on ?page= only