Authoring in Edge Delivery Services

Transcript

Hello all, good morning, good afternoon, welcome. We have already 19 people here. We’ll wait a minute or two for everybody to join. And then start with the program.

Hello again, welcome and thank you for joining today’s session focused on authoring in Edge Delivery Services.

While people are still joining, we are slowly beginning.

My name is Michael Grob and I work in Adobe’s Ultimate Success team or about this a little bit later.

I’m going to go ahead and kick off our session today. First and foremost, thank you for your time and attendance today. Just to note that this session is being recorded and the link to the recording will be sent out to everyone who registered afterwards.

This live webinar is a listen only format, but do feel free to share any questions into the chat and Q&A pod.

Our team will answer as possible there and in addition we have reserved time to discuss questions that are surfaced at the end of the session.

We already have 31 people here. So while we wait for attendees to filter in, I wanted to let you know that we do have another session coming up this quarter that is open for you to attend as well. In a week, customer journey analytics will be the topic of the webinar. If this is something for you, scan the QR code. We will send out the link as well with the other material.

Okay. So I think most have joined. So I would say let’s continue.

Both Carolis and I are working for the ultimate success team.

What you see on this slide is the foundation of our ultimate success model which combines proactive strategic leadership with responsive technical support to help customers maximize value and maintain stability with their Adobe solutions. On the proactive side, we work hand in hand with our teams to align on a unified success plan, execute targeted accelerators and support your roadmap through expert led activities across technical health, strategic planning and event readiness. At the same time, we’re here to ensure rapid response when needed. Our responsive model includes dedicated support resources and subject matter experts who monitor, prioritize and resolve issues swiftly, whether it’s a P1 incident or ongoing incident analysis. Together, this approach ensures you’re not only covered for today’s needs but are continuously moving toward long-term success and value realization. So now without further ado, let’s roll the tape.

My name is Michael Grob. I’m a principal field engineer in Adobe’s ultimate success team. I’m a translator between technology and business, focusing since more than 20 years on Adobe Experience Manager and now as a subject matter expert for edge delivery services. When not working, I use Adobe’s tools for film and photography and often you can find me in a hockey stadium live streaming games.

Karolis, would you like to introduce yourself? Hi, everyone. I’m Karolis Kalenta. I’m a senior field engineer in Adobe’s ultimate success organization. I work as a technical architect, helping customers turn AAM and Adobe Experience Cloud into solutions that are not just well implemented but tightly aligned to their business goals. I spent over eight years in the AAM world from early CQ 5-6 days to AAM as a cloud service and edge delivery services across luxury brands and large-scale global enterprises.

And as a free time, I don’t actually use any Adobe products, but I very much enjoy working with everything to do with Adobe. So let’s continue on.

Thank you, Karolis.

And so let’s begin.

Edge delivery services is new uncharted territories. It feels a bit like the old wild west. So let me tell you the story of edge delivery services authoring and how it all begun once upon a time in the west.

There was a dusty town called Edgewill.

Edgewill is a small quiet outpost perched somewhere on the edge of the web, a place where the digital winds blow softly and time seems to pause. Solid, reliable, but unremarkable, it stands as a testament to the countless websites that came before, each built with care but fading gently into the background.

Here, stories settle like dust and every page whispers memories of what might have been, waiting for someone to breathe new life and meaning into the silence.

One day, edge delivery services rode into town.

In one swift night, everything changed.

Developers long resigned to slow progress, suddenly saw blazing fast sites with perfect lighthouse course, offering a speed they’d only dreamed of around campfires. Marketers realized they could author content without waiting on development cycles. No longer shackled by old town bureaucracy, they sparked new stories that had lain dormant and business leaders saw the chance to scale globally without performance penalties. A new gold rush began, bringing a few shady characters into town, two contestants fighting for control over the authors.

The first one to stride into this untamed territory was document-based authoring.

Document-based authoring allows you to create content using familiar tools, such as word processing documents or spreadsheets.

This content is then seamlessly integrated into edge delivery services.

The central concept here is that authors can concentrate on developing the content itself, while developers are responsible for organizing the structure and building the necessary blocks. By enabling content creation in tools that most users already know, we simplify the authoring experience and make it easier to deliver content efficiently through edge delivery.

The air burst with relief and the quiet excitement. Finally, the authors used tools they knew as well as the back of their hands, eyes fixed on their stories rather than the mechanics of some peculiar rattling editor.

