This page is a growing glossary of terms and acronyms used in technical writing, documentation, and related fields. It’s intended to help writers quickly identify unfamiliar language and understand how a term is being used in context.
You can search by acronym, term, context, or definition, or sort the table by term or acronym. Because many terms are used differently across industries and disciplines, context is included to help distinguish between similar or overlapping meanings.
To build and expand this glossary at scale, AI tools have been used to help generate and organize content. These tools are used carefully and reviewed, but they are not perfect. If you notice something that’s unclear, incorrect, or missing, your feedback is welcome.
If you know of a term or acronym that should be included, feel free to send it: admin@twi-net.org.
| Term ⬍ | Acronym ⬍ | Definition | Context |
|---|---|---|---|
| Accessibility | The practice of making content, interfaces, and products usable by as many people as possible, including people with disabilities. More info | ||
| Active Voice | A sentence structure where the subject performs the action. | ||
| Adaptive Content | Content that adjusts based on factors such as device, user behavior, location, or audience needs. | ||
| Agile | An iterative approach to work that emphasizes collaboration, flexibility, and continuous improvement. More info | ||
| Ambiguity | The presence of multiple possible meanings in a sentence, phrase, or concept. | ||
| Analytics | The collection and analysis of data used to measure performance, behavior, or outcomes. | ||
| Application Layer | The top layer of a system where user-facing applications operate. | ||
| Application Programming Interface | API | A set of rules that allows software systems to communicate with each other. More info | |
| Audience | The intended readers, users, or consumers of content. | ||
| Augmented Reality | AR | A technology that overlays digital elements onto the real-world environment. More info | |
| Authentication | The process of verifying the identity of a user or system. | ||
| Authorization | The process of determining what an authenticated user or system is allowed to do. | ||
| Back End | The part of a system responsible for data processing, storage, and server-side logic. | ||
| Backlog | A prioritized list of tasks, features, fixes, or work items waiting to be completed. | ||
| Backward Compatibility | The ability of a system to work with older versions, formats, or data. | ||
| Branch | A parallel line of development used to work on changes independently from other work. More info | ||
| Branching Strategy | A defined approach for organizing and managing branches in a repository. | ||
| Build | The process of generating output from source files, such as compiling documentation into a website. | ||
| Build Artifact | The output produced by a build process, such as compiled files or generated documentation. | ||
| Build Failure | An error that prevents a build process from completing successfully. | ||
| Build Trigger | An event that automatically starts a build process, such as a commit or pull request. | ||
| Call to Action | CTA | A prompt that encourages users to take a specific action. | |
| Cascading Style Sheets | CSS | A language used to describe the presentation and layout of web pages. More info | |
| Changelog | A record of changes made to a product, system, or project over time. | ||
| Clarity | The quality of being easy to understand and free of unnecessary confusion. | ||
| Commit | A saved change in a version-controlled project, usually recorded with a descriptive message. More info | ||
| Competitive Audit | An evaluation of competitor products, content, features, or experiences to identify strengths, weaknesses, and opportunities. | ||
| Component Content Management System | CCMS | A content management system designed to store, manage, and reuse content at the component or topic level. | |
| Conciseness | The practice of expressing ideas clearly using only the necessary words. | ||
| Conditional Content | Content that is included, excluded, or modified based on rules such as audience, product, or output type. | ||
| Conditional Text | Content that appears or is hidden based on specific publishing conditions or rules. | ||
| Consistency | The uniform use of terminology, formatting, structure, and style across content. | ||
| Content | Information presented in a form intended for people or systems to consume, use, or interact with. | ||
| Content Analysis | The process of evaluating content to identify patterns, quality, gaps, structure, or effectiveness. | ||
| Content Audit | A systematic review of content to evaluate quality, accuracy, usefulness, and performance. | ||
| Content Brief | A document that outlines the goals, audience, requirements, and direction for a piece of content. | ||
| Content Calendar | A schedule used to plan, organize, and track content creation and publication. | ||
| Content Chunking | The practice of breaking information into smaller, manageable pieces to improve readability and understanding. | ||
| Content Design | The practice of planning, structuring, and creating content around user needs and goals. | ||
| Content Engineering | The practice of designing content systems, models, workflows, and structures for scalable content delivery and reuse. | ||
| Content Experience | The overall experience a user has when interacting with content across channels, devices, or touchpoints. | ||
| Content Flow | The movement and progression of content through a user journey, workflow, or system. | ||
| Content Governance | The policies, roles, standards, and processes used to manage content across its lifecycle. | ||
| Content Inventory | A list of content assets, often including details such as location, ownership, format, and metadata. | ||
| Content Lifecycle | The stages content goes through from creation and maintenance to archiving or retirement. | ||
| Content Management | The process of creating, organizing, maintaining, and publishing content throughout its lifecycle. | ||
| Content Management System | CMS | A system used to create, manage, organize, and publish digital content. | |
| Content Matrix | A framework used to organize content by factors such as audience, format, channel, or purpose. | ||
| Content Migration | The process of moving content from one system, platform, or format to another. | ||
| Content Model | A representation of content types, elements, relationships, and structure within a system. | ||
| Content Optimization | The process of improving content to increase effectiveness, usability, discoverability, or performance. | ||
| Content Product | Content treated as a managed product with defined goals, audiences, ownership, and ongoing maintenance. | ||
| Content Quality Assurance | CQA | The process of reviewing and validating content for accuracy, consistency, usability, and quality. | |
| Content Reuse | The practice of using the same content in multiple locations, formats, or outputs. | ||
| Content Scorecard | A tool or framework used to evaluate content against defined quality or performance criteria. | ||
| Content Standard | A documented rule or guideline that defines how content should be created, structured, or maintained. | ||
| Content Strategy | The planning, creation, governance, and management of content to support user and business goals. | ||
| Content Type | A defined structure for a specific kind of content, including its fields, attributes, and purpose. | ||
| Continuous Delivery/Deployment | CD | Practices that automate the release process. Continuous Delivery prepares changes for release, while Continuous Deployment automatically releases them to production. | |
| Continuous Integration | CI | A practice where changes are automatically tested and integrated into a shared codebase. | |
| Controlled Vocabulary | A predefined set of approved terms used consistently to organize and describe content. | ||
| Conversion | A completed user action that fulfills a desired goal, such as a purchase, signup, or download. | ||
| Cookie | A small piece of data stored in a browser to remember information about a user or session. | ||
| Copy Editing | The process of correcting grammar, punctuation, spelling, clarity, and style in written content. | ||
| Customer Journey Map | A visual representation of the steps, interactions, and experiences a user has while engaging with a product, service, or organization. | ||
| Customer Support | Services and assistance provided to help users resolve issues and successfully use a product or service. | ||
| Digital Asset Management | DAM | The organization, storage, management, and distribution of digital assets such as images, videos, and documents. | |
| Darwin Information Typing Architecture | DITA | An XML-based standard for creating, organizing, reusing, and publishing technical documentation. More info | |
| Deployment | The process of making software, systems, or content available in an environment. | ||
| Deployment Pipeline | An automated workflow that moves code or content through stages such as testing, staging, and production. | ||
| Deprecated | A feature, function, or component that is no longer recommended and may be removed in the future. | ||
| Development | The process of designing, building, testing, and maintaining software or digital systems. | ||
| DevOps | A set of practices that combines software development and IT operations to improve collaboration, automation, and delivery speed. | ||
| Discoverability | The ease with which users can find or encounter content, features, or information. | ||
| DocBook | An XML-based markup language designed for writing technical documentation and books. More info | ||
| Docs-as-Code | An approach where documentation is created and managed using the same tools and workflows as software development. | ||
| Document | A written or digital piece of content created to communicate information. | ||
| Document Engineering | The design and management of document structures, workflows, and systems for creating and delivering information. | ||
| Documentation | Content created to explain, support, describe, or guide the use of a product, process, or system. | ||
| Documentation Process | The structured set of activities used to plan, create, review, publish, and maintain documentation. | ||
| Dynamic Content | Content that changes automatically based on data, user behavior, or system conditions. | ||
| Editing | The process of reviewing and improving content for accuracy, clarity, consistency, and quality. | ||
| Editorial Calendar | A schedule used to plan and manage content creation, review, and publication activities. | ||
| Endpoint | A specific URL where an API can access resources or perform actions. | ||
| Environment | A specific setup where software or content systems operate, such as development, staging, or production. | ||
| Error Message | A message that informs users about a problem and helps them recover from it. | ||
| Extensible Markup Language | XML | A markup language used to structure, store, and transport data. More info | |
| Faceted Taxonomy | A classification system that organizes content using multiple independent categories or attributes. | ||
| Feature Branch | A branch created to develop a specific feature, update, or change independently from the main branch. | ||
| Findability | The ease with which users can locate information or content. | ||
| Folksonomy | A user-generated system of categorization based on tags rather than predefined structures. | ||
| Front End | The part of a system that users interact with directly. | ||
| Gap Analysis | The process of identifying missing elements, weaknesses, or differences between the current state and desired goals. | ||
| Git | A distributed version control system used to track changes and collaborate on projects. More info | ||
| Globalization | The process of designing products, content, or systems to support multiple languages, regions, and cultures. | ||
| Governance | The policies, processes, roles, and standards used to guide and manage systems, content, or organizations. | ||
| Governance Model | A defined structure for how decisions, responsibilities, workflows, and standards are managed within an organization or system. | ||
| Heading Hierarchy | The organization of headings and subheadings to reflect the structure and importance of content. | ||
| Heuristics | General principles or rules of thumb used to evaluate usability and design effectiveness. | ||
| HyperText Markup Language | HTML | The standard markup language used to create and structure web pages. More info | |
| Hypertext Transfer Protocol | HTTP | A protocol used to transfer information between clients and servers on the web. More info | |
| Internationalization | i18n | The process of designing systems so they can be adapted to different languages and regions. | |
| Information Architecture | IA | The organization and structure of content to make information easier to find and understand. | |
| Information Visualization | The visual representation of information or data to improve understanding and communication. | ||
| Intelligent Content | Structured, reusable, and semantically meaningful content designed for automated processing and multichannel delivery. | ||
| Interaction Model | A framework describing how users interact with a system, interface, or product. | ||
| Internet of Things | IoT | A network of physical devices connected to the internet that can collect and exchange data. | |
| Jargon | Specialized language or terminology used by a particular group or profession. | ||
| JavaScript Object Notation | JSON | A text-based format used to exchange structured data between systems. More info | |
| Knowledge Base | KB | A centralized collection of information used to help users solve problems or learn about a product. | |
| Key Performance Indicator | KPI | A measurable value used to evaluate progress toward a goal or objective. | |
| Label | A word or phrase used to identify, categorize, or describe content, navigation, or interface elements. | ||
| Linter | A tool that analyzes content or code for errors, formatting issues, and style violations. | ||
| Linting | The automated checking of content or code for errors, formatting issues, or style violations. | ||
| Localization | The process of adapting content for a specific language, culture, or region. | ||
| Machine Translation | MT | The automated translation of text from one language to another using software or AI systems. | |
| Main Branch | The primary branch where stable code or content is maintained. | ||
| Markdown | A lightweight markup language used to format text with plain text syntax. More info | ||
| Merge | The process of combining changes from one branch into another. | ||
| Merge Conflict | A situation where changes cannot be merged automatically and must be resolved manually. | ||
| Merge Request | MR | A request to merge changes from one branch into another, similar to a pull request. | |
| Message Architecture | A structured framework that defines the priority and organization of key messages in content or communication. | ||
| Metadata | Data that describes other data and helps organize, find, manage, or classify content. | ||
| Modular Content | Content created in reusable, self-contained units that can be combined in different ways. | ||
| Multichannel | A strategy that delivers content or experiences across multiple channels or platforms. | ||
| Multidevice | Designed to function across multiple types of devices such as desktops, tablets, and smartphones. | ||
| Multilingual Search Engine Optimization | The practice of optimizing content for search engines across multiple languages and regions. | ||
| Navigation | The system that allows users to move through content, interfaces, or products. | ||
| Networking | The practice and systems used to connect devices and enable communication between them. | ||
| Omnichannel | A strategy that creates a connected and consistent user experience across multiple channels and touchpoints. | ||
| Ontology | A structured model that defines concepts and the relationships between them within a system or subject area. | ||
| Parallel Structure | The use of consistent grammatical forms in related content or lists. | ||
| Parametric Search | A search method that allows users to filter results using defined attributes or categories. | ||
| Passive Voice | A sentence structure where the subject receives the action instead of performing it. | ||
| Persona | A fictional representation of a target user based on research, behaviors, goals, and needs. | ||
| Personalization | The customization of content or experiences based on user data, behavior, preferences, or context. | ||
| Pipeline | An automated sequence of steps used to build, test, and deploy content or software. | ||
| Plain Language | Writing that is clear, concise, and easy for the intended audience to understand. More info | ||
| Plain Language Principle | A guideline emphasizing clarity, simplicity, and user understanding in communication. More info | ||
| Post-commit Hook | A script that runs automatically after a commit is completed. | ||
| Pre-commit Hook | A script that runs automatically before changes are committed. | ||
| Production | Prod | The live environment where users interact with a system or product. | |
| Progressive Disclosure | A technique that reveals information gradually to avoid overwhelming users. | ||
| Proofreading | The final review of content to identify and correct errors before publication. | ||
| Pull Request | PR | A request to merge changes from one branch into another in a version-controlled project. | |
| QR Code | QR | A machine-readable code that stores information such as URLs, text, or contact details. | |
| Qualitative Audit | An evaluation focused on the quality, usability, clarity, or effectiveness of content rather than numerical metrics. | ||
| RACI | RACI | A responsibility assignment framework identifying who is Responsible, Accountable, Consulted, and Informed for a task or process. | |
| RAITES Method | A framework used to organize procedural information into reusable content components such as requirements, actions, information, tips, examples, and support material. | ||
| Re-skin | The process of updating the visual appearance of a product, interface, or website without significantly changing its functionality. | ||
| Readability | The ease with which readers can understand written content. | ||
| Rebase | The process of moving or combining commits to maintain a cleaner project history. | ||
| Redirect | A method of automatically sending users or systems from one URL to another. | ||
| Redundancy | Unnecessary repetition of words, information, or ideas. | ||
| Release Notes | A summary of updates, changes, fixes, or new features included in a release. | ||
| Repository | Repo | A storage location for project files, revision history, and collaboration in version control systems. | |
| Request | A message sent by a client to ask a server for data, resources, or actions. | ||
| Requirements Matrix | A structured table used to track requirements, responsibilities, status, or compliance across a project. | ||
| Response | The data or result returned by a server after receiving a request. | ||
| Responsive Design | An approach to design that allows content and layouts to adapt to different screen sizes and devices. | ||
| Return on Investment | ROI | A measure used to evaluate the value or profitability gained from an investment. | |
| Revision | The process of improving content for clarity, structure, quality, or effectiveness. | ||
| Rollback | The process of reverting a system, deployment, or release to a previous version after a problem or failure. | ||
| ROT | ROT | An acronym for Redundant, Outdated, and Trivial content used to identify low-value information. | |
| Scannability | The ease with which users can quickly locate and understand information in content. | ||
| Schema | A blueprint that defines how data or content is organized and structured. | ||
| Search Engine Optimization | SEO | The practice of optimizing content to improve visibility in search engine results. | |
| Security | The protection of systems, data, and information from unauthorized access, damage, or misuse. | ||
| Semantic Versioning | SemVer | A versioning system that uses a structured numbering format to communicate the type and impact of changes. More info | |
| Standard Generalized Markup Language | SGML | A standard markup language used to define the structure and organization of documents. | |
| Single Sourcing | The practice of creating content once and reusing it across multiple outputs or formats. | ||
| Site Map | A visual or structured representation of the pages and organization of a website or system. | ||
| Subject Matter Expert | SME | An individual with specialized knowledge who provides expertise or information for content and documentation. | |
| Software Development Kit | SDK | A collection of tools, libraries, and resources used to build applications for a platform or system. More info | |
| Source Files | The original files used to create or generate published content or documentation. | ||
| Staging | A pre-production environment used for testing before release. | ||
| Static Site | A website composed of pre-generated files served without server-side processing. | ||
| Static Site Generator | SSG | A tool that builds websites from source files into pre-generated static pages. | |
| Status Code | A numerical code indicating the result of a request between a client and server. More info | ||
| Structured Authoring | An approach to writing that uses defined structures and reusable components to improve consistency and scalability. | ||
| Structured Content | Content organized using defined elements, rules, and relationships so it can be reused, managed, and processed consistently. | ||
| Structured Data | Data organized in a defined format that makes it easier for systems to process and interpret. | ||
| Style Guide | A set of standards for language, formatting, tone, terminology, and usage in content. | ||
| Style Sheet | A document that defines writing, formatting, and editorial rules for a project or publication. | ||
| Synonym Ring | A group of related terms treated as equivalent in a search or classification system. | ||
| Tag | A keyword or label assigned to content to improve organization, filtering, or searchability. | ||
| Tagging | The process of assigning keywords or labels to content for organization and retrieval. | ||
| Taxonomy | A structured classification system used to organize content into categories and relationships. | ||
| Technical Documentation | Documentation created to explain technical products, systems, processes, or workflows. | ||
| Terminology | The collection of terms and definitions used within a specific field, product, or subject area. | ||
| Terminology Management | The process of organizing, maintaining, and standardizing approved terms across content and languages. | ||
| Token | A piece of data used to represent authentication, authorization, or access permissions. | ||
| Topic-Based Authoring | An approach where content is written in self-contained topics rather than long linear documents. | ||
| Transactional Content Map | A framework that maps content to specific user tasks, interactions, or decision points. | ||
| Transclusion | The inclusion of content from one source into another location by reference rather than duplication. | ||
| Translation | The process of converting text from one language into another. | ||
| Translation Memory | TM | A database that stores previously translated text segments for reuse in future translations. | |
| User-Centered Design | UCD | An approach that focuses on user needs, behaviors, and goals throughout the design process. | |
| User Interface | UI | The visual and interactive elements through which users interact with a system or product. | |
| Uniform Resource Identifier | URI | A string used to identify a resource. URLs are one type of URI. | |
| Uniform Resource Locator | URL | The address used to locate a resource on the web. | |
| Unstructured Content | Content that does not follow a predefined structure or consistent format. | ||
| User Experience | UX | The overall experience a user has when interacting with a product, service, or system. | |
| User Flows | Visual or structured representations of the steps users take to complete tasks or navigate a system. | ||
| User Story | A short description of a feature or requirement written from the user's perspective. | ||
| UX Writing | The practice of creating interface content that helps users navigate and interact with products effectively. | ||
| Variable | A reusable placeholder used to insert changing values or content into documents or systems. | ||
| Version Control | A system for tracking and managing changes to files over time. | ||
| Versioning | The practice of assigning identifiers or numbers to track changes over time. | ||
| Voice and Tone | Voice is the consistent personality expressed in content, while tone changes depending on context or audience. | ||
| Wayfinding | The design of cues and structures that help users understand where they are and how to navigate content or systems. | ||
| Web | A system of interconnected digital resources accessed through browsers and internet technologies. | ||
| Web Content Accessibility Guidelines | WCAG | A set of international guidelines for making web content more accessible. More info | |
| Wireframe | A simplified visual layout used to plan the structure and functionality of a page or interface. | ||
| Writing | The process of creating written content to communicate ideas, information, or instructions. | ||
| YAML | A human-readable format commonly used for configuration files and structured data. More info |