Overview
Bio Santekno is an auto-fresh link-in-bio and portfolio. It aggregates live stats (articles, videos, subscribers) server-side and renders with ISR so the page is fast and SEO-friendly while staying current.
Gallery
An auto-fresh link-in-bio rendered with ISR — profile, links, and a shareable URL.
Problem & Solution
Static link pages go stale and bury the engineer story behind a wall of links; client-side widgets leak keys and hurt SEO.
A Backend-for-Frontend aggregates every source with secrets kept server-side, caches per source in Redis (TTL + SWR), and the page is ISR with graceful degradation — a failed source hides its section instead of breaking the page.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
A BFF route handler fetches every source server-side and normalizes them into one payload, cached per source in Upstash Redis. The page is statically generated with ISR and revalidated on publish via a webhook.
Features
- Always-fresh links & stats
- Fast first paint (ISR)
- Share the profile in one tap
- Edit via one config file
- Auto-fresh dynamic sections
- SEO metadata + sitemap
- Secrets stay server-side
- Per-source cache (TTL + SWR)
- Graceful degradation per section
Tech Stack
Engineering Challenges
Live data must stay current without slowing first paint. Fix: ISR + on-demand revalidation, with stale-while-revalidate cache so visitors never wait on upstream.
Any upstream (YouTube, GA4, RSS) can fail. Fix: fetch sources independently and hide a failed section — never a raw error or a misleading 0.
API keys must never reach the browser. Fix: a BFF route handler holds all secrets; the client receives only a normalized payload, verified by a build-time secret scan.
Outcomes
Lessons Learned
A BFF is the simplest way to keep keys safe and the client light. Graceful degradation turns flaky upstreams into a non-event. And ISR gives the freshness of dynamic with the speed of static.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.