Only a short time later, a new figure rode into town, Universal Editor with AM Sites.

The Universal Editor, when used with AM Sites, offers a visual and intuitive way to edit pages and components directly within AM Sites, while using the speedy publishing features of edge delivery services. It provides through what you see is what you get editing in an expandable framework that allows full control over the editing process. This approach enables marketers and content authors who work right on the page they are building, giving them immediate context and control over their content.

It was the best of both worlds, a chance for every creator to be both gunslinger and poet, where the old dust trails met the promise of the open sky.

So it happens what must happen. The town is too small for both. Tension hangs thick in the dry air, every soul in town holding their breath, knowing full well that, in the end, only one can ride out victorious.

But when the dust settles and the dwell looms in the afternoon haze, a lone silhouette appears on the horizon. The new sheriff rides into town, her arrival quite as a shadow, stirring as the promise of rain. No one knows her story. Legends trail her like dust in the wind. Some say she’s gone by many names, wandered many dark alleys. But right now, none of that matters. All that matters is she’s the fastest way to shape the stories of this town She will edit content with edge delivery services in seconds. Her badge is in silver, but it shines with the promise of simplicity and control.

The dwell still lingers, but with her arrival, it feels like the old ways have met their match and the future might begin. Her name? Document Authoring.

Document Authoring is the framework for managing and standardizing document-driven authoring within the Edge ecosystem. She brings governance, consistency and orchestration across authoring models.

This approach combines the rapid publishing capabilities of edge delivery services with the user-friendly and the experience of a simplified editor, enabling multiple editors to collaborate seamlessly.

Editors, writers and creators can finally breathe easy, knowing that document authoring is a place where stories are forged, governed and delivered with the steady hand of a legend.

What? The rules are the rules. Etched into the very dust and stone of Edgeville, not even the Sheriff, with all her legend and quiet power, can hold the wheels of fate once they begin to turn. Here in this frontier town, honor is more than a word. It’s the law of the land, written in the hearts of every soul who walks this street.

Thus it happens as it must at well.

The first round in this showdown is all about the ease of authoring. A test of speed, grit and determination on these untamed planes. The needs ring out as clear as a church bell at dawn.

As an author, I aim to create content quickly, releasing updates efficiently. I prefer an authoring platform that is straightforward, user-friendly and reliable.

This is about ease of use, time to market and onboarding a lot of new authors, fast.

In Edgeville, where every word carries the weight of legend, only a true authoring platform worthy of the frontier will do. And how do our brave contestants? Karolis will show you now.

Yes, so we’ll look at the first dual.

We’ll start from document-based authoring and we’ll take a look at a recording of the authoring. So here we have Google Drive. You can both connect Google Drive or SharePoint as you wish. And here what we have is just a simple text editor, nothing different from any text editing. You can see we have a couple of tables and here you can see some configurations. And this is more or less the way how you control components or nowadays we call them blocks. So here we have a couple of components. Here we have a cards component. Before that we saw columns component. You can see that each cards row is a specific card by itself. So each row expects a image and a little bit of text. Here we have some section metadata if we want to have a section for that part of the page to be styled a little bit differently. And then we have a little bit of metadata for the page itself.

So it works in different ways. We have default content. Here you see highlighting default content, which is considered basically hyperlinks, bold text, underscore or italic. So these default contents basically can be used in combination to basically invoke different behavior on edge delivery services. So a mechanism called auto blocking.

We can also use default content in nested context as like a zim and blocks. So here we’re basically adding a row. We’re showing how to add some text and we’re going to add a little bit of text here, change it to live demo.

And as well play around a little bit with what various ways of using default content.

So the way this default content gets interpreted is purely custom. We provide boilerplate solutions that can be used for inspiration. But overall, it’s really up to each customer to decide what they want to do. Should you have bold text, italic text and underlined text invoking some behavior or just bold text in a specific block? So the possibility is quite vast. Here we just put a picture. And here at the bottom right now we see a sidekick. So this sidekick is the connection for authors to push content to the preview page and eventually to the live page. Here we’re pushing it to preview. As you can see, you cannot push directly to the production site. So now, yes, we can see that our default content has been pushed. And here we can see that it’s a dot page. So the dot page means that it’s a preview site. So not yet live. It’s for authors to understand that they enjoy everything that they changed and they feel sound to publish it. And now we’re pushing it out to the production site.

Marked by the dot live. So, yes.

