Keynote - Adobe Experience Manager Update
Begin with an Executive Welcome from Loni Stark, Vice President of Strategy and Product at Adobe, setting the stage for the day. Then, join Cedric Huesler, Director of Product Management for Adobe Experience Manager, as he shares Adobe’s vision for digital experiences. Explore the latest innovations driving Adobe Experience Manager forward, their impact on web development, and a preview of what’s on the horizon.
Transcript
Wow. Thank you, Sherry and Ron. First of all, I just want to give a round of applause to the folks that have prepared and organized this. And, There’s too many people to name, so you know who you are. We’re not going to do, like, an Oscars naming everybody. But just thank you to everyone who has really helped to bring this together. Developers are so important to, Adobe and the experience manager at Adobe Commerce business. And then also, thank you to you, both here and online. I know many of you have been on this journey together with us for the last. Some of you for multiple decades now. So I just want to thank you for coming to this developer’s live.
I feel like this developer’s life is special because, we are now trying both the in-person and online format to really develop even a greater connection with all of you who are innovating on our platform. And, when I think about this journey that we’ve been on just recently, we reached an incredible milestone for the experience manager and, business, which is now the one of the cornerstone of Adobe’s digital experience business. And we had actually shot new, come and visit us and talk about his journey with, seeing the growth, the innovation in this area that started as something for web content management has now moved to really be the digital experience backbone of the experience cloud. So I want to share also, the journey that, I’ve been on and reflect with you on what I think makes this community, this developer community special and the people in it. So, I started actually as a developer, I know for some of you that may be hard to believe, but I started in 2000 as a developer during the.com boom here in Silicon Valley. So, like many of you, I started my career bright eyed and bushy tailed and, my, journey with em started in 2010 when we, acquired this company that started in a sausage factory. So some of you may know one of our founders who is now fellow at Adobe, David Schuler.
The core technology started actually in a sausage factory in 1993, where a bunch of people got together and said, how are we going to innovate and reimagine this space called content management? And so in 2010 was when I was just sitting at my desk at Adobe, and this incredible group of people, came through the door. And I will say that, it was one of it has been and will continue to be one of my highlights of my professional career was just meeting the incredible people, that came through the door and really reimagining content management, having all of these ideas. But it wasn’t just the people, in the core company, it was all of you and the people online, the whole entire community. They came through the door as well. What was special to me was, and what do I mean by it was just exciting, was that you had a bunch of people who just cared about.
Figuring out where the world was going and just making it happen.
And that was just so exciting to me as the developer in me, as the product leader and me, just to be part of the, the, energy that came through. And since then it’s been quite crazy. All the innovations. I know Cedric’s going to go into it, but we’ve been on this journey together, from just web content management to thinking about asset management, to think about forms, and now we’re throwing in some commerce into it as well. And in each part of that journey, we’ve reimagined what great experiences are. We’ve reimagined, which means to have an enterprise cloud solution. We reimagined what developers were capable of and the kinds of experiences and the insights that we can gather from these digital experiences. And we’ve had companies, right? Brands, large brands, build their digital experiences on this technology in partnership with many of you.
But one of the things I didn’t realize back in 2010 that I’ve come to more appreciate now that we’re on to 14 years and counting. Next year will be our 15th year anniversary as part of the Adobe family.
For this part of the business is something that I’ve observed, which is this is a group. This is a community that is a leader in this area and still not afraid to disrupt it as well. And the latest area, I would say that you’re going to hear from many of the speakers is how we’re reimagining the role of what developers can impact, as well as the kinds of experience with Gen I, AI and what’s incredible. Right? And I hope Cedric doesn’t mind me talking a bit about him. He’s going to be speaking next. I’ve known Cedric for 15 years, and ever since the first day I met the guy. First of all, I thought, you know, he he basically explained the whole thing to me right? At first. The first couple of weeks was like, Cedric, what is this? Content management. He was patient. He went through all of the details. But what’s interesting about Cedric is he’s an expert in the industry, in content management. But yet every time I meet the guy, he’s talking about what is going to change, what things we’re going to continue to innovate. And that’s been going on like for 15 years. And Cedric is not alone, right? We have Lars back there. We have Marc. We have all of you. We have him and we have folks here. And I’m just mentioning a few. But all of you make this such an incredible community where we have experts, but also people who are courageous and unafraid to disrupt everything in order for us to be continuing the leader and to create the future.
And I thought about, why is that? What makes this group, what makes you, what makes everyone online so great? Just to be able to be a leader, to have built so many accomplishments that all of you have, and yet be courageous and unafraid to tackle new things. Here’s what I’ve observed, and here’s what I’ve come to the conclusion about each and one of you, each and every one of you and the people I’ve met. That courage comes from our recognition that in this journey that we have been on, we have grown, we become stronger. And as a result of that, we have this inherent belief that the future of what we are able to create far exceeds anything we have created to date.
That is the inherent belief that we share as a community, and something I truly believe as well, which is no matter how amazing all the things you have accomplished, what we have accomplished as a community, our future is brighter because we are stronger and we have the capacity to create.
And m what I love about M as a product is it brings together the developers. It brings together the creative. It brings together the marketers to help brands create their future of who they are as a company, how they interact on brand engagement all the way to commerce that is the Y, and that Y is built fundamentally on the culture that we have as a team, as a community. And this developer’s life, to me, is the ability to bring you all together online and here in person, not just for us to share what we’ve been thinking about, but what’s so important is for all of you to also in the online comments, in the questions, in the dialog that happens with all the food and beverage to actually share your idea.
And from that, we’re going to create the future. We’re going to make it. It’s so exciting. I don’t know about you, but I’m excited and tired at the same time because just when I thought that the last, you know, that things were starting to, move and we had all figured out.
Jen, I came into the picture, I natural language processing, all of that, but but what’s interesting in innovation, I find most exciting is it builds on top of the shoulders of what we’ve already created, all the assets, all the, knowledge that we have in our systems today. And so I think this combination of both, everything we’ve learned up till now that makes us who we are and this new technology, it’s going to be really amazing. And with that, I’m looking forward to what comes out of this day. But more importantly, I’m looking forward to all the conversations that this day will start going forward. So with that, I’d like to bring up and welcome Cedric. And I think he’s going to share a couple things. And every time I talk. To Cedric, that blows your mind. So. So, Cedric, welcome.
Okay. One second and of course.
I’m good to go. Okay. Well, thanks for having me. Yes. I am the lead product manager for Am sites, and I don’t commerce storefront. And what I want to do in the next 40 minutes is following.
I want to give you a little of an update on what we’re doing with as services.
Then I would just want to talk a little bit about what keeps me busy. Day in and day out and, general, talk about the future.
So let’s get into house action and services doing so I think, the first one you might know that we started that kind of like it’s a small project, and the idea was that some folks might have heard that story or any or none, but did it really was, how can we make sure you can deliver or build and deliver websites or web based experiences? They don’t necessarily need to show up in a browser, web based experiences that you can do this, factor ten or even more faster from the development point of view, but also that the end result, the actual site, is as fast as it possibly could be. And we said that level to fastest websites in the world.
And I know that’s a tall order. And I’ll talk about this. Quite a bit today of what it means and what a challenge is, are and where I feel like we all need to work together to ultimately achieve this goal. And we’re going to apply it. Now, having said that, a little bit more than a year ago, it was in October last year, we launched, and built this, so this domain where you can go and you can just, go and try out the services. It was a deliberate choice for us to make sure that this technology that be filled, we can make this available to all folks of the community here, in order for everyone to try it out because it is a departure. It is a departure where we came from and is part of where we want to go. And so we felt like it’s really important that everyone gets a chance to learn about it, because it is new and different. And again, this is just some stats from, October. I think once we just finished, we had over 740 of you folks out there, creating new sites or storefronts. We’re using the same technology for both, and which I think is great. And actually, this number is, is probably is higher if you remove all the tests. So I took the list, I remove all the things that are obviously like a test in order to now because the number is obviously much higher to with that. So this is a phenomenal growth for us in terms of and it’s even executive order on it, which means that you all on there that work on it Adobe spends monitor every day that you get a chance to try out. And actually the services would look something small, something big. Whatever you’re building, get used to it, learn about it. And it was feedback. The other one, the other aspect for us to measure our success or our ability to, to show whatever this technology serves as purpose, is when we measure it, the amount of change we used to have, we can do a big difference, obviously, between the experience manager and the way you know it. And actually the services is actually results accurate. So you’re delivering anybody and everyone doesn’t matter if you are doing a com that runs on it or your test site that you just created five minutes ago, that is all delivered by the same service. And, and where I was, you know, looking very closely into that. So at this point and you see here we’re delivering the last seven days, over 80 million interviews from that service, and it’s probably around 11%, the, complete traffic that we have of a service, service level is, you know, folks, you know, you all have, shared, you know, on dedicated compute, versus instances. The other thing that I want to talk about is our community here. Definitely. That’s also, I think, change for us. We decided last year, a year ago now, and we want to have a deeper community with all you folks in it. So that allows us to really feel the questions or, or really create this community that you folks are sharing among yourselves. And I definitely want to, I will find a few, things to process, my speech today about, what I’ve learned from the community.
So one of the key differences between the services I think of. You think a search engine or a manager is that you separate the delivery? You know, the actual part makes your website get delivered and the content management or what I referred to is as the content source or the content is already managing, content is coming from and I don’t want to introduce it. Initially, this was even before general before general availability. We focused a lot on what we call the common baseline. And today if you go to analyze and try it out, you are actually, you know, getting it to a tutorial which walk you through and how to use inbox as your most resource. And I know a lot of folks in the community or an outside, I’ve kind of pushed ahead a little bit. So like, what is this? Why are you doing that? And I think there’s I want to say two things about that. Number one, we really wanted to find a way to, when little of it, this little dependencies or other things that you can try out additional services and find a way to basically separate the content management in a way that is completely different. And in this case, yes, Google Docs, for example. Now let me check that all the way of doing that, we also discovered there’s actually quite a bit of benefits. There’s lots of use cases or places where actually and just a document that is there to actually publish the page is actually reasonably easy and a good way to do so. So we have therefore kind of embraced this idea that the content doesn’t all have to be in the same place. It could be some various pieces. Chances are it’s already in the cloud somewhere, and then you want to take it from there and publish it. But of course you don’t want to. Folks that use that. All right. That’s folks that use em as you know it, you know, content repository. And last year at summit with us here in summit this year, we officially, made all the parts available to use, Amazon know it as a content source. Excellent services. And, and we got some really good uses here. It’s hard to represent Supreme Court. These are again the, the sites that were created just last month. This is not complete here. This is just, what was created, last month and which content source is chosen? Of course, The Boondocks, most of those, I believe are probably folks who are using the tutorial and making something more than just a small test, which is great to see. Yeah. Yeah. So I also represent your, previous announcement. I want to say here we are going to bring, this, like, exclude services for delivery tier four. And you’re going to bring this to my instances. So all the customers that are using managed services today, that I mentioned, this is offering, that we are going to make this available at the beginning of, 12 throughout the first half of next year. But if you’re super interested in that, you want to get going.
Let us know. And, we can get to you here on this model, developing this capability and make sure it works as intended. Okay. So the other, I think interesting aspects to kind of last bullet point here on that slide, bringing your own content. And that’s something that we want to keep investing more and more. One of the capabilities for you just a few months ago certainly called helix five, or our ability to, you know, once again next you think need your version of services. Now again, you typically don’t see us updating self service. That happens like I maybe twice a week or something at this point. But, in most cases you don’t notice anything. But we do tend to on and off shift with our new features. And one of those is, the ability to make it even easier to bring in older content sources in and, publish them through your APIs, through our delivery infrastructure. I think this is a great way to really, consolidate, different sources that you might have without having to move them. Good. So let’s think about and I was, when I introduced the services, as I was talking about websites, and I think it comes through, the point you folks might have heard me talk about this before, and, it’s, something I’m very passionate about.
Making a web experience that is as fast as you. I don’t know what to expect. It’s kind of a new comparison for everybody. Has a different kind of interview expectation. But I think initially it certainly was. Let’s. Okay, we can create native mobile apps, which I know a lot of lives can be really fast and well built.
And then this whole discussion started when he comes back from that time on the mobile rise came up with the live stream. And I was like, why can we not build websites going as fast as we want? And but having all the downside of, of, you know, having to be updated or more modern.
This comes from that idea that we really want to do that. And, it’s really great to see the community directly and to further, everybody’s take like the shepherds of the web being a browser developers, folks working on browsers, folks are web standards folks working on infrastructure. Here are, protocols like it should be. I know this, have really come together over the years and have delivered one piece after another that today allows us to build sites that are as fast as native mobile apps and don’t have the downside of, mobile apps. Something that you might be running an old version of the app because you didn’t updated it. You don’t want and you look at the, how are we doing? These are, 388 sites that run our services that we’re tracking. We have an internal system. We have our own rules on how far we want to go and what we do. And it tracks around 55,000 worlds. And, it’s going to, you know, think of a cohort of URLs and, it’s time to look at and see how they’re doing. Again, we’re doing pretty good. It’s, it certainly is respectable as a result to see. Now, the question is, what is good? Good is, Greek government. So if you’re passing the three core learnings, metro system is what you consider good and of course, inverse places where you need to work on. And but it’s very interesting and I think is the mindset for us as a company. If you think of, optimizing things like your to your website, slow. Okay. Sorry. Sorry about that. Right. And our new approach is actually if your site is so.
Well, maybe there’s something we need to learn, right? Yeah. I want to get into this a little deeper. One of the things that gives me great joy, if I can look at these kind of graphs where and just to kind of to accelerate this chart, is that for three course vitals? I’m sure everybody of, you know, and, and these are, for example, like a site we were previously running on a different technology or company and, with, with their sling based delivery and or e-commerce delivery. Mr… Have after distribution of services using this web services, those public lands are basically improved to the point of delivering are bring I think that is exactly what you want to see again. So folks are already halfway there.
You it’s just one of the metrics is missing, right? Others, are way off and on, right.
Unlike let me back.
Okay. That was, All right, let’s talk about, what good looks like. Let’s talk about what great looks like. So now our friends over as well. Tech. I just recently launched customer, ecommerce services. And, again, to do want to do that in most front. We got a great tutorial at least already, which really walks you step by step through how to redo your storefront for e-commerce.
Using, Pitch linen services, which is the link inside hardware. This. But anything that I want to pull out here is there’s so much things that we can do out of the box. And then there’s challenges that you have to clone yourself in terms of more. And those results in the, the, the challenges that like website performance is a lot of different reasons and why we as vendors can give you a really good start, can give you the maximum amount of budget or available budget for you to spend into your business during the part. It is challenging to anybody here in the developer community. This screen here should not be unfamiliar to me. I just called if it is optimized. If you’ve never seen something like this and you can do that, you don’t have to install anything as a command.
Please just put it into your calendar block. One and right there, profiling your own website. Okay. Now you don’t hear us to understanding how the browser actually loads a site in search of the sequencing of resources that are downloaded is something very vital to success. If you’re building a site that is not just fast initially and consistently fast, why? It’s about two. It’s it’s about clarity to rate. And what needs to happen. There is can this team answer LCP questions when the website is on the user? You really want to make sure anything that happens before is anything that is towards can also be fast. And I have many conversations with customers about this guide. There’s all kinds of things that happen before dawn, which is very challenging because.
You need to really ask yourself the question, what do you want? What’s the most important thing on a website? Is it important that you are all the people? I don’t want to call out somebody, but I it’s important to what your.
Ability. I am calling out on my own problems here, but if we have to trade off to performance and again I’m super biased, but I think I’m fine with doing anything. If anything ever wanted right after LCP. But don’t do before because you really want to make sure that whenever a user clicks on the page that you actually see something, because otherwise, what’s the point? Now I want to show you this site, because you can reproduce this yourself. With this tutorial. So what is it? It’s really the how how fast can website possibly be? And, and so you hear this little that you try to again we were trying things out with transitions other things. But sorry. So basically I know it was on a, on a fast network here and, but if you see the, the URLs on it.
Oh it. Okay, okay okay, okay. So it looks like there’s some audience here. Sorry about that. I hope I like, so the ability to just do pretty much instantly load pages and being as quick as possible, I think a welcome everybody to visit the site or browse around it. I think it’s a good example and it’s it there’s not that much magic that goes into it. It’s really using our boilerplate basically. Plus, some making sure that you’ve implemented it according to the way we recommend it. And then you basically get that. And I think that is a testament to our achievable of getting it to a point where you can just build sites fast. And so I really appreciate everybody who has spent the last 12 months with us. Plus to figuring this out and putting all those pieces together for us to do that.
Good. Having said that, there are still many ways to go wrong and we we really believe that there needs to be a better way to do that. And we talked about performance quite a bit, but there’s more than just performance. There’s lots of other things that you need to do to make your website effective. The question is, whose fault is it? And I know it’s a little bit of a joke here, but in our kind of older mindset, if I think of this and I’m talking about my mindset here, I was like, well, is your problem because you built the website, so you want to see us in the next 6 to 8 months, really talking about this problem and how we as Adobe are going to be taking care of this for you. So looking forward to talk about this a lot more, as we’re going into next year, because operating a site or a storefront and I call it peak maturity or like that, it really runs really smoothly and does not impact or negatively impact any of your revenue for, again, 100 and other reasons and something that we we really want to, dig much deeper in and make this, a place like, make em a place where we are just taking care of that.
Having said that. Performance. I talk about user experience, mostly all those other benefits. I know you know that. And one of those is traffic from traffic, like Google or other traffic sources that are either because it’s easier to index to page, or because we’re really cleaning up your site map, which you might have a mess in. Or again, not calling anybody out here, but you know, these are hard, hard things to do. But when you do it right, when you do all that, when all these things are done properly, one thing that can happen, and here’s an example of a customer that you’re getting more people onto your site that you otherwise would have to pay for. What I mean by this a key acquisition strategy for sites today or buying advertising. That’s great. You can do that. But how about getting some free traffic? And I think we really got into this when we looked into, okay, what can we improve? So this site here, what you see is that we were able to, again, with improving the site. And you really have to look at the middle line here. The middle chart is that’s the real numbers. That’s basically the daily volumes of traffic that comes to the site without mentioning the brand. So if you think of these 527 people, that showed up on this site on that day, on November 4th.
What can we do with them? Because they came to the site with not the intent, the brand and think of, you know, what device you would look for the brand and say something like in Portland. But in this case, they came to the brand without. And I think that’s our next foray is really understanding what happened with those people that come to the site and what can we do. And we really focus. We really focus on just exactly and often people going to I want to know the exact journey that they went through and everything you can do to look at tools. For this, we focus on exactly one thing. The problem is that a lot of those 500 odd folks that showed up, they made one page for you and walked away.
Or just disappeared. And we don’t know what happened with them. And that’s one of the things that we really trying to, focus on in our work, both in the sense of tooling that we want to provide, you provide you folks both and in the way that we can proactively understand those patterns and make recommendations to you folks about what to do. So the chart that you’re looking at here right now is, data that we capture as part of the resources folks probably know that we have a service that is included in actually, we call it run. And as part of that, we’re not just tracking page views, which is great, but we also track what actually happens on the site, which is very interesting actually, for the very first page for you, because that’s where you got the biggest loss, because you want to understand what happened, and particularly if you make any changes to the site, whenever there’s any benefit of that.
So this is something that you’re going to see us again. We’re going to invest heavily in that area to, not just necessarily giving you a tool where you can create these beautiful reports. You can have that too, but you’re going to spend the whole day looking at reports and deciding, okay, what should I do next? But we only want to we want to get a step closer. And so we actually want to give you recommendations based on the data that we’ve seen. And then you can act upon those.
How do you get there? I had this question a lot, of course, because we made a significant change. And folks are okay. So how I’m going to start using your services now. We talked about the tutorial how if we haven’t done that one yet, that’s step number one.
Step number two is really figuring out where could you get the most benefit of it, like as part of your implementation, as part of your current deployment, where do you get most benefit? Again, some folks go on this journey and say, you know what, I love this. I’m going to wholesale change the whole site and we got tools to help you. And I’ll talk about those shortly. Others like, you know what, I really have this area of my site where either because of performance or because I mean, or because I continuously make changes to this page or continuously make design and layout changes to that site because we maybe are experimenting a lot or we got other things. So disability for you to build code and deploy quick. And I don’t have to really talked about this too much yet about its delivery services ability to very quickly build things and deploy them. To the developer experience. And I’m going to switch to this topic now. And, I want to shout out to Tom, Thomas created some awesome tutorials out there in the community, on how to leverage some of the newer AI coding, techniques to be much faster about edge level services or adopting ancillary services faster. So let me just stop here for a brief moment, and I want to talk to you about something about that. So software development or coding right? Is has changed everything. It was the first place where Jenny, I, I think made a big impact. Right now we talk about all the things that marketing company and and stuff. But software development is the first place obviously with GitHub copilot and others you can’t name, you can’t count them anymore. Ways to help you to be more effective.
And one of the key things, one of the key technology decisions that we’ve made, knowing that development will change because you’re so smart, how to complete even some of the things was already early on visible and obviously now today, but so on, prompt development is that we wanted to make sure that we develop the technology or the stack that we choose to, for you to deliver your front end should as standard as possible. So for you to leverage off the shelf tools to be much quicker and build. So the alternative is like, oh, you got some proprietary templating language or some poetry APIs and so on. So that’s harder to, adopt this kind of new way of developing. But because services really relies on HTML as an API, if you think this way. So for those so that you know that we’re delivering an HTML server over the edge, that basically, yes, it’s markup as an HTML, but technically it’s actually an API because it’s clearly structure.
And we’re using the browser Dom and the blocks that we’re loading as a way to decorate the data. Think of the HTML data to decorate that a way that you need it.
Two benefits of that. Number one, we’re solely relying on the browser’s capability to decorate that. I mean, you can use your frameworks if you want to, but again, most of those modifications are reasonably straightforward. Talk about websites and publications, right? Websites. And therefore, because we’re just using standard API features of the browser, today’s code generation. And Jenny I can at his code innovation comes with can actually do this fairly easily. We’re going to show you a few more examples. Just today, of what we are doing with this now and how much this will accelerate your development process to build new blocks and to basically get to a point where you can just make a make up any design you want, and you can just deploy that reasonably quickly just because you don’t really have to put all those pieces. So the standard browser or APIs, as, the conduit for much faster development with any number two is, the ability for you to. So I’m going to make another jump on jumping ahead here. But another jump is in the future. And I’m going to talk. Another is going to show an example in a bit. Experiences or the content experiences doesn’t necessarily come as a static HTML from the server, but there is going to be a mix of generation that happens on the edge, and some adaptation consideration happens in the browser. Again, I just stepped a year ahead of all of us here. Okay, I comes to the browser so we can now start to personalize sites in a way that has never been able to do before.
The challenge with that sense from that is taking team work, which is being figured out. But the other one is how do you develop what’s and this idea that you have blocks? These blocks are completely independent from each other, and you can load the JavaScript. And yes, for those blocks exactly when you need it. If you look at how actually the services works and if you open that debugger that I showed earlier, you see how we’re doing this. One of the loading know is every performance which tells you not to do this, but don’t listen to those blocks.
That’s a joke. It’s not a joke because it shouldn’t be. To really solve this problem, you can. Wonderful. Loading. This is no problem. But, it allows you really to load the code in JavaScript is needed for this block. That requires imagining a web where you have not no longer using, just the static rendering. The static composition. But, you are generative UI composition, the ability to load exactly stuff from the server that is required for this experience to work is going to be essentials.
In the last five minutes, I just jump straight ahead of where we could be, and I understand I might have lost some of you folks. That’s, We’ll get back to that. But.
How do you get there? Leverage the latest tools that are available out there to help you to build that code, from that code that’s required to build your experience we have today. And you will realize that it is a fraction of the time that you spend today. Whatever other technology stack you have, including the Am. And we all know. So whether we’re working on tools which you find until the end of life, that helps you, it really extracting the content out of your site that you have today, structuring data in a way that actually the service understands, these are stored out in Google Docs, SharePoint, or even right on that source you pick and then make it available. So later today we’re also going to show you how this works on computer that we’re offering here. That helps you to really to, kind of structure the content in a way that, that, actually services that’s ideal for businesses. All right. So while it were kind of like or a step into the future and I want to talk about one more thing and that is. If you look at the the Java repository, we have search indexes that we keep up to date at any given time. Right. Because the actual underlying JCR requires this search index, because there’s lots of TCR APIs itself that actually rely on search to work properly.
Now, with the onset of new search functionalities and specifically talking about the search here. So the ability to not just search is an inverted index or whatever other index types that we’ve been using for the last 15 years in the table. But you methods for retrieval have obviously been, discovered or discovered. Not really. They’ve been around for a while, but they really go mainstream now with with RAC, right. When you’re basically using an index to index your content and allows you to make semantic search, or you can use it to get an Lem Welsh language model to actually generate content or summarize. And that’s how a lot of this technology, it’s only using today, including what I just referred to earlier, helps you to do that.
One of the things that you want to do is we want to make or we will be, making. And it’s kind of come to you very soon. You’re going to make something, that makes, default. Yeah. So whenever you give it, for services, there’s going to be a vector index that’s going to be kept fresh and update to the second, and we do that both for author and just for delivery. Now, just the fact that we’re going to make this available for you is actually you can start to build some really cool things for it. So an example I have here is actually our intranet. Here the domain that runs on him for the cloud service to be specific. And the ability to just ask questions about the content that is in your repository or in this case in the published repository.
So I want to actually, stop here, but we look forward for a conversation with you folks.
How can we leverage this index for lots of interesting things? We’re going to build it into our do you I you do find content. We’re going to build some interesting features within the product UI itself. You’re going to talk a lot more about it. Summit and we want to make sure we want to make that API available to you folks to build really cool things, actual site. So connecting the dots, I was just talking about this idea of generative UI so that you’re making decisions as the page is getting rendered or as you requested based, maybe some, some of those, some of that index. And to change the way to site render and the ability for us to do that while the page is rendering and not loading too much stuff ahead, the loading, the blocks that are actually required for this page to render was just the two topics at the topic I just talked about earlier. Combining this with this one. Now you kind of see the bridge that I’m trying to make here, I think will get us to a place where we have a great infrastructure and I kind of dare to say framework, that helps us to really build these next generation web experiences that our customers expect, because there’s clearly a race going on. Are you going to go to your agent, an assistant, to get everything done for you or or not or and are you going to go to your trusted brand site, which will offer the same quality and flexibility, but based on the trusted content of the brand? We want to be your partners in building these next generation web experiences that really cater to the consumer. The future consumer needs that we all getting used to with being able to ask any question, any time, and we get a response in a matter of just a few seconds.
All right. It’s your turn to fill that slide here.
Looking forward to discussions on this on what cool things we can build next time I’m going to show you work here. So that’s it for me. Thank you very much.
Community Discussion
Continue the conversation in the Adobe Developers Live Community discussion.
Key takeaways
- Importance of Developers Developers are crucial to Adobe and its Experience Manager and Adobe Commerce business.
- Hybrid Format The event is special because it combines both in-person and online formats to foster greater connection.
- Milestone Achievement Adobe Experience Manager has become a cornerstone of Adobe’s digital experience business.
- Historical Context The core technology of Adobe Experience Manager started in a sausage factory in 1993 and was acquired by Adobe in 2010.
- Community and Innovation The developer community is recognized for its leadership and willingness to disrupt and innovate, especially with new technologies like Gen AI.
- Performance and Speed Emphasis on creating the fastest websites and web-based experiences, with a goal to deliver sites as fast as native mobile apps.
- Community Engagement Adobe has launched a domain for the community to try out new services and provide feedback.
- Content Management Adobe is focusing on separating content delivery from content management, allowing for more flexibility and efficiency.
- Future Developments Adobe is investing in new technologies and tools to enhance web performance, user experience, and developer productivity.
- Generative UI and Personalization Future web experiences will involve generative UI composition and personalized content delivery based on real-time data and user interactions.
- Search and Indexing Adobe is implementing advanced search functionalities, including vector indexing, to improve content retrieval and user experience.
- Collaboration and Feedback Adobe encourages community collaboration and feedback to continue innovating and improving their products and services.
recommendation-more-help
3c5a5de1-aef4-4536-8764-ec20371a5186