Headless Content Management System
헤드리스 CMS
An architecture that separates content management from the front-end interface and delivers content through APIs.
An interface that delivers content from a headless CMS to the front end as JSON through REST or GraphQL. Review implementation considerations.
콘텐츠 API
REST endpoints return predefined fields, which simplifies caching but often leads to over-fetching. GraphQL lets clients request only the fields they need, reducing payload size, while query interpretation makes server-side caching more complex. Large headless platforms such as Contentful and Sanity commonly provide both options. A hybrid approach can cache listing pages through REST and retrieve precise field combinations for complex detail pages through GraphQL.
Minimizes payloads through targeted GraphQL queries or cached REST endpoints.
Manage REST over-fetching and the back-end query complexity introduced by GraphQL.
헤드리스 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.
잼스택
A web architecture built on client-side JavaScript, reusable APIs and pre-rendered markup.
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.