Here we can see that we have edited text and everything looks as it should. So let’s move on now to Universal Editor.

So here we see standard AEM as a cloud service setup. We’re opening a page in the Site Explorer.

And we’re going to basically edit an index page. So you can see it’s basically standard AEM.

However, from the moment when we click edit, we’re being forwarded to a cloud solution and Universal Editor is a cloud solution. So we’re being forwarded to the Universal Editor canvas. This canvas basically opens up the page and it provides the what you see, what you get editing or in shorter terms, WYSIWYG editing.

We have the possibility to select components. So again, these components, this setup specifically is actually a demo setup. Anyone can have it for free and you can explore it by yourself. But essentially this is a setup that allows us to just play around a little bit with components, show how component definition works. Here we can see some properties for this specific block to be edited in different styles. Again, custom code, purely custom behavior. This is not something set in stone. This is not set within certain limits available to be changed or to take inspiration from this code base itself.

The interesting part about this setup is that you actually get the codes with this setup. So you’re welcome to explore it as well. Here we have a asset selector to choose a different image for our hero.

And basically providing a very nice what you see, what you get editing experience. Again, another way of how to navigate through the content sometimes might not be too clear. So there is a clear content tree and the content tree basically allows us to see a little bit more relationships of how these blocks work. So we can see here that once we are selecting a section, we can add a vast majority of components. However, when we look at our cards component, we can only add cards component. Again, this is something configured through JSON configurations on a specific repository. Just to allow to control author behavior a little bit so that basically authors wouldn’t be adding hero components in the cards component. So very simple and plain.

Available with many different text editing as well, with rich text editing and possibilities to basically help authors choose what they want to choose better.

Yes, and of course we can publish, we can publish the preview. Again, Edge Delivery Services provides two tiers, preview and live. We always recommend pushing to preview before pushing to live, but in this case, it’s minor hiccup.

Let’s move on to document authoring. So document authoring in essence is a skimmed down text editor. In Google Docs or Microsoft Office, these features basically come, features come with these text editors quite vast and sometimes might feel a little bit cluttered. So what document authoring aims is just what you need for Edge Delivery Services. So a really good choice for customers who don’t want to use Google Drive or don’t want to use Microsoft Office, but still want to maintain that document authoring experience. And this is again, very simple, very basic, very similar to document based authoring. Block invocation is based on creating tables as well as different combinations of default content will provide different behaviors. We of course provide some boilerplate code for that to explore. But of course, some inspirations can take place and different results of different combinations of content can provide different stylings. And here we see how a columns component is being used in simple column one, column two, column zero.

And of course, the first row of every table is always a single cell. The cell basically identifies the component that is to be used and here we’re adding a section break as well, just to show that we can edit the section specifically with metadata. So again, that specific part of the page is going to be edited within the design styles provided for that code base. So in this case, some default editions there.

Publishing happens again with preview and live. First to preview, always, and then to live.

And here we have some representation. Again, boilerplate representation. This is something that you can get right now for free. No questions asked and yes, try it out by yourself. So that was the first dual. Over to you, Michael.

Thank you very much, Carolis.

So we have…

We have three parts. If your authors live in Word Google and Speed Matters, go document based. If you already run AMS sites and need governance at scale, choose Universal Editor. If you want the fastest way to create in Edge delivery services for new or lean sites, use Document Authoring.

The second round of… Hold on. Small problem with my windows. Again, the second round of this high stakes dual is where the real great shows. Here, it’s all about control, flexibility, and the unyielding pursuit of brand consistency. As a content creator, I seek a flexible user interface that lets me precisely manage my actions while maintaining brand consistency. All about control, flexibility, brand consistency.

Every click is a calculated draw. Every adjustment a mark of confidence. In this showdown, only those with the sharpest tools and the steadiest hands will prevail, forging legend in the lore of digital creation.

So I ask again, Carolis, how do our contestants do? Let’s take a look.

So flexibility, ease of use is always very relative. Some customers will enjoy working with text editing. So let’s start from Google Drive.

So everything that has to do with Google Drive for SharePoint, so that’s text editing, sharing the documents, that would be the choice of the product and that’s the product capability. So in this case, it’s Google Drive. Here, Google Drive allows us to copy a link and share it to whoever has it. We have some security limitations, again, using just Google. So it has nothing to do at this point with Edge delivery services, because this is just a content. So the content source is Google Drive. And with that comes all the security capabilities and all the mechanisms from Google itself. So if customers already use G-suit and use vast majority of Google products, definitely a good choice.

