@salesforce/b2c-tooling-sdk 2.2.0 → 2.3.0

package/data/guides/enrichment.json

@@ -5951,6 +5951,20 @@
       "SLAS authentication"
     ]
   },
+  "b2c-commerce/ucp-connect-third-party-oms": {
+    "summary": "Integrate a third-party Order Management System with B2C Commerce to manage orders outside the platform.",
+    "keywords": [
+      "OMS",
+      "order management system",
+      "third-party integration",
+      "connect OMS",
+      "external order management",
+      "order system integration",
+      "OMS integration",
+      "order fulfillment",
+      "third party order system"
+    ]
+  },
   "b2c-commerce/ucp-google-gmc-configuration": {
     "summary": "Set up Google as a commerce platform by completing UCP compliance, configuring Google Merchant Center feeds, and sharing checkout credentials for Gemini and AI Mode shopping.",
     "keywords": [
@@ -7912,6 +7926,765 @@
       "commerce API"
     ]
   },
+  "ocapi/apiexplorer": {
+    "summary": "Interactively explore, browse, and test Open Commerce APIs using the API Explorer tool with Swagger UI.",
+    "keywords": [
+      "API Explorer",
+      "OCAPI",
+      "Open Commerce API",
+      "Swagger UI",
+      "test APIs",
+      "browse APIs",
+      "API documentation",
+      "interactive exploration",
+      "meta API",
+      "Swagger 2.0",
+      "demo metadata",
+      "API testing tool"
+    ]
+  },
+  "ocapi/apiusage": {
+    "summary": "Learn how to use OCAPI including API exploration, batch requests, caching, CORS, customization, and optimization techniques.",
+    "keywords": [
+      "OCAPI usage",
+      "Open Commerce API",
+      "API Explorer",
+      "batch requests",
+      "OCAPI best practices",
+      "CORS",
+      "caching",
+      "client identification",
+      "expansions",
+      "custom properties",
+      "OCAPI customization",
+      "multipart requests"
+    ]
+  },
+  "ocapi/batchrequests": {
+    "summary": "Send up to 50 subrequests in a single multipart HTTP POST/OPTIONS request to reduce network overhead and API calls.",
+    "keywords": [
+      "OCAPI batch requests",
+      "multipart HTTP request",
+      "batch API",
+      "reduce network calls",
+      "subrequests",
+      "Content-Type multipart/mixed",
+      "batch endpoint",
+      "OCAPI batching",
+      "multiple API calls",
+      "request consolidation",
+      "OCAPI performance"
+    ]
+  },
+  "ocapi/bestpractices": {
+    "summary": "Learn OCAPI best practices for building scalable, high-performance applications, including caching behavior and request optimization strategies.",
+    "keywords": [
+      "OCAPI best practices",
+      "OCAPI performance",
+      "OCAPI vs controllers",
+      "OCAPI caching",
+      "application tier cache",
+      "OCAPI requests",
+      "request optimization",
+      "batch requests",
+      "thread behavior",
+      "payload size",
+      "scalable OCAPI",
+      "OCAPI tuning"
+    ]
+  },
+  "ocapi/caching": {
+    "summary": "Configure HTTP cache headers and max-age times for OCAPI Shop API resources to enable client and proxy caching.",
+    "keywords": [
+      "OCAPI caching",
+      "HTTP cache headers",
+      "max-age",
+      "cache control",
+      "Shop API caching",
+      "cache configuration",
+      "REST API caching",
+      "cache time settings",
+      "proxy cache",
+      "Business Manager cache",
+      "cache enablement",
+      "response caching"
+    ]
+  },
+  "ocapi/clientapplicationidentification": {
+    "summary": "Identify client applications to OCAPI by obtaining and including a client ID in every API request using tokens, parameters, or headers.",
+    "keywords": [
+      "OCAPI client ID",
+      "client application identification",
+      "Open Commerce API authentication",
+      "x-dw-client-id header",
+      "client_id parameter",
+      "Bearer token",
+      "JWT issuer claim",
+      "Account Manager API client",
+      "OCAPI authorization",
+      "API client registration"
+    ]
+  },
+  "ocapi/cors": {
+    "summary": "Enable browser-based cross-origin API requests securely using CORS headers and preflight mechanisms instead of same-origin policy restrictions.",
+    "keywords": [
+      "CORS",
+      "cross-origin resource sharing",
+      "cross-origin requests",
+      "XMLHttpRequest",
+      "preflight",
+      "HTTP headers",
+      "same origin policy",
+      "browser security",
+      "API access",
+      "credentials",
+      "OPTIONS request",
+      "JSONP alternative"
+    ]
+  },
+  "ocapi/customization": {
+    "summary": "Customize Shop API resources using before, after, and modifyResponse hooks to augment server-side logic with custom script code.",
+    "keywords": [
+      "OCAPI hooks",
+      "Shop API customization",
+      "before hooks",
+      "after hooks",
+      "modifyResponse",
+      "extension points",
+      "basket calculations",
+      "checkout customization",
+      "server-side logic",
+      "API resource modification",
+      "convenience hooks",
+      "OCAPI extensions"
+    ]
+  },
+  "ocapi/customproperties": {
+    "summary": "Set and read custom properties on OCAPI business objects using c_ prefix with supported value types across SHOP and DATA APIs.",
+    "keywords": [
+      "OCAPI custom properties",
+      "c_ prefix",
+      "custom properties OCAPI",
+      "business object properties",
+      "OCAPI value types",
+      "SHOP API custom properties",
+      "DATA API custom properties",
+      "input output documents",
+      "OCAPI hooks",
+      "modify hooks",
+      "custom fields OCAPI"
+    ]
+  },
+  "ocapi/dataformats": {
+    "summary": "Learn how to specify JSON or XML data formats for OCAPI requests using URL parameters and HTTP headers.",
+    "keywords": [
+      "OCAPI data formats",
+      "JSON XML",
+      "content-type header",
+      "format parameter",
+      "REST API formats",
+      "OCAPI request formats",
+      "HTTP content negotiation",
+      "API response format",
+      "application/json",
+      "application/xml"
+    ]
+  },
+  "ocapi/exceptions": {
+    "summary": "Reference for all OCAPI global exceptions with status codes, types, arguments, and descriptions for error handling.",
+    "keywords": [
+      "OCAPI exceptions",
+      "global exceptions",
+      "error handling",
+      "status codes",
+      "BodyDecodingException",
+      "EnumConstraintViolationException",
+      "HookStatusException",
+      "InvalidClientIdException",
+      "HTTP method override",
+      "exception types",
+      "OCAPI errors"
+    ]
+  },
+  "ocapi/expansions": {
+    "summary": "Use OCAPI expand query parameter to include omitted subresource data in products and product_search API responses, reducing network traffic by default.",
+    "keywords": [
+      "OCAPI expansions",
+      "expand query parameter",
+      "products resource",
+      "product_search",
+      "subresources",
+      "API response optimization",
+      "network traffic reduction",
+      "comma-separated expansion",
+      "products prices variations",
+      "OCAPI response filtering"
+    ]
+  },
+  "ocapi/exportdataunitsconfiguration": {
+    "summary": "Configure which data units to export from a B2C Commerce site by specifying catalogs, inventories, libraries, customer lists, and global data.",
+    "keywords": [
+      "ExportDataUnitsConfiguration",
+      "site export",
+      "data units",
+      "export configuration",
+      "catalogs export",
+      "inventory export",
+      "libraries export",
+      "customer lists export",
+      "global data export",
+      "OCAPI export",
+      "data export settings"
+    ]
+  },
+  "ocapi/exportglobaldataconfiguration": {
+    "summary": "Configure which global data units to export from a B2C Commerce instance using ExportGlobalDataConfiguration document properties.",
+    "keywords": [
+      "ExportGlobalDataConfiguration",
+      "global data export",
+      "export configuration",
+      "OCAPI",
+      "data export settings",
+      "global preferences export",
+      "custom types export",
+      "job schedules export",
+      "metadata export",
+      "instance configuration export",
+      "selective data export",
+      "export options"
+    ]
+  },
+  "ocapi/exportsitesconfiguration": {
+    "summary": "Configure which site-specific data units to export using boolean properties in the ExportSitesConfiguration document.",
+    "keywords": [
+      "ExportSitesConfiguration",
+      "site export configuration",
+      "export data units",
+      "site data export",
+      "OCAPI export",
+      "site configuration export",
+      "export settings",
+      "site backup",
+      "data export document",
+      "site preferences export"
+    ]
+  },
+  "ocapi/filtering": {
+    "summary": "Filter OCAPI resource instances by specifying parameters like type and direction to reduce result sets.",
+    "keywords": [
+      "OCAPI filtering",
+      "filter parameters",
+      "resource filtering",
+      "OCAPI query",
+      "result set filtering",
+      "resource type filtering",
+      "relationship filtering",
+      "OCAPI REST",
+      "filter syntax",
+      "cross_sell filter"
+    ]
+  },
+  "ocapi/flash": {
+    "summary": "Use OCAPI Flash property to store special document information like basket submission errors and unavailable products.",
+    "keywords": [
+      "OCAPI Flash",
+      "basket flash",
+      "document property",
+      "addFlash",
+      "removeFlash",
+      "getFlashes",
+      "basket submission",
+      "product unavailable",
+      "flash messages",
+      "scripting API",
+      "basket errors",
+      "flash paths"
+    ]
+  },
+  "ocapi/get-started-with-ocapi": {
+    "summary": "Learn how to access B2C Commerce resources using OCAPI with HTTP requests, including Shop API, Data API, and Meta API fundamentals.",
+    "keywords": [
+      "OCAPI",
+      "Open Commerce API",
+      "REST API",
+      "Shop API",
+      "Data API",
+      "Meta API",
+      "HTTP requests",
+      "client ID",
+      "API authentication",
+      "get started",
+      "API setup",
+      "commerce resources"
+    ]
+  },
+  "ocapi/globaljobs": {
+    "summary": "Execute global jobs to build search indexes for active data and content across B2C Commerce sites using OCAPI.",
+    "keywords": [
+      "global jobs",
+      "search index update",
+      "active data index",
+      "content index",
+      "job execution",
+      "OCAPI jobs",
+      "sfcc-search-index",
+      "site scope",
+      "index building",
+      "SearchIndexUpdateConfiguration",
+      "JobExecution",
+      "full index update"
+    ]
+  },
+  "ocapi/hookcircuitbreaker": {
+    "summary": "Manage hook stability and prevent cascading failures using the Circuit Breaker feature that tracks failed hook executions and returns 503 errors.",
+    "keywords": [
+      "hook circuit breaker",
+      "OCAPI hooks",
+      "hook failures",
+      "503 service unavailable",
+      "extension point",
+      "HookCircuitBreakerException",
+      "circuit breaker states",
+      "hook monitoring",
+      "hook troubleshooting",
+      "hook rate limiting",
+      "HookInvocationException",
+      "half-open state"
+    ]
+  },
+  "ocapi/hooks-data": {
+    "summary": "Execute custom logic after content asset creation, deletion, or update operations via OCAPI Data API hooks in version 24.5.",
+    "keywords": [
+      "OCAPI hooks",
+      "Data API",
+      "content hooks",
+      "afterCreate",
+      "afterDelete",
+      "afterUpdate",
+      "content asset",
+      "lifecycle hooks",
+      "dw.ocapi.data.content",
+      "trigger actions",
+      "API callbacks"
+    ]
+  },
+  "ocapi/hooks-shop": {
+    "summary": "Intercept and customize customer authentication in Shop API using OCAPI hooks before and after POST /customers/auth requests.",
+    "keywords": [
+      "OCAPI hooks",
+      "Shop API authentication",
+      "beforePOST",
+      "afterPOST",
+      "customer auth",
+      "/customers/auth",
+      "auth hooks",
+      "authentication lifecycle",
+      "guest login refresh",
+      "authorization header",
+      "hook execution"
+    ]
+  },
+  "ocapi/http-headers": {
+    "summary": "Reference guide to OCAPI global HTTP headers for requests and responses, including CORS and character encoding.",
+    "keywords": [
+      "OCAPI headers",
+      "HTTP headers",
+      "CORS headers",
+      "Accept-Charset",
+      "Access-Control-Allow",
+      "request headers",
+      "response headers",
+      "OCAPI reference",
+      "cross-origin",
+      "preflight request",
+      "HTTP standards"
+    ]
+  },
+  "ocapi/httpmethods": {
+    "summary": "Learn how OCAPI supports RESTful HTTP methods (GET, DELETE, PUT) for retrieving, removing, and managing resources with proper status codes.",
+    "keywords": [
+      "HTTP methods",
+      "OCAPI",
+      "REST API",
+      "GET",
+      "DELETE",
+      "PUT",
+      "RESTful",
+      "status codes",
+      "RFC 2616",
+      "resource management",
+      "idempotent"
+    ]
+  },
+  "ocapi/httpstatuscodesandfaults": {
+    "summary": "Understand OCAPI HTTP status codes and fault documents for handling errors in Open Commerce API requests.",
+    "keywords": [
+      "OCAPI HTTP status codes",
+      "API error handling",
+      "fault documents",
+      "400 Bad Request",
+      "401 Unauthorized",
+      "404 Not Found",
+      "500 Internal Server Error",
+      "HTTP response codes",
+      "Open Commerce API errors",
+      "REST API status codes",
+      "OCAPI faults",
+      "error responses"
+    ]
+  },
+  "ocapi/httpversions": {
+    "summary": "OCAPI supports HTTP/1.1 (case-insensitive headers) and HTTP/2 (lowercase headers required) with format differences and availability by instance type.",
+    "keywords": [
+      "HTTP versions",
+      "HTTP/1.1",
+      "HTTP/2",
+      "OCAPI",
+      "header names",
+      "case-insensitive",
+      "lowercase headers",
+      "instance group",
+      "production staging development",
+      "ODS sandbox",
+      "RFC 7540",
+      "RFC 2616"
+    ]
+  },
+  "ocapi/images": {
+    "summary": "OCAPI returns image URLs through the Shop API as absolute URLs for product and content images.",
+    "keywords": [
+      "OCAPI images",
+      "Shop API",
+      "image URLs",
+      "absolute URLs",
+      "Open Commerce API",
+      "product images",
+      "image endpoints",
+      "OCAPI Shop",
+      "content images",
+      "image resources"
+    ]
+  },
+  "ocapi/jsonp": {
+    "summary": "Use OCAPI's callback parameter to enable JSONP responses for cross-domain browser requests with wrapped JSON data.",
+    "keywords": [
+      "OCAPI JSONP",
+      "JSON with padding",
+      "callback parameter",
+      "cross-domain requests",
+      "JSONP",
+      "browser JavaScript",
+      "cross-origin",
+      "API response format",
+      "wrapped JSON",
+      "Open Commerce API"
+    ]
+  },
+  "ocapi/jwt": {
+    "summary": "Use JWT authentication with OCAPI Shop API resources by obtaining tokens via /customers/auth or /customers/auth/trustedsystem endpoints after registering your client application.",
+    "keywords": [
+      "OCAPI JWT",
+      "JSON Web Token authentication",
+      "Shop API",
+      "customer auth",
+      "/customers/auth",
+      "OAuth token",
+      "client ID",
+      "trusted system",
+      "API authentication",
+      "OCAPI security",
+      "JWT token",
+      "Account Manager registration"
+    ]
+  },
+  "ocapi/localization": {
+    "summary": "Learn how to request localized content in OCAPI Shop API and Data API using locale parameters and fallback behavior.",
+    "keywords": [
+      "OCAPI localization",
+      "locale parameter",
+      "Shop API locale",
+      "Data API locale",
+      "language code country code",
+      "locale fallback",
+      "localized content",
+      "multi-locale",
+      "language fallback",
+      "locale format",
+      "OCAPI internationalization"
+    ]
+  },
+  "ocapi/metadata": {
+    "summary": "Access OCAPI metadata to discover available APIs, versions, resources, and documents with OAuth authentication.",
+    "keywords": [
+      "OCAPI metadata",
+      "meta API",
+      "API discovery",
+      "available APIs",
+      "API versions",
+      "resource descriptions",
+      "OCAPI settings",
+      "OAuth token",
+      "metadata caching",
+      "API documentation",
+      "Shop API metadata",
+      "Data API metadata"
+    ]
+  },
+  "ocapi/oauth": {
+    "summary": "Authenticate OCAPI requests using OAuth 2.0 with client credentials grant or Business Manager user grant based on server-to-server or user interaction scenarios.",
+    "keywords": [
+      "OCAPI OAuth 2.0",
+      "OAuth authentication",
+      "client credentials grant",
+      "Business Manager user grant",
+      "Data API authentication",
+      "Shop API authentication",
+      "server-to-server OAuth",
+      "OCAPI authorization",
+      "OAuth 2.0 protocol",
+      "API access control"
+    ]
+  },
+  "ocapi/ocapi-api-doc": {
+    "summary": "Reference documentation for OCAPI Shop API and Data API endpoints for B2C Commerce development.",
+    "keywords": [
+      "OCAPI",
+      "Shop API",
+      "Data API",
+      "API reference",
+      "B2C Commerce",
+      "REST API",
+      "commerce API",
+      "OCAPI endpoints",
+      "API documentation",
+      "commerce endpoints"
+    ]
+  },
+  "ocapi/ocapisettings": {
+    "summary": "Configure OCAPI settings in Business Manager to manage client permissions, caching, and API behavior across sites or globally.",
+    "keywords": [
+      "OCAPI settings",
+      "configure OCAPI",
+      "Business Manager OCAPI",
+      "client permissions",
+      "OCAPI caching",
+      "global settings",
+      "site-specific settings",
+      "Open Commerce API",
+      "API configuration",
+      "OCAPI deprecation",
+      "SCAPI migration",
+      "JSON configuration"
+    ]
+  },
+  "ocapi/opencommerceapi": {
+    "summary": "RESTful API with Shop, Data, and Meta components for accessing Commerce Cloud Digital storefront and configuration functionality.",
+    "keywords": [
+      "Open Commerce API",
+      "OCAPI",
+      "REST API",
+      "Shop API",
+      "Data API",
+      "Meta API",
+      "Commerce Cloud Digital",
+      "storefront API",
+      "B2C Commerce API",
+      "API components",
+      "REST endpoints",
+      "commerce integration"
+    ]
+  },
+  "ocapi/optimisticlocking": {
+    "summary": "Understand OCAPI's two-level optimistic locking mechanism for preventing concurrent modification conflicts and handling HTTP 409 errors.",
+    "keywords": [
+      "optimistic locking",
+      "OCAPI",
+      "concurrent modification",
+      "HTTP 409",
+      "ConcurrentModificationException",
+      "data consistency",
+      "lost update problem",
+      "retry logic",
+      "conflict resolution",
+      "Commerce Cloud Digital"
+    ]
+  },
+  "ocapi/pagination": {
+    "summary": "Configure OCAPI pagination using start and count parameters to retrieve API collection data in manageable chunks with navigation links.",
+    "keywords": [
+      "OCAPI pagination",
+      "start parameter",
+      "count parameter",
+      "API paging",
+      "collection pagination",
+      "Open Commerce API",
+      "paginate results",
+      "next previous links",
+      "resource chunks",
+      "API response paging",
+      "pagination parameters",
+      "offset limit"
+    ]
+  },
+  "ocapi/propertyselection": {
+    "summary": "Use property selectors with the select parameter to reduce API response size by retrieving only needed resource properties.",
+    "keywords": [
+      "property selection",
+      "select parameter",
+      "OCAPI",
+      "resource properties",
+      "bandwidth optimization",
+      "property selectors",
+      "API filtering",
+      "complex properties",
+      "child document properties",
+      "array indexing",
+      "filter expression"
+    ]
+  },
+  "ocapi/queries": {
+    "summary": "Use queries to selectively retrieve OCAPI data with match_all, term, text, boolean, and filtered query types to reduce bandwidth.",
+    "keywords": [
+      "OCAPI queries",
+      "query types",
+      "match_all_query",
+      "term_query",
+      "text_query",
+      "boolean_query",
+      "filtered_query",
+      "data filtering",
+      "search criteria",
+      "record selection",
+      "query syntax",
+      "OCAPI data retrieval"
+    ]
+  },
+  "ocapi/resourcestates": {
+    "summary": "Implement optimistic locking in OCAPI clients using resource state tokens to prevent concurrent update collisions.",
+    "keywords": [
+      "resource state",
+      "OCAPI resource state",
+      "optimistic locking",
+      "_resource_state",
+      "x-dw-resource-state",
+      "concurrency control",
+      "lost update problem",
+      "ETag alternative",
+      "collision prevention",
+      "resource state header",
+      "OCAPI locking"
+    ]
+  },
+  "ocapi/searchindexupdateconfiguration": {
+    "summary": "Configure search index update settings with site scope properties for B2C Commerce OCAPI.",
+    "keywords": [
+      "search index update",
+      "SearchIndexUpdateConfiguration",
+      "site scope",
+      "search index configuration",
+      "OCAPI",
+      "index settings",
+      "search configuration",
+      "index update",
+      "site_scope",
+      "search indexing"
+    ]
+  },
+  "ocapi/sessionbridge": {
+    "summary": "Enable seamless authentication between OCAPI and session-based storefronts by exchanging JWTs and session cookies without reauthentication.",
+    "keywords": [
+      "OCAPI session bridge",
+      "JWT session exchange",
+      "dwsid cookie",
+      "customers/auth resource",
+      "/sessions resource",
+      "Authorization Bearer token",
+      "session authentication",
+      "OCAPI authentication",
+      "guest customer JWT",
+      "registered customer session",
+      "dwsecuretoken",
+      "seamless authentication"
+    ]
+  },
+  "ocapi/sitearchiveexportconfiguration": {
+    "summary": "Configure site archive export jobs by specifying data units, export file path, and overwrite settings for OCAPI system jobs.",
+    "keywords": [
+      "SiteArchiveExportConfiguration",
+      "site archive export",
+      "OCAPI document",
+      "export configuration",
+      "data units export",
+      "system job",
+      "export file",
+      "IMPEX",
+      "overwrite export",
+      "archive export setup"
+    ]
+  },
+  "ocapi/sitearchiveimportconfiguration": {
+    "summary": "Configure site archive import settings including file path and merge mode for system jobs.",
+    "keywords": [
+      "SiteArchiveImportConfiguration",
+      "site archive import",
+      "import configuration",
+      "system job import",
+      "file_name property",
+      "merge mode",
+      "import mode",
+      "archive import setup",
+      "OCAPI import",
+      "site data import"
+    ]
+  },
+  "ocapi/systemjobs": {
+    "summary": "Trigger and monitor predefined OCAPI system jobs via background job requests with job status responses.",
+    "keywords": [
+      "OCAPI system jobs",
+      "background jobs",
+      "job status",
+      "OCAPI Data API",
+      "sfcc- prefix",
+      "system job request",
+      "job triggering",
+      "job monitoring",
+      "predefined jobs",
+      "job ID",
+      "OCAPI request"
+    ]
+  },
+  "ocapi/urlschema": {
+    "summary": "Learn how to construct OCAPI URLs using base URL and extended URL patterns for accessing Commerce Cloud API resources.",
+    "keywords": [
+      "OCAPI URL syntax",
+      "Open Commerce API URLs",
+      "base URL structure",
+      "extended URL patterns",
+      "OCAPI endpoints",
+      "Commerce Cloud API URLs",
+      "URL construction",
+      "API resource access",
+      "production instance URL",
+      "non-production instance URL",
+      "api_type",
+      "site_id"
+    ]
+  },
+  "ocapi/versioninganddeprecationpolicy": {
+    "summary": "Understand OCAPI versioning scheme, deprecation policy, and how version numbers are formatted in URLs and documents.",
+    "keywords": [
+      "OCAPI versioning",
+      "API deprecation policy",
+      "version numbers",
+      "API versioning strategy",
+      "OCAPI versions",
+      "version format",
+      "deprecated API versions",
+      "API version management",
+      "Commerce Cloud API versioning",
+      "version numbering scheme"
+    ]
+  },
   "pwa-kit-managed-runtime/active-data": {
     "summary": "Use Active Data in PWA Kit to collect shopper engagement and order metrics for merchandising rules and performance analysis.",
     "keywords": [
@@ -10194,6 +10967,23 @@
       "site-locale prefix"
     ]
   },
+  "sfnext/sfnext-hybrid-section": {
+    "summary": "Set up and deploy Storefront Next alongside existing SFRA or SiteGenesis storefronts using Hybrid Auth with routing and authentication.",
+    "keywords": [
+      "hybrid storefront",
+      "Storefront Next",
+      "SFRA",
+      "SiteGenesis",
+      "Hybrid Auth",
+      "go live",
+      "routing configuration",
+      "login registration hybrid",
+      "parallel deployment",
+      "storefront migration",
+      "authentication hybrid",
+      "multi-storefront setup"
+    ]
+  },
   "sfnext/sfnext-images": {
     "summary": "Optimize storefront images using Dynamic Imaging Service (DIS) and the DynamicImage component for responsive, format-converted, server-resized delivery.",
     "keywords": [