Glossary, CMS, PIM, DAM, AI and digital terms explained

Agentic CMS is a term that describes a CMS where AI agents are built in as a core part of the platform, not as an add-on. In an agentic CMS, AI can perform tasks for the editor: update content in bulk, quality-check pages, suggest new content based on data, and act on natural-language instructions. It is about moving from AI as a tool to AI as a colleague in content work.

CMS stands for Content Management System, a platform for creating, managing, and publishing digital content without writing code. There are traditional CMSs (like WordPress) and headless CMSs (like Contentful, Strife) that separate content from presentation. Modern headless CMSs offer everything from minimalist developer interfaces to rich visual editing experiences.

A headless CMS is an architecture where content and presentation are separated. The CMS manages your content and exposes it via an API, and a separate frontend displays the content. The benefit is freedom of technology, multichannel publishing, and better performance. The quality of the editor experience varies between platforms. The best modern headless CMSs offer rich visual editing experiences.

DXP stands for Digital Experience Platform, a broader platform than a CMS that manages the entire digital customer experience. Beyond content management, a DXP often includes personalization, A/B testing, customer data, e-commerce, and integrations. Optimizely is a typical example. DXPs are powerful but expensive and complex. Many organizations pay for features they never use.

Headless e-commerce means the e-commerce platform's backend (product catalog, cart, payment) is separated from the frontend (what the customer sees). Content is managed in a CMS, transactions in the e-commerce platform, and they are connected via APIs. The result: faster sites, a better customer experience, and the freedom to combine the best tool for each part.

Content operations platform is a term for platforms that manage not just content but the entire workflow around it: creation, review, approval, publishing, distribution, and analytics. It is the step beyond a traditional CMS. The focus is on streamlining how teams collaborate around content, not just where it is stored.

SaaS CMS (Software as a Service) means the CMS is delivered as a cloud service. You don't need to install, host, or maintain anything yourself. The provider handles infrastructure, updates, and security. You pay a subscription. Most modern headless CMSs (including Strife) are SaaS-based. The upside: no maintenance. The downside: you depend on the provider's infrastructure and roadmap.

Master data management is the discipline of ensuring an organization has a consistent, accurate, and complete set of core data for customers, products, suppliers, and locations. In a product context, MDM means the same product information is used everywhere: on the web, in e-commerce, with distributors, and in print. PIM is often the part of MDM that handles product data specifically.

Metadata is data about data. In a CMS context it is information that describes your content: titles, descriptions, tags, categories, publish dates, authors. In a PIM context, metadata describes a product's attributes: weight, material, color, certifications. Good metadata makes content searchable, filterable, and automatable.

PIM stands for Product Information Management. A system for collecting, structuring, and distributing product data. Technical specifications, descriptions, images, categories, and relationships. All in one place. Without PIM, product data lives in silos: ERP, Excel, folders, different systems. With PIM you have one source of truth that feeds web, e-commerce, distributors, and print.

A product catalog is a structured collection of all the products an organization offers, with descriptions, images, specifications, and prices. Digitally it is usually managed in a PIM system and published to web, e-commerce, and PDF catalogs. The challenge is keeping it consistent and up to date across all channels.

Taxonomy is how you organize and categorize content or products. In a CMS context it is about categories, tags, and hierarchies that make content navigable. In a PIM context it is about product categories, attribute groups, and relationships. A good taxonomy helps both editors and visitors find the right thing. A bad one means everything ends up under "Other".

Image optimization is the process of reducing image file size without losing visible quality, for faster load times and a better user experience. Modern systems handle this automatically: converting to efficient formats (WebP, AVIF), adapting size per device, and using smart cropping. In a CMS with an integrated DAM, this happens without the editor having to think about it.

CDN stands for Content Delivery Network, a network of servers that delivers your content (images, video, files) from the server closest to the visitor. The result: faster load times, no matter where in the world the visitor is. In a CMS context, images and media are often handled via a CDN automatically.

DAM stands for Digital Asset Management, a system for storing, organizing, and distributing digital assets such as images, video, documents, and graphics. A DAM gives you a central source for all visual material, with version control, searchability, and automatic image optimization. Instead of images in folders on a server or in a shared drive, you have everything in one place, searchable and always in the right format.