Scrolling around here, we have a very interesting point about the way stylings work. So here we change it to Comic Sans to show how this will be represented in the final page or in the preview page.

Here we’re also adding a little bit of, again, showing ease of use of just adding another row for the cards component, just adding another image to show that have just copy pasted there.

And copying a little bit of text. So something to pay attention here, the hyperlink. So you can see that there’s hyperlinks on each row of the columns component. And we will take a little bit of a look of how is that represented in the preview page.

So again, we’re using the sidekick, using the sidekick to preview it.

And right here at the top, we can see that our hyperlinks have different styles. So again, this is something that through the stylings of the code, you basically provide the behavior. And here we can see that the title is not actually Comic Sans because well, Comic Sans, I mean, yeah, use it to your own discretion. But here we have basically imposed H1 stylings, again, something that is provided through the Edge Delivery code base. And so that maybe certain design aspects wouldn’t degrade the site.

So now we’ll move on to Universal Editor.

In Universal Editor here, we basically sustain the AM authoring. So managing of the pages, how versioning works, how security works, how we’re sharing, giving access to different authors.

Yeah, possibility to edit certain parts of the page or certain components.

And here we’re opening the index page, allowing it to load. Again, this is a cloud application. So we’re actually moving to Universal Editor away from our instance and it’s opening the page through Universal Editor.

Clicking a rewards block right here through the content tree, showing the different nested blocks that are available within a given block. Again, something that can be limited to only this selection of blocks. So again, not to step away from the intended design and feel of the site. Here we have a vast majority of blocks that we can add because we’re actually on a section right now. So a section is something that we want to populate with. So we usually want to populate that with the vast majority of blocks. Therefore, we allow to have the full possibility of the block selection.

And we’re simply navigating, going through the different properties, showing, for example, cards work. Again, asset selector. The asset selector is again another story, very powerful, has many different integrations to dynamic media and very different other places to even more enhance the editing.

Right, changing the page and changing an image and we’re moving to document authoring.

So document authoring by far is the favorite for edge delivery services, purely because of the simplicity, purely because of the availability of bulk editions and the extensibility of it is quite great and is only going to get better.

Very much like document based authoring, except for without the Google Drive and the SharePoint features and functionality. Something a bit more simple uses Adobe IMS. So the security and providing different access to this document is basically going to be through the admin console. Here versioning is as well available.

And yeah, can be restored to any different version in the past. So back to you, Michael.

Thank you very much Karolis. I’ve just seen that our Q&A part is still empty. So don’t be shy. Nobody will get shot just for asking a question. Well, probably.

So, let’s move on.

Let’s count the hits, folks.

Each contender trading blows under the blazing sun, dust swirling with every move. If your authors need a very high degree of flexibility, choose document based authoring.

If visual editing and leveraging AM functionality is your thing, go with Universal Editor and AM sites. If you want to support multiple authors at the same time while being dependent on SharePoint or Google Docs, use Google Authoring.

No clear winners emerged from the standoff yet. The crowd holds its breath, waiting for the next decisive shot in this wild west showdown of content creation.

The third round will be the last round. Now everything counts.

This is about operations, governance and scale.

As an administrator, I need a system that can scale on demand, is straightforward to maintain and manage, and offers flexibility for developers. Or, in other, more common words, I need tools as reliable as a trusted steed and as adaptable as a seasoned ranch hand. Give me something that won’t break when the going gets tough and I’ll make sure our brand rides tall.

The dust settles, the horizon stretches wide, and those who’ve made it this far know this is where legends are made or broken.

Karelis, who will be such a legend? Let’s take a look. Let’s start from document-based authoring, our first contestant. So, document-based authoring runs with minimal resource usage. So, content to store SharePoint or Drive, something that you already use, considering you already use that. Governance is primarily managed through processes, as Office or Google with limited strict CMS control. So, no capabilities of multi-site management and maybe no bulk addition. Anything of that sort would have to be a custom implementation or custom addition.

It’s quite easily scalable for many authors, though managing sites and locales becomes a little bit challenging due to the lack of multi-site management capabilities.

With Universal Editor with AEM Sites, it’s a little bit of complex setup involving numerous components, but supported well-established operational tools. And I would say it’s a very good choice for customers that are used to AEM authoring, authors that are actually welcome to AEM authoring and enjoy the multi-site management capabilities that it provides.

