Headless Content Management System
헤드리스 CMS
An architecture that separates content management from the front-end interface and delivers content through APIs.
A web architecture built on client-side JavaScript, reusable APIs and pre-rendered markup. Learn how it works and what to consider in practice.
잼스택
The term Jamstack was introduced by a Netlify co-founder in 2015. It describes pre-rendering content at build time and calling APIs through JavaScript when needed. Without assembling pages dynamically for every request, applications can reduce server downtime and the attack surface exposed to DDoS, while CDN caching enables fast global delivery. User-specific data, including live inventory and personalized dashboards, still requires client-side API calls or edge functions. Neglecting these dynamic paths can make a static site unexpectedly slow.
Reduces dynamic server workloads and security exposure while supporting fast page delivery.
Plan client-side API calls for dynamic interactions and real-time data updates.
헤드리스 CMS
An architecture that separates content management from the front-end interface and delivers content through APIs.
디커플드 아키텍처
A software architecture in which independent back-end and front-end layers communicate exclusively through APIs.
SSG (정적 사이트 생성)
Generating pre-rendered HTML, CSS and JavaScript as static files at build time.
SSR (서버 사이드 렌더링)
Generating HTML dynamically on the server for each incoming request and delivering it to the browser.
ISR (증분 정적 재생성)
Periodically regenerating selected static pages in the background without rebuilding the entire site.
하이드레이션
Attaching client-side event listeners and state to server-rendered HTML to make it interactive.