Agent-based AI means the AI doesn't just answer questions but actively performs tasks. In a CMS context, an AI agent can update every product page missing a meta description, find content not updated in six months, or create a campaign section based on a description. The difference from ordinary AI: an agent acts, it doesn't just analyze.

Generative AI is AI that creates new content (text, images, code, video) based on instructions (prompts). In a CMS context, generative AI is used to write drafts, translate, simplify text, generate product descriptions, and create page components. The value is not in replacing the editor but in accelerating the work: the AI does the heavy lifting, the editor reviews and refines.

MCP stands for Model Context Protocol, an open protocol that lets AI tools communicate with other systems. In a CMS context, MCP means AI assistants (like Claude) can work directly in your CMS: create pages, update content, fetch data, and perform tasks. It is the connection that turns AI into a colleague instead of a standalone tool.

A prompt is an instruction you give an AI model, a description of what you want. It can be anything from "write a product description for this pump" to "create a campaign section with three columns in our brand style". The quality of the prompt determines the quality of the result. In modern CMSs, editors can prompt new page components into existence without involving a developer.

A token is the smallest unit an AI model works with. It can be a word, part of a word, or a punctuation mark. When you send an instruction to an AI model, the number of tokens in both your question and the answer is counted. That is usually how AI services are priced. A rule of thumb: one English word is roughly 1.3 tokens. That means a page with 500 words uses around 650 tokens to read, plus more tokens to generate an answer.

RAG stands for Retrieval-Augmented Generation, a technique where AI fetches relevant information from a database or system before generating its answer. In a CMS context, it means the AI can search your existing content, your product data, or your documents and use it as the basis for suggestions. The result is more relevant and accurate than AI that just generates from its general knowledge.

Semantic search understands meaning and context, not just keywords. Instead of matching exact words, the search engine interprets what you mean. In a CMS context, it means editors can search for "that guide about returns" and find the right thing, and visitors can search in their own words instead of site jargon.

API stands for Application Programming Interface, an interface that lets different systems talk to each other. In a CMS context, the API is what lets your website, app, or other service fetch content from the CMS. A strong API is the foundation of headless architecture and what makes integrations with e-commerce platforms, CRM systems, and other tools possible.

API-first means a platform is built with its API at its core. All data and functionality is available via the API, which makes it possible to integrate with other systems, publish across multiple channels, and build your own frontends. In a CMS context, API-first means the content is not locked to a specific website but can be consumed by any service.

Backend is the part of a website or application the user doesn't see: the server, the database, the business logic. In a CMS context, the backend is the system that stores content, manages users, and exposes APIs. In a headless CMS, backend and frontend are completely separated, which gives greater freedom in how the frontend is built.

CLI stands for Command Line Interface, a text-based interface where you type commands instead of clicking in a graphical interface. In a CMS context, CLI is used by developers to set up projects, run deployments, and interact with the platform's API. Some modern CMSs also offer CLI-like interfaces for editors, where you can give instructions in text and let the platform perform the task.

Cloud native means a platform is designed from the ground up to run in the cloud, not an old on-premise product lifted onto a server. Cloud native systems scale automatically, update without downtime, and require no server infrastructure of your own. Most modern headless CMSs are cloud native, which means you avoid worrying about servers, backups, and scaling.

Composable architecture means you build your digital platform from specialized, interchangeable components instead of one monolithic all-in-one solution. CMS from one vendor, e-commerce from another, search from a third, all connected via APIs. The upside: you pick best-in-class for each part. The downside: more integrations to maintain.

A design system is a collection of reusable components, guidelines, and principles that ensure consistent design across an entire website or product family. In a CMS context, it means editors build pages from ready-made, approved components instead of designing from scratch. It delivers visual consistency and faster production.

Frontend is the part of a website the user sees and interacts with: HTML, CSS, JavaScript, the visual interface. In a headless CMS, the frontend is built separately with frameworks (React, Next.js, Vue) and fetches content via the CMS's API. That gives full control over design and performance.

