Ha Bui
Jul 6, 2022
  568
(6 votes)

CMS 12 Welcome Integration UI addon

Hi everyone, do you know about the great blogpost from Kate: CMS 12 integration with Welcome’s Digital Asset Management Librar (optimizely.com)

If not then I would suggest you please go throught that first to get overview of main purpose and user case of CMS 12 and Welcome DAM integration!

After reading but you still got struggling about: How to enable it in your template? then you are in right place. Here is detailed instruction for you:

Welcome DAM UI integration

This will describes standard setup that you need for a template site in order to able to use Optimizely DAM UI integration packages.

Prerequisites

  1. EPiServer.CMS.Core 12.8 or later
  2. EPiServer.CMS.UI 12.9 or later

Installation

Install from command line

$ dotnet add package EPiServer.CMS.WelcomeIntegration.UI

In `Startup.cs` add following line:

services.AddDAMUi();

Start your site and use!

Configuration Options

Customize option can be done via `application.json` under `EPiServer\Cms` section, now we are supporting:

{
  "DAMUi":{
    "Enabled":true,
    "Settings":{
      "Welcome":{
        "IconClass":"dijitNoIcon",
        "AvailableTypes":"episerver.core.imagedata",
        "StoreName":"episervercmsdamcontentcreation",
        "Endpoint":"https://app.welcomesoftware.com",
        "PathAndQuery":"/cloud/library-picker?assetTypes=image"
      }
    }
  }
}


Under "DAMUi", with Settings options then you can:
1. Change icon class so can use whatever icon you wants (default is "dijitNoIcon")
2. Change "AvailableTypes" so the new editor command only be added if it is (or inherited from) one of available type. (default is "episerver.core.imagedata" so all properties that allow an image to be added will have the new command)
3. Change store via "StoreName" so that you can customize server side code (with your new store) to add more your business logic into. (default is "episervercmsdamcontentcreation")
4. Change end point via "Endpoint" so that you can transform the root DAM domain for each environment you have (inte, preprod or prod) (default is "app.welcomesoftware.com")
5. Change path and query so that you can add default filter for the DAM library picker by image, video or all (default is "image")

Screenshots

From Welcome DAM... for ContentArea

From Welcome DAM... for ContentReference property with thumbnail editor

Popup open when click (Welcome DAM login is required for the 1st time)

After login then next time, library picker will be shown

Select your asset then click `Choose`, popup will be closed then content will be saved (thumbnail will display after a while)

Related topics

1. Configuration
2.EPiServer CMS configuration section
3.Addon Overview

Jul 06, 2022

Comments

Praful Jangid
Praful Jangid Jul 6, 2022 11:20 AM

Thanks for sharing, I didn't notice this post is already there in series to Kate's post on how to install and configure it. Great post!

Please login to comment.
Latest blogs
Dynamic Route in ASP.NET Core When MapDynamicControllerRoute Does Not Work

Background Creating one of the add-on for Optimizely I had to deal with challenge to register dynamically route for the API controller. Dynamic rou...

valdis | Sep 25, 2022 | Syndicated blog

404 Error on Static Assets Within an Optimizely plugin

Background With the move to CMS 12 and .NET 5/6, developers are now able to build Plugins and Extensions using Razor Class Libraries (RCL).  These...

Mark Stott | Sep 23, 2022

How to bypass the content creation view in Optimizely

Something that has come up a couple of times in the last few year is feedback from content editors about the editing view that comes up when creati...

Ynze | Sep 23, 2022 | Syndicated blog

Welcome to Optimizely World's New Tech Video Portal

Optimizely, leader in the digital experience realm, has become a wealth of world class SaaS products including Web Experimentation, Full Stack, B2B...

The Developer Marketing Team of Optimizely | Sep 22, 2022