Offers robust governance for Workforce, MSM, policies and comprehensive audit and compliance features. So, yeah, conventional AEM setups of permission matrices as well exist here and are basically respected. It’s built to support extensive multi-site and multi-local environments with the new engine of edge delivery services.

So, document authoring eliminates the need for SharePoint or Drive. So, it’s simpler than using AEM. So, we don’t have Google Drive, we don’t have SharePoint and we don’t actually have something that new customers think with AEM as a little bit too cluttered authoring experience. We just have a document where we control everything through tables and default content and a very skimmed down version of that. It offers integrated governance features that standard documents yet remains less complex than AEM.

As mentioned, it does provide less cluttered document editing, but it also provides many MSM capabilities and extensibilities to ensure multi-site, multi-local setups.

It efficiently supports numerous authors and multiple locales for DA’s project and locale management tools along with bulk editing capabilities and as well often, often underlooked extensibility possibilities. So, there’s also possibility to create your own extensions and more extensions are going to be added in the future.

Back to you, Michael.

Thank you very much, Karolis.

Out here in this digital frontier, each contender brings their own special firepower to the showdown. If external overhead is okay for you and you need minimal operations overhead by maximum author scale, document-based authoring is for you. If you need enterprise governance, multi-site scale or what you see is what you get editing, Universal Editor is the right choice.

If you need something in between, namely a governed, scalable authoring hub with its own governance, select document authoring.

So, when the sun’s hanging low and the stakes are high, it’s not just about who draws fastest. It’s about knowing what you’re made of and playing to your strength.

But wait, there’s a twist to the tail partner.

The town is big enough for us all, the sheriff declared.

True enough. Under the watchful eye of the sheriff, the editors, each as stubborn and skillful as a bronco rider, found their way to work together. They played to their strengths, shoring up the weaknesses of their neighbors, just like a posse working side by side under the white western sky.

So it came to pass that Edgewill, once a town of rivals and lone riders, became one of the most famous towns in the whole west. A place where teamwork and trust built legends that echoed from MISA to MISA. But how should that work? The barkeeper asked. Polishing a glass with hands, worn from years of stories.

Let me break it down for you. It’s actually pretty straightforward, the sheriff said.

On one side, we have document authoring, which is the modern approach to creating content in edge delivery services. It’s designed to make things easier for teams, supporting multiple authors and languages, thanks to its project and local management tools. Plus, you can handle lots of tasks at once, and everything is stored in its own repository, known as AuthorBus.

Now, when we look at Universal Editor with AMSites, it uses the classic AM repository and gives authors a familiar what you see is what you get experience. By the way, we’ve got a question about this. Why is it called Universal Editor with AMSites? Because it uses the AMSites repository and the AMSites site console functionality. We’ll come to that a bit later in a minute.

You might wonder, can authors get the advantages of Universal Editor with document authoring and AuthorBus? The answer is yes. By using a Universal Editor gateway and some clever JSON configuration, Universal Editor can also work with AuthorBus repositories, even side by side with document authoring, authoring the same page. This is a new feature, however, but it’s already ready for use in real world scenarios.

You can also bring your own content repository into the mix, like SharePoint or Google Drive, and use document-based authoring.

So all of these options can coexist, letting you take advantage of each one’s strength. And the best part, you can share your code and your designs across the different authoring methods. That way, you can choose what works best for your situation every time. And no matter which repository and authoring method you choose, you will have the advantage of publishing through Edge delivery services and therefore having lightning-fast websites with all of them.

So, quite cool, I think.

And from this moment on, the three authoring methods lived peacefully on the same systems and Edgeville became one of the content richest towns in the whole West. This is the moment to wrap up our story, to thank you for your attention, and to take care of your questions.

Fortunately, some questions arrived. So, first one from the chat by Fernando. Is it possible to define granular permission control in Universal Editor to limit authors to just edit specific block or only specific parts of a page? I can save that question.

So, yes, it is possible with this specific combination of Universal Editor and AEM sites. AEM sites, since that is the content source, it will maintain the access level control for those specific parts of the page. So, if you want to limit certain authors to, let’s say, not edit heroes or not edit navigations, then yes, that is a possibility. Even though Universal Editor is a cloud application, the way it persists data, it still abides the ACLs on AEM sites. So, yes, it is possible to have that.

Thank you.