MACH stands for Microservices, API-first, Cloud native, Headless. These are four principles that describe modern digital architecture. MACH-certified platforms follow all four. It is a framework that helps organizations choose technology that is flexible, scalable, and future-proof, instead of locking themselves into a monolithic vendor.

Microservices is an architecture where an application is built as a collection of small, independent services that communicate via APIs. The opposite of a monolithic architecture where everything is connected. In a CMS context, it means content management, image processing, search, and publishing can be separate services, which makes them easier to scale, update, and replace.

SDK stands for Software Development Kit, a package of tools, libraries, and documentation that makes it easier for developers to build integrations with a platform. In a CMS context, an SDK gives developers ready-made building blocks for fetching content, handling images, and authenticating users, without having to build everything from scratch against a raw API.

Staging is a test environment that mirrors the live site but is not public. Here new features, design, and content are tested before they go live. A good staging environment reduces the risk of errors reaching visitors and gives the team a chance to review changes in a realistic context.

Web components are a set of web standards that let you create reusable, encapsulated HTML elements. They work in all modern browsers without external frameworks. The advantage over framework-specific components (React, Vue, Angular) is that they have no external dependencies. If the framework you built with stops being maintained, you have to rebuild. Web components that follow web standards work for as long as browsers exist.

Web standards are the specifications that define how the web works: HTML, CSS, JavaScript, Web Components, and the APIs browsers support natively. They are developed by organizations like W3C and WHATWG. Building on web standards means you are not dependent on third-party frameworks that can become outdated or unmaintained. It is the difference between building on land you own and land you rent. Platforms that follow web standards avoid technical dead ends.

A webhook is a way for one system to automatically notify another system when something happens. In a CMS context: when an editor publishes a page, the CMS can use a webhook to trigger a rebuild of the frontend, send a message to Slack, or update an external system. It is the glue that makes systems react to events in real time.

Impact mapping is a method for connecting a web initiative to real business goals. Instead of listing features ("we need a blog"), you identify the effects you want to achieve ("we want 30% more potential customers to find us via search") and work backward to which features are needed. It prevents you from building things no one actually needs.

Information architecture (IA) is about how content is organized, structured, and named on a website. It includes navigation, page structure, categorization, and searchability. Good IA helps visitors find the right thing without thinking. Bad IA makes them give up and leave.

A requirements specification describes what a website should do, for whom, and with which technical prerequisites. It covers functional requirements (what the system should handle), non-functional requirements (performance, security, accessibility), and integrations. A clear spec reduces the risk of misunderstandings, cost overruns, and disappointments.

KPI stands for Key Performance Indicator, a metric that shows whether you are moving toward your goal. In a web context, KPIs can be visitor numbers, conversion rate, bounce rate, average session length, or number of leads generated. Without KPIs you don't know whether your site delivers results. You guess.

UX design (User Experience) is about designing digital products that work well for the user. In web projects it includes research, wireframes, prototypes, user testing, and iterative improvement. The goal is to make the visitor's journey, from landing to action, as frictionless as possible.

Web strategy is the plan that connects your website to your business goals. It answers: Which audiences do we want to reach? Which messages drive action? How do we measure success? A web strategy prevents the web from becoming a project without direction, and ensures the investment pays off.

A wireframe is a simplified sketch of a web page that shows structure and content hierarchy, without colors, images, or detailed design. It is the blueprint before the build. Wireframes are used early in web projects to quickly test and iterate on page structure and flows without getting stuck in design details.

A/B testing means showing two variants of the same page or element to different visitors and measuring which performs best. It can be different headlines, buttons, images, or whole page layouts. The goal is to make decisions based on data instead of gut feeling.

Content marketing is a strategy where you create and distribute valuable, relevant content to attract and retain a defined audience, and ultimately drive profitable customer action. Instead of selling directly, you build trust through knowledge. The page you are reading right now is an example.

Content operations (content ops) is about the processes, tools, and workflows needed to produce, manage, and distribute content efficiently. It is the difference between having a CMS and actually being able to use it productively in an organization with multiple editors, approval flows, and publishing channels.

CTA stands for Call to Action, a prompt for the visitor to do something: click a button, fill in a form, book a demo. A good CTA is clear, specific, and placed where the visitor is ready to act. A bad CTA is vague ("Read more").

