Content API (REST / GraphQL)
콘텐츠 API
An interface that delivers content from a headless CMS to the front end as JSON through REST or GraphQL.
A software architecture in which independent back-end and front-end layers communicate exclusively through APIs. Explore its practical uses.
디커플드 아키텍처
Decoupled architecture is broader than headless content delivery. It includes any system whose back-end services and front end are separated by a network boundary, such as microservices paired with an SPA. Lower coupling introduces responsibilities previously handled by the framework: authentication tokens, CORS and preview workflows must be designed explicitly. Live preview is particularly demanding because editors need to view unpublished pages through separately authenticated draft API endpoints.
Lower coupling simplifies maintenance and scaling under increasing traffic.
Design authentication and the live-preview pipeline carefully.
콘텐츠 API
An interface that delivers content from a headless CMS to the front end as JSON through REST or GraphQL.
토큰
The smallest unit of text processed by an AI model, which may be a word, character or subword fragment.
헤드리스 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.
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.