Ilham asks, can I add the document authoring to an EDS website that is already in place with SharePoint? I can take that. Yes and no. Basically, if you go back to this slide, you see that if you have already document-based authoring, with SharePoint and Google Drive, you use a different repository than the authorables of document authoring.

But you use the same blocks, the same design, the same functionality you have implemented. So, it’s not that easy, just a few clicks, but you can do it. And in effect, some of our customers actually do this on purpose. So, they start implementation with the SharePoint or Google Drive at the beginning, so they can just ask their editors to write text down into their Word documents and give these to the developers and designers as a basis for their work so that they can test with actual content from day one on and at a later point in time, then set up the whole thing to get the document authoring in the author bus. So, yes, it’s possible, but it’s a little bit of effort.

Okay. So, next one.

Is it a thing to have a page delivered through the traditional AM and have parts of the content editable through Universal Editor? If I might take that as well.

Yes, you can have on the same AM sites different sites that use different technologies. So, you can have a site that is based on Universal Editor and Edge Delivery Services, and you can next to it have a site that runs on traditional AM publishing with page editor. So, you have to decide for each site how you want to publish stuff, but you can, through your CDN, combine these two sites under the same domain. So that, for example, your existing website where you have all your product information and or your services that you offer, still having been delivered in the traditional way and adding a new section to this site, for example, a blog or a magazine style part where you use Universal Editor and Edge Delivery Services. So, here again, yes and no. Technically, it’s still two different sites, but you can have to run them in parallel on the same environment. I hope this answers the question.

So, next one. If EDS approach is selected for a content website and after some time business wants to integrate with third party APIs or session transactions, how it could be approached? Does it mean the website will have to be rewritten or full stack approach? You can try to take this. Yes, please.

So, if an EDS approach is selected for a content site and after some time business wants to integrate third party.

So, it really depends what’s the starting point. Does it mean the website has to be rewritten to full stack approach? So, actually full stack approach, there’s not much full stack that happens in AEM as it happens in Edge Delivery Services.

It’s mostly client-side rendering, basically. So, if you are to add third party APIs, let’s say you choose document-based authoring or document authoring, then that would be a client-side implementation. So, not too different from client-side rendered applications like React.

The difference here is that EDS is, yeah, it’s recommended to use it VanillaJS and Vanilla CSS and avoid frameworks, but overall, yeah, that’s not really too much of a headache as much as it would be to just make a feature for it. But you’re welcome to clarify your question if I didn’t answer that, but I think it should be fine.

Okay, thank you. Then next one, can you have Universal Editor with EDS or does it only work with AEM sites? That’s the one that I’m a little confused on the second column naming. Yeah, I’m sorry about that. I tried to answer this already during the presentation. So, basically all of these methods use EDS as the publishing method, right? And basically how the site is implemented from a technical point of view. And we just mentioned Universal Editor with AEM sites to mention that the repository that’s behind is the AEM sites repository and that you basically build it on top of AEM sites, but it still uses edge delivery services. So, again, to go back to this slide here, it uses the AEM sites repository and site console’s functionality, but uses the publishing part and the website design and the whole implementation part of edge delivery services.

Okay, I hope this becomes clear as well. I know we have a little bit, it’s not the easiest product names to compare.

This is basically because everything changes so fast all the time and names that are current today might not be tomorrow. Good, next one.

We piloted with doc-based authoring on SharePoint for our corporate comms team and the dream is real. I hope it was a good dream. We will migrate our soundstar.com websites, 50 websites, to edge using Universal Editor for multi-site management. So probably not a question, but more a statement. So basically what they did is they started here and now they’re doing this. So cool thing. Want to know more about it.

Okay, next one. Can this record be shared with clients or is it strictly internal? Yes, I think it can be shared with clients. Frankly, I don’t know. We have clients here, so they can download it. So, yes, why not? It will be shared. Yes, it has already been answered.

Next one. If we currently have document-based authoring and want to implement Universal Editor, it sounds like we must first transition to document authoring, correct? No. Please share more of the journey that will be required to move from document-based authoring to Universal Editor.

So there are two things that need to be done. One is basically the configuration of the Universal Editor itself and one is basically the migration of the content.

