This blog post provides perspective on the term SDK, or Software Development Kit, as it is used in content management systems, specifically the Contentstack SaaS headless CMS.
This post is a member of the following glossary:
An SDK is a technology-specific programming library that allows developers to integrate with and customize existing software components.
As opposed to developing custom software that builds on and runs within the CMS itself, SDKs provide customer systems with access to existing CMS instances, repositories, and features. With decoupled and headless CMS, SDKs abstract the HTTPS APIs provided by the CMS for specific technologies such as JavaScript and .NET.
- CMS Glossary: API (Application Programming Interface) – Deliverystack.net
- Differences between Decoupled CMS and SaaS Headless CMS – Deliverystack.net
- Working with [Headless] [CMS] Vendor [.NET [Core]] SDKs – Deliverystack.net
- Whether to Use Vendor SDKs to Access Vendor Services – Deliverystack.net
- Why Isn’t This In the .NET SDK? – Deliverystack.net
While any client technologies could invoke their services, decoupling allow SDKs for any number of technologies. Headless CMS vendors typically provide SDKs to wrap their HTTPS APIs for a wide variety of technologies.
Deliverystack.net 
2 thoughts on “CMS Glossary: SDK”