--- title: "Integrating a Third-Party DAM into Optimizely CMS 12: A Case Study" url: https://daily.dev/posts/integrating-a-third-party-dam-into-optimizely-cms-12-a-case-study-vb0p0wdhy source_url: https://techhub.iodigital.com/articles/optimizely-cms-third-party-dam-integration type: article source: "iO tech_hub" published: 2026-07-07T07:32:06.291Z updated: 2026-07-07T07:32:33.430Z tags: ["cms"] reading_time: 19 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Integrating a Third-Party DAM into Optimizely CMS 12: A Case Study **[iO tech\_hub](https://daily.dev/sources/iotechhub)** · 19 min read · 0 upvotes · 0 comments ## Summary A detailed case study on integrating a third-party DAM (Wedia) into Optimizely CMS 12 without official documentation. The author walks through the full research process — decompiling the CMP NuGet package, studying CMS.zip internals, and using Geta's Categories package as a blueprint. The solution involves four key patterns: configuring module.config for Dojo, extending ContentReferenceEditor (not replacing it) with a custom Dojo widget, using postMessage to bridge the DAM iframe picker with the CMS field editor, and creating proxy content items (WediaImage/WediaVideo) via a REST endpoint so picked assets become native CMS ContentReferences. A custom Assets pane tab with 'For All Sites' and 'For This Site' roots completes the integration, enabling editors to browse and reuse DAM assets like native media. Code samples are provided for all major components including C# descriptors, Dojo JavaScript, and the proxy content API controller. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: --- Tags: [#cms](https://daily.dev/tags/cms) [View this post on daily.dev](https://daily.dev/posts/integrating-a-third-party-dam-into-optimizely-cms-12-a-case-study-vb0p0wdhy)