Glossary

A detailed narrative that showcases how a specific customer achieved success using a product.

The role dedicated to managing the relationship with customers post-sale, ensuring renewal.

The high-cost work of creating bespoke functionality within a framework like Drupal.

The accumulation of excessive, unneeded data within a database, causing slow performance.

A set of policies and procedures that define how an institution's critical data is collected, stored, and protected.

Location where critical data is stored, a key legal concern.

A situation where essential data is isolated within one platform and cannot be accessed by others.

The practical value and usability of data collected by a digital platform.

A content structure where different departments manage their own localized content, requiring central governance.

A system design where the front-end and back-end are separated, allowing for design agility.

An approach where Drupal serves only as the Headless CMS back-end.

The plan to separate the front-end from the back-end to reduce risk.

Process of creating market interest and awareness.

A state where updating one component requires updating dozens of others in a complex sequence.

The difficult process of moving code changes to production in a complex ecosystem.

A comprehensive set of standards, reusable components, and documentation that ensures a consistent brand experience.