So as you see here, the design, functionality, everything you’ve implemented, basically the blocks and the design of the system, you can use for both approaches. For Universal Editor, you need to create a few additional JSON config files, but this isn’t a big deal. To migrate the content itself, it gets a bit more complicated. So basically, if you just want to use the same site structure and create a new site, that’s basically quite easy. If you want to take over content from your SharePoint or Google Drive to the AM sites, this gets a bit more complicated. Karolis, do you want to add something to that? No, I think you nailed it. Code-based stays the same. Content just has to be moved to document authoring in order to have that persistence, basically. But not too much of an effort then moving from any other site into document authoring. I think it’s relatively easy.

Then we have another question. Is it feasible, advisable to have a section of the same website in publisher-based tech? I assume you mean the old AM sites technology. And another section in EDS. For example, home and about as traditional dispatcher publisher, but the blog section as EDS. Yes.

You can do that. It’s more or less what I tried to answer a few questions ago. You still will have two different sites, but you can basically bring them together with some CDN magic. That’s exactly what you have written here in your question. You will be able to do so. You can basically do with whatever flavor of edge delivery service you want to be. Document authoring, Universal Editor AM sites. That would probably be the one you want to use when you already have an AM site. Or you could use document-based authoring as well. Okay. Can we edit pages interchangeably between Universal Editor and document authoring? Yes, you can. Since a few weeks. I’m not sure if the documentation is out there yet. It is. It is. Okay. Thank you. This is a completely new feature that’s available since a week or two. That’s why I had to update my slides again.

But basically, yes, this is now possible. But it’s new release technology. You might run into one or the other challenge while trying to do it.

Okay. Absolutely share. Customers should get to know the benefits of this.

I think there’s one question. There’s one question before that. What are the biggest challenges to change from doc-based authoring to Universal Editor? Michael? I can take it. No problem. I think it depends on what level. If you look at it from a developer point of view, I think that’s what you want to answer, Carolis. Or you want to look at it from a more business point of view. The business point of view would be you change your complete environment. And while document-based, you use SharePoint and you use Word, basically something that your authors probably know quite well, you move to AM. If your authors are used to AM, no problem with that. But for certain customers, that would be a known goal. To train every author to use AM and the AM authoring and Universal Editor because it’s a little bit of a learning curve. But if you have that already, no problem with that. The whole administrative stuff is more or less comparable.

So either you have to set up all your, for example, governance in SharePoint or in AM. So it doesn’t matter. And from a developer point of view, Carolis? From a developer point of view, well, there’s not much to be honest. The code base is more or less the same. You would have to use some additional JSON configuration for what we call Universal Editor instrumentation. Again, to limit certain components that, for example, cards components can only receive cards and such as that. But yeah, the effort from a developer perspective, if you’re already on document-based, it’s very minimal.

Okay, so I think this is the last question. In your experience, has anyone done a huge jump from on-prem AM implementation to edge delivery services with Universal Editor based delivery through complex migration? If so, what are some things to be mindful of? Yes, I know that from my personal experience, I did a launch advisory, one of the services that Ultimate Success offers.

We accompanied one customer who did exactly this. So they went from on-prem AM to edge delivery services with Universal Editor while doing a redesign of the whole website. So basically, they implemented the website from scratch in edge delivery services. It was a steep learning curve for everybody involved, we can say that. But in the end, it worked. And we were able to do some automated migration. So migration is one of the things that you have to be careful about this. And I personally would do an on-prem AM implementation.

Sorry, a migration from on-prem AM to edge delivery services at the moment when you want to have a site redesign anyway. When you change your information architecture, simplify your website, you now have 100,000 custom components. Remove them 10 blocks, 15 blocks is enough and use the standard blocks as much as possible. So if you try to change your information architecture, then it would be great to…

That would be the right moment to do that. You can do that with the same design as well. Yes, but it’s quite an effort. Well, it was quite an effort until two weeks ago. Because two weeks ago, the… How’s it called now? The Experience Modernization Agent went live. This is an agent in AM where you can use Gen AI to migrate your whole website, including design to edge delivery services.

We don’t have time to talk about this, but this would fill another hour. And I can say it’s pure magic. It’s really… It’s even black magic, I must say.

Look into this, look into the Experience Modernization Agent and…

Yeah, this is the way to go. Okay, we have finished all questions. We are already one minute over time. Thank you very, very much for joining. And if I could find it… There is a poll. Please don’t leave before answering three small questions.

And yes, the poll is up, it looks like. Thank you very much for your attention.

See you next time on the same channel. And have a good rest of your week. Thank you very much.

Take care, everyone.