Digital marketing is an umbrella term for all marketing that happens through digital channels: website, search engines, social media, email, apps, and digital ads. It includes SEO, content marketing, SEM, social media marketing, and marketing automation.

Conversion optimization (CRO, Conversion Rate Optimization) is about increasing the share of visitors who take a desired action on your website: buy, fill in a form, book a demo. It is done by testing and improving everything from page layout and headlines to load times and CTA placement. Better conversion means more results from the same traffic.

Lead generation is the process of attracting and capturing potential customers' interest and turning it into contact details you can work with. On the web it often happens through valuable content (guides, whitepapers, webinars) in exchange for an email address. Your CMS plays a central role: it is where you build the landing pages, forms, and content that drive leads.

Omnichannel means giving the customer a seamless experience regardless of which channel they use: web, app, store, customer service, social media. Same message, same brand, same data. In a CMS context, it is about publishing the same content to multiple channels from one source, which requires an API-first architecture.

SEO stands for Search Engine Optimization, the work of being visible in search results like Google. It is about creating relevant content, structuring it correctly (headings, meta descriptions, alt text), and building credibility (internal and external links). Your CMS affects SEO directly: a CMS with built-in SEO validation and fast load times gives you a head start.

Web analytics is about measuring, collecting, and analyzing data about visitors to your website: where they come from, what they do, how long they stay, and where they lose interest. Common tools are Google Analytics, OpenPanel, and Matomo. The insights drive better decisions about content, design, and marketing.

AEO stands for Answer Engine Optimization, optimizing for search services that give direct answers instead of a list of links. Think Google's AI Overviews, ChatGPT, Perplexity, and the like. While SEO is about ranking high in a list of links, AEO is about becoming the source the AI cites in its answer. It requires clearly structured content, authoritative sources, and content that answers questions directly.

AI Overviews is Google's feature that shows an AI-generated answer at the top of search results, above the traditional links. The answer is compiled from several sources. If your content is cited in an AI Overview, you get visibility without the user necessarily clicking through. It changes the rules of SEO: being cited can be as valuable as ranking in position one.

AI SEO is the adaptation of your SEO strategy for a world where AI services (ChatGPT, Perplexity, Google Gemini) are an important search channel alongside traditional search engines. It includes structuring content so AI models can understand and cite it, using schema markup, and creating authoritative content that AI services trust as a source.

GEO stands for Generative Engine Optimization, optimizing to appear in AI-generated answers. While SEO focuses on Google's traditional search results, GEO focuses on being cited by AI models like Google AI Overviews, ChatGPT, and Perplexity. Techniques include clear factual statements, structured data, an authoritative tone, and content that directly answers specific questions. GEO and SEO do not exclude each other, they complement each other.

A knowledge graph is a structured database of facts and relationships that search engines and AI services use to understand the world. Google's Knowledge Graph, for example, powers the info box shown next to search results. In a CMS context, you can influence how your organization is represented in knowledge graphs by using schema markup and structured data on your website.

Schema markup is code you add to your website that helps search engines and AI services understand what your content is about. It can describe that a page is an FAQ, that an organization has a certain phone number, or that a product has a certain price. Schema markup increases the chance that your content appears as rich snippets in Google and is cited by AI services.

Structured data is information organized in a standardized format that machines can read. Schema markup is the most common way to implement structured data on the web. As AI services become more important search sources, the value of structured data increases: it helps AI models understand, categorize, and cite your content correctly.

GDPR (General Data Protection Regulation) governs how personal data is handled within the EU. In a CMS context, it is about where your data is stored, who has access, and how personal data is processed. A CMS with European cloud infrastructure gives you better control and protects you from issues around the CLOUD Act, the US law that gives US authorities the right to request data from US cloud providers, regardless of where the data is stored.

WCAG (Web Content Accessibility Guidelines) are international guidelines for web accessibility. They ensure digital content is accessible to everyone, including people with disabilities. In Sweden, the DOS Act requires public organizations to meet WCAG 2.1 AA. But accessibility is not just a legal requirement, it is better UX for everyone. A CMS with built-in WCAG validation helps editors follow the guidelines without being specialists.