Hi everyone and welcome to today's FirstSpirit Product Office Hour. This is the December edition. I am Timo. I am responsible on the product side for FirstSpirit. The Product Office Hour is a series of events that happens quarterly. One happens usually on a Thursday in English, the other one on a Friday in German. This session is recorded. Also, if you have questions or remarks, please don't hesitate to write those down and I'm doing my best to check the chat to answer your questions. With that said, let us start to have a look at the agenda. On the agenda today is the survey results. We will go through the poll that we had in the previous edition of the Product Office Hour and see what the answers were. Also, there's going to be a recap. So we will have a look at what happened in 2024 in terms of features and releases, but also events on the FirstSpirit and Chromebook side. Multi-set management is going to be a focus topic. You will get to see the new pieces of functionality in that domain in a hands-on demo. Also, of course, as always, we have a look at AI and I want us to focus today on prompt management, also in a demo. And then we are going to wrap things up by having a look at what lies ahead. So I will walk you through the rationale and a few of the upcoming topics for next year. With that said, let us have a look at the survey results. So let's start with the first topic, which is the strategy, because you said that you're interested. Strategy in terms of midterm roadmap, also the rationale that lies behind certain initiatives. As I said, we will have a look at AI and here not only what you will see is a nice demo, but then also we will see a few use cases and talk about best practices. The recap is then the topic that we will have a look at first in a second. Before we do that, if you think that you would love to see more on search, AI in search, or the FirstSpirit development part, or even CAS, and I'm listing here a few of the items down below, we will definitely have the chance next year to pick a few of those and also showcase new functionality in the prod office hour. With that said, and I'm looking at more and more participants joining, thank you very much. Let us go through the past 12 months. And here we are highlighting certain features. I want us to start by looking at e-commerce. So for e-commerce, we kicked off that section within the company by providing the Sprite Cloud Commerce OS reference implementation on GitHub. This is what the team did for you to have a look at best practices and how things can be implemented and done. A big one, of course, was the release of the Connect for Commerce front-end API. Here, the main value is that you can connect to any e-commerce solution that you want to. It's super versatile. It's easy. It's performant. It's the whole package, basically, as I see it. And then the third thing in regards to e-commerce, which was also provided during the first quarter this year, is the Salesforce B2C PWA Kit, also on GitHub, also available for you. Now, if we shift our focus and look at the developers and for Spirit, one could highlight the development capabilities being released in Content Creator. So during the first half of the year, the teams released the following functionality. From now on, you can, for instance, work on your templates within Content Creator. You can work on your database schema and also your scripts. Without ever changing the environment or the product, it's all in there. Additionally, if that is your tool of choice, you can use Git to develop for first part. So the idea is, in the past, you could not synchronously work on the very same part of your project. Now, by using Git, of course, you can because you merge off what you're working on. Let's say it is a feature and then you branch that off. Excuse me, you branch off what you're working on and then you merge. You can switch that back to your main project after you're done. Also, what was released was the first Spirit GraphQL API. So the CAS team did a wonderful job. This one can be used and is continuously improved on. Content Creators. For those, multi-set management, of course, needs to be mentioned. Big piece of functionality within Content Creator. It's, I think, quite easy to select content, put that in a bundle, and then distribute that from your main project to your target projects in a scalable manner because you can also trigger certain workflows, have automation with it, run some scripts as you like. The AI Assistant Suite during the middle of the year was also launched. Content Assistant, Analyze Assistant, Image Assistant. We will have a look at that a bit later. What I can say already is that we have quite a few customers use it, try it out, and the feedback that we gather is wonderful. And OCM3, of course, needs to be mentioned here. The idea here is, as someone working, for instance, in marketing, in your preview of your website within Content Creator, you don't want to bother with the fact that your project is a static, a hybrid, or a headless one. You also don't want to bother whether or not certain elements, because you can mix those on one page with OCM3, are on the same page. What you want to do is work efficiently on your content that you want to publish. And with OCM3, all of that is possible. As I see more people joining, thank you very much for joining. This is the Broad Office Hour, of course, and I am monitoring the chat. So if you have questions, please write those down there. For the project experts, looking at 2024, I'd like to highlight two items. First, rsync in the cloud. For a while, this was only available for on-premise customers. We've made it available for cloud customers, too. So if you want to sync your data via rsync, as a SaaS customer, you can also do that. And then remote data. In addition to distribution of content via multi-set management, the teams have also worked on and released remote data. So imagine you have a piece of content in one place, and you want that to be the very same one, same attributes, all of that, in a different place, different project, for instance. You can. You want to manage that in one place? You can, with remote data, because FirstSpirit helps you do that. And as you see on this slide, and no worries, I'm not going to go through each and every item here, the teams have worked on so much more than we can cover today. Just to pick out a few, the whole YouTube module got overhauled, updated, much better shape today. For the developers, the First Spirit Docker image for development and testing purposes is available. And then the script value service, which is also tremendously important. For certain AI cases, it's also available. If we look at the events of the past year, there are some to highlight. Lots and lots of webinars with several customers. So thank you very much for joining those and also participating in those. The customer connect days in several cities, as you see here on the photo. Many customers, many of you were there. You had a wonderful experience. You held your own presentations. Partners held presentations in Stuttgart or Düsseldorf or Munich. That was just a wonderful experience. Plus the big one here at the DMX in Cologne in September, both for the customers, but also for the partners. This was a big one with the booth and the attention over those days. As a matter of fact, Crown Peak was also present at the Oktoberfest in Stuttgart. In Munich. And most recently, there was a partner business meeting in Dortmund where we celebrated and gave awards to our partners. With all that said, of course, thank you very much for your continued interest in the product, for providing feedback and for staying with Crown Peak. Now let's have a look at the first piece of news. So I have a new functionality that is Modus App Management 1.5. And for that, I have prepared a demo environment. So what you see here is a standard smart living page. And as a quick recap, because some of you might not be too familiar with Modus App Management, as a quick recap, Modus App Management, you will find that with this icon here, helps you organize and distribute content across multiple pages and projects. So as you see me, as you saw me click on the icon, this pop-up appeared. And here I have two options. So I can pick an existing bundle and add content. And here, this would be my header section to a existing bundle. The about us bundle is here. Or I could create a new one. So here, let's say I'm creating a new one. So I can say, I want our demo of Modus App Management. And I can say, I want either the released, so the live state of that element that I just picked, or I want the current state. The current state might differ. Because here in my preview, I might have made some changes which are not yet released. In this case, I'm perfectly fine with the released state. And then I can pick from a few different bundling strategies. So what is that all about? As a quick recap, I have a few options here to say, I want to include the content references. So I want to say I have a certain element. It has certain references that are either on this page or to multiple other pages. I want to not even bother with that. So minimum, or I can say, I want to even have the outgoing one. So here, think of the size of the bundle. That would be the maximum. In this case, let's put it all in there. So if I had a bigger page that I'm adding, that would be my PDF, my files, my documents, my images, maybe even a video. Not only the reference, but everything including. Here, I can pick from two options. One is when I send out certain content, I am considering what is the status of that content in my target project. Because it might be that I want to override. It might be that I want to keep it as is. It might be that I have, to give an example, a page where in my target project, I made very specific changes to one or two paragraphs that I don't want to see overwritten with the next bundle distribution. So here, let's keep it as is. I could also then define a workflow or a script, as mentioned earlier, because I might want to translate content. Or I might want to notify someone in the team saying, please review. In this case, it's all good. I can save that. Now I have my bundle. And here I have my element. And if I want to see the overview of that, I have my product office hour here. Because I created my bundle. The use case today, that I want to show you, is going to be about the whole About Us page. So what I have prepared here, because I want to talk about the target project now, is a bundle, which, as you see here, was distributed to my Multisite Management France and my Multisite Management Spain target projects. And as you see here, all is good. Everything is updated, completed. Now, for the ones who are familiar with Multisite Management, you might have noticed already that we have a new tab here, which is the pull tab. As I click on it, it's empty. No worries. We're going to fill it in a second. The idea here is that when a change happens in the target project, so we have the one in France and the one in Spain, and that change was part of the distributed bundle, so that is the About Us bundle that I already had created, the project is saying, look, for instance, that translation that you provided is not correct. We have a better one. Or we want localized content. Please use that in the future. They now can make a change. And I, in my main project, which we're looking at, can see that change and then decide, do we want to accept or reject that? Let me show you how that works. So I'm moving from my main project to my project that I'm calling the France project. And here I have my About Us page as well. And let us make a change and see how that works. So here I'm going to rephrase this a bit. Nice. And you know what? Since we've distributed our bundle to not only the French but the Spanish project too, I'm going to move here as well. And I'm going to make a change here too. So we have now made a change on the very same element in different ways. Why don't we make a change that is only with the Spanish project? So here, as you see, I'm changing the title. And what I need to do now, because with the newest release of Modest App Management, we are not yet providing a user interface for the target projects that is on the roadmap, but rather an API. What I need to do now is I need to push that back to my master. So I've made a change here. Let me push that back. Let me push the Our Smart Home back as well. And then the same for the France project. There we go. Now, when I go back to my master project, I should see a few changes. And I do already. That is wonderful. So now we have a few elements here. You see on the left-hand side, the project Spain-France that works, languages that is English that also works. And then I can filter for all elements, non-conflicting ones or conflicting ones. And as a matter of fact, we only have conflicting ones here. Why is that? Because as you recall, the About Us bundle was distributed as is to those projects. And it differs now because you made some changes. So let's go in and have a look. So we start here at the top. What is this one all about? First of all, we see the element that is the source project that is Spain, correct? This one was in English, also correct. And then we see the name, the date, time, plus the conflict. There is a conflict here. And we see a few icons. So we can have a look at the log. We can merge. We can discard, say, I want that. Or we can say we apply that. Then we have a second item. And here you see I can open that one up. Why is that? Because you made those changes, as you recall, in the very same title on that page, both in my Modest App Management France and the Spain project. Here you see again, name, element, and then the time. And it's a conflict as well. So how do we go about that and resolve that? As I click on the Merge icon, you see here that on the Spanish page, what I did is I added the great, the team, our great team. And here that's my headline. That is in the main project that we are in at the moment. And what I can do is I can apply that. It has been modified, correct. I can then revert that if I don't like it anymore. Here I can apply component changes too. And I can edit the component if I want to. So here I could say, yep, our great team, and save that. Why don't we do it? So I hit Save. And so as you see here with the icon, let me zoom in a bit, the manual merge was performed. OK. And I can say I want to apply selected changes already. So let's do that. So we just have one item left. And these are the two where we made a change to the very same item. So how do we go about that? Distributed content, different, and one target project than the other. Let's see. So here I can hover again. And I have the same options. And I can also say merge if I want to. And yes, do it like that. Or I merge. And we've identified that's the same one, this one here. As a matter of fact, I think the title works as is. So I can bulk say, I don't like those changes. And they're gone. Now, as I made a change on the About Us page, let's scroll down. Here it is. This is how it works. So on my Spanish page, I added the great to our great team title. Then by multi-step management, I was informed about that. And I could make a decision whether or not I like that. I do like that. So I said accept. I've hit the Save button. And now here it is. And next time when I'm in multi-step management and I'm rolling out the About Us bundle, that change will also be applied. Any questions to that? Nice. Then let's continue. So what have we seen? We saw that we can act on the content changes that are coming from the target project or projects in our main project. And you saw me accept and reject. And you saw the list and the filtering. And all of that is based on the API for the target project. So I want to emphasize the user interface for the target project is on our list. With this release, we are starting to see starting with the new poll tab in our main project. If you want to go ahead and test this, please don't hesitate. Please reach out because we have a beta phase running. Now, the next topic, as we learned in the poll in our last proud office hour that you're interested in that, is strategy for next year. Before we talk strategy, I want to talk goals. So what are our goals in terms of product for the next year? First thing here, we want to keep listening to you. And that really means we love having those one-on-ones, in-depth discussions where you tell us what you like and what you don't like about the product. We love going through the insights that we're collecting when you're on the roadmap and you're writing a new idea. At the end of the day, we want to keep listening to you. And this is basically how we build a good chunk of our roadmap. Because we want to continue, this is our next goal, to make data-informed decisions. This means RICE is what we're going for. RICE here, if you're not familiar with it, stands for B, business importance. R, reach. I, impact. C, confidence. And E, effort. And along those five criteria, imagine we have a long list of items. They get a score. The score is not making decisions for us, but it's informing those decisions when we plan and look at new items. And yes, the goal is always to make a decision in which we pick the most impactful one. Areas. So what does this apply to? The first here is, and you might have seen that in the recap for the year, content creation. So think of marketing experts, those that are writing, creating content for it to be published on, for instance, a website within Content Creator. So Content Creator will get lots and lots of additional enhancements. And you will see that in specific items. We'll talk about those in a minute. The second area, though, is for the developers. Coding. You saw the wonderful releases of development capabilities in Content Creator for this year, the Git-based development. And for next year, there is more to come for that. All in all, one of the key areas that we are focusing on is scalability. So our solution is there to help you if you want to go global, if you want to have multiple pages and projects run in an efficient manner with efficient and easy, think about multi-site management, content distribution. Now, to be a bit more specific, on the roadmap for 2025, we are starting the first half of the year with Smart Search Java 21 and Solr and Zookeeper, by the way, as well, compatibility. Then additional CAS enhancements and updates. And I will talk about one in a minute. If you're interested in language pen release specifically, there is the previous Prod Office R in which we are talking around 5 to 10 minutes on that very topic. In regards to CAS, for CAS, the team has worked on a new rich text format. And we would love to get your feedback on it because the goal was to improve the JSON-based rich text format that is, of course, relevant for headless API with a more modern structure and a simplified handling on the developer side. So we want to improve the whole developer experience with it. On the right-hand side, you see a very small example of it. And we are already talking to some of you. We'd like to talk to even more for it to be a bit more refined and then to be released next year. One thing that should be mentioned here is something that I consider a good practice in the software domain, and that is sunsetting. Sunsetting means there is a piece of functionality, a plugin, a product that reaches its end of life. So you have a newer version or a newer product or plugin out there that replaces the old one, for instance, for several reasons. And here you see a few examples of that. We are replacing OCM 2 with OCM 3. And that means we are stopping maintenance and also provisioning at some point of version 2. The details you'll find on the right-hand side behind the QR code, plus a guide on how you migrate. Spoiler, if you use the vanilla version of OCM 2, it's not a hard thing to do. It's basically changing one URL. If you've made more project-specific changes, we are trying our best to guide you through migrating those as well. Next one is Fragment Creator. So here, maintenance mode with First Spirit 25.1. That is the January release that is coming up. Meaning, yes, there will be bug fixes, but only if we have truly critical issues like security-relevant ones. Regarding cloud availability of the Fragment Creator, we are ending that by default with the .3, the March release, and only on request providing it. And then provisioning will end by December 2025. If you have questions about that, please reach out. We are next default JDK. I think that's best practice as well. Now back to the topics that we are releasing and planning to work on. Collaboration and commenting. That is a new one that we haven't spoken about in this format. Let's spend a minute on that soon. The AI Assistant Suite will also receive quite a few additions and updates. More on that in a minute as well. And then, like I said, we are doing our best to make data-informed decisions. Please continue doing so. Go to the roadmap, provide insights, write a comment down a feature or feature requests, and we are reading that. Now, on collaboration and commenting. As you see here on the right-hand side, the idea is to help you work asynchronously your content through those stickies which you place on, for instance, the page soar, data sets, or sections. You will be able to provide feedback, edit then those elements, and just have multiple people working on those same elements in an asynchronous manner. As I mentioned, we have the roadmap here. You'll find the QR code. Please have a look. And continue submitting ideas. Now, for an announcement for the next product officer before we have a look at AI. Formcentric 7 is coming to FirstSpirit. You might be very familiar with WebForms. That is WebForms 6.x. Formcentric 7 is coming. And we have the experts of Formcentric join our product officer in March. Thursday the 13th and Friday the 14th of March. Now, to prepare for that session, those experts asked me to gather input. And it would be lovely if you could provide yours in a poll that I'm going to run in a second. So here, the ask is to provide a question or many questions that you have to the Formcentric experts. Please write those down. That would help tremendously prepare the session. Okay. I'm going to keep the poll open and continue. Because the next topic on the agenda is the AI assistance suite. And here, let's continue with the demo. So what I have prepared is my demo environment for AI. The newest update to the AI assistance suite is prompt management via content creator. So here, I'm going to open up the content assistant. That is on my right-hand side. And you might have noticed that I can hear. Let's have a look at that in a minute. Let us first translate that section to French. And see what we can do here. This is pretty straightforward. This is what you know. Now, up here, we also have an icon. So we can get a bit here. What we can do is now edit that very AI operation. So as you see here, we see the AI action. And here, I'm getting notified that I see a global prompt that is available in all projects. That is perfect. Because we are including not only prompt management, but also roles, rights, and permissions with that. So here in this case, I don't have the sufficient right to change that prompt. But I can have a look at the prompt and see how it works. Wonderful. And you see here, it is under language, presets. So we have the source preset as well. That is coming from Crown Peak. So we are owning certain prompts, providing a list of those. And I could have a look here and see my selection. So as you saw, I picked French. And this is how the prompt looks like. This is the first one. Going one level higher, I can also click here on that very icon. And then do even more prompt management. So what you see now here is an overview of all the prompts that are relevant for this very project. Let's start at the top. I'm looking at content assistant prompts. And you see those here down in that list. I'm looking at their visibility. So I can click, let's say, on this one and say, this one is active, meaning it's visible. It's inactive, invisible, or active by default. I can change its position. So I have my drag and drop icon here to move those operations. It's going down and up. As well. And what else can I do? Of course, I see the name. And I see the tag, meaning which assistant does this apply to? Because we have the content assistant, the analysis assistant, and the image assistant. And here, this is for the content assistant. And on the right-hand side, I have different types of prompts. What is that all about? I have project prompts, share prompts, presets. I can even see whether or not I modified those. So the project prompt means it's rolled out by server admins, users with sufficient rights, let's say, to those projects to be used there. The share prompts are also rolled out to multiple projects. But they can also be changed. So you saw that we did block. Editing certain prompts a minute ago. Others, I can change. So the share prompt, as you see here, is actually editable by myself. And as I click into it, what we have on the right-hand side is the testing. Let's have a look at that in a second as well. So if I wanted to, for my project here, I could say, I prefer American English over British English, or the other way around. Or I could say, numbers from 0 through 12 must be spelled out. Or I could say, numbers from 0 to 13. Add and delete certain rules here for my tone of voice. On the right-hand side, you see the testing, which we always have as well in this prompt management setup. So here, what I can do is I can pick my assistant. And then I can say, I have my input. And as you recall, we are working on the very first paragraph, which is about Crown Peak enhancing CMS, and so on and so on. And then my rules that I defined here, or my translation, or my keywords, whatever is in my prompt, is directly applied. And if I make a change, that will be directly reflected here. So that is the prompt testing too. I'm going to pause you for a second. Any questions? All right, so let's move on. We have this implemented for Content Assistant. We also have this implemented for Analyze Assistant. So here, on the right-hand side, we have our Analyze Assistant. And as I click on that icon, you see the very same overview. So we can work with that and change and manage our prompts too. And you see it's slightly different because, of course, we are now within Analyze Assistant. And now we are also seeing what applies to Content Assistant. And as a shortcut, if I want to change, for instance, my review, I can click on that icon. And now I have this prompt in front of me with the very same functionality. So I can also test my text. And here, the Analyze Assistant is picking a default text to work with. And you see how it applies what needs to be applied. All right, this is the prompt management functionality. Let me do a quick recap. We've seen today the Content Assistant and the Analyze Assistant of our AI Assistant Suite and focused on one thing. That was the prompt management, which allows you to edit, add, duplicate, assign, but also show and hide all compliance and scalability prompts. It is, of course, very different to how you would use ChatGPT in your browser or another third-party AI tool, as in everything that you have set up within FirstSpirit integrates nicely with your groups and roles and across your projects with how prompt management is set up. We've also seen two types of prompts. So we've seen the global prompts. That the server admin can change or delete. So we've been blocked by doing so. Very nice. See, that works. And we've seen the share prompts. And we've changed. We were able to change those as well. If you ask yourself about availability, in parts, this was already made available with the December release of FirstSpirit. The full functionality will be available with the February release, so 2025.2. For everybody who is using actively AI Assistant Suite and also for the participants of the trial phase, of course. A question we get asked a lot is, what is it that you support in terms of SaaS and on-premise? And also, can I bring my own key or do I need to use yours when I want to connect with certain AI vendors? And as you see here, let's say you bring your own AI API key. And you're a SaaS customer. It's all good. For on-premise, same thing. Let's say you don't bring your own API key for the AI vendor. That is also good because you can use ours. And here, this applies to SaaS and on-prem alike. And if you say, well, the AI vendors that you are natively integrating to aren't the ones which we use internally. We want to connect our own. Maybe you have a custom GPT. You can do that as well because we have the Assistant API that we offer. On the native integrations, there is an update as well. In the past, we natively integrated to OpenAI's shared GPT. And we started doing that already with the 3.5 release. Now, we are also natively integrating to Azure AI. This was much asked for. It is now here. And AWS Bedrock 2. So the only thing that we need from you is the API key and the endpoint. And then you're ready to go. I touched on the trial phase already for the ones who asked themselves, what is the trial phase? The trial phase is usually a four-week-long period, sometimes six, where you get the chance to try out the AI Assistant Suite at no cost attached to it, completely free of charge, and with a clear set of goals, regular check-ins, a review of your progress and how you're doing. Please do reach out to Marcel to get the AI Assistant Suite trial phase started. And as I said, it would be great if you could help us make those well-informed product decisions. So I'm going to run the second poll for today. So the first one will end, and that is the second one. And I'm going to leave it open, of course, for a minute there. And as participants are going through the poll, I want to make an announcement, and that is that we are going to have an AI webinar in January. On Wednesday, the 21st, from 3 to 4 p.m., with Justyna and Daniela. So we have experts in regards to prompt management and prompting. And UXUR, you'll learn about why certain decisions were made in regards to, for instance, how the analysis system or the content assistant works. Additionally, as we learned quite a bit about pain points during the implementation of AI, it should be more than just another tool in the stack. We will also talk about that. And here you'll find behind the QR code the registration page. That said, let me double-check once more the Q&A and the chat if there are any questions. Or please reach out if you have those. If another question comes up afterwards, after the session, and you're saying you want to write me an email, go ahead. This is my email address. As there are no more questions, there's one last thing for me left to do, and that is to wish you a wonderful December. And if you're celebrating Christmas, have a wonderful Christmas as well. And hopefully a great New Year's Eve. Bye, everyone.