So my talk today is reallygoing to explore not just
a genetic experiences, but alsofor those of you who are in agencies,
really wanting to give you a little bitof a look at what goes on at Enterprise.
Because I've been in WordPress as wasjust mentioned for about 15 to 17 years.
And in all that time, I havebeen around the block, let's say.
I've started out like many people, auser using WordPress many years ago.
And from there, I started my journey intoa lot of different avenues of WordPress.
I worked in the SaaS worlda lot, so I've done plugins.
I've sold, you know, themes.
I opened an agency and ranan agency for about 20 years.
Some of you may know Envatoand Theme for us and CoCanyon.
And if you were around about 10 yearsago, that's where I used to work as well.
And it was a lot of fun.
And so one of the things that Idid over these years, of course,
was doing that, the agency kind of thing.
And in an agency, you mayhave experience this as well.
If you've ever run anagency, you start and you build
these small websites forteams of one or teams of two.
And then over time, you geta little bit of experience and
you start to grow and you'reable to charge more money.
The logos that you haveattached to your agency
websites start toget a little bit bigger.
The teams start to growthat you're working with.
Now you're not just working withteams of two or three, but maybe 10 or 15.
They slowly start to grow.
And this, for me at least, wasthe world of WordPress that I knew.
For many, many years, that was what I did.
And I sold into those kinds of companiesand I was really, really good at it.
But it was all about thesekinds of things, right?
Feature conversations, likewhich plugin should you be using?
Which page builder should you be using?
Is WordPress better than Wix orSquarespace or whatever, right?
And I think you probably allknow this conversation too.
And so when I joinedWordPress VIP, I was really,
really confident becauseI knew WordPress, right?
I knew the ecosystem.
I had over a decade in the community.
I had even written for things likethe WP Tavern, which was a lot of fun.
And so because of all ofthat, I thought that I was
prepared for what enterprisewas going to throw at me.
In fact, I had been an enterprise before.
So I knew it from that side.
I knew how to be a user.
I knew the tools and I understoodthat world kind of from the inside.
And so for me, though, thiswas the first time that I was
actually going to be on theother side of the table, right?
Working with enterprisebuyers, teams making decisions
about WordPress at thelargest companies in the world.
And I thought the problemswould be familiar, which is bigger.
More users, morecontent, a little bit more
complexity, but fundamentallythe same kind of work.
But it wasn't.
To the problems were materially different.
They weren't biggerversions of the same thing.
There was organizationalcomplexity, technology complexity.
And yes, WordPress complexity.
And what I discovered was thatorganizations weren't just comparing CMSs.
I mean, that conversation, the one thatwe've all been having for years trying to
convince people about WordPress in enterprise,it's there, but it didn't apply as much.
Because the CMS decisionwas kind of already decided, right?
WordPress was there.
The question aboutwhether WordPress belonged
in the conversationhad already been settled.
The conversations thatI discovered had almost
nothing to do with theWordPress that I knew.
They were problems I didn'treally have language for, right?
And for me, somebody who hadbeen in WordPress for 15, 17 years.
Somebody who had written formajor publications in WordPress.
Somebody who had been marketingWordPress to users across the globe.
It was really humbling because all thatexpertise and confidence didn't matter.
And I was back to being a learner.
It wasn't because any of myWordPress knowledge was wrong.
It just wasn't the thingthat mattered in the room.
And then you want to throwsomething else into the mix.
AI shows up.
And AI shows up not in a smallway, but it lands like a bomb.
Right? Accelerating everything.
Changing the entire way we look at the web.
What enterprise was tryingto solve yesterday, things
like personalization,workflow, content operations.
AI began to rewrite those conversationsor those questions in real time.
Problems began shifting fasterthan anyone could build playbooks for.
And watching this from inside, thelargest WordPress deployments in the world,
is incredibly different than maybewhat some of you have experienced.
And the gap between whatenterprise is dealing with and
what the rest of the WordPressecosystem is talking about.
It's not actually gettingsmaller, it's getting wider.
Maybe you're like me, you'rewatching enterprise from
the outside, the projects,the budgets, the scale,
wondering how can youget into that conversation.
It is different.
And right now it mattersmore than ever because of
what AI is doing to themarket that we're in today.
I don't know aboutyou, but at least for
me, it feels a littlebit rocky, doesn't it?
AI is kind of makingus all a little bit nervous.
At least for me, I look at it andI see people that can go and
write a single prompt and declawedand come out with a website.
What does that do for thoseof us in agency and freelance
world when now they don't needus to do that for them anymore?
For some of us, this isan existential crisis, isn't it?
I mean, what happenswhen AI is the first person
you call to build a websiteand not an agency?
Now, I don't think it's the future forever,but it is a moment that we're in right now.
It's real right now.
The thing that we have spent 20 yearsmastering just got commoditized in six months.
It's a big problem.
Then there's the speed of thenew players that are showing up.
I mean, lovable is a $400million business in one year.
An AI site builder that didn'texist and now it's everywhere.
And these aren't incremental competitors.
They're moving at apace that feels impossible.
And we're watching it happentrying to figure out where we fit in.
At least that's how I feel.
Do you feel that way?
See, AI makes it reallyeasy for a team of one
to produce something,anything really, right?
Because they're the only user.
This is something that Ihave been noticing a lot.
I've been wrote about it on my blog.
There's a post called N equals one.
Go check it out if you want.
But it works becausethey're the only ones who
have to care about what'sunder the hood, right?
If there's a bug or if there's anissue, you just go into Claude.
You say, hey, Claude, this doesn't work.
Claude goes, oh, you're right.
Let me fix it for you.
And then it fixes it.
And your websites backup and running or the
thing that you're buildingis back up and running.
That's fine.
But as soon as youintroduce a second person
into the mix, everythingchanges, right?
A team of two is a fundamentallydifferent problem than a team of one.
Now think about this, a teamof ten or a team of fifteen.
It's a totally different universe.
You have to think about workflow.
You have to think about governance.
You have to think about compliance.
Editorial standards acrossdozens of contributors.
See, that's where AIalone can't actually solve it.
That's where human expertiseand WordPress actually matter.
And that's where enterprise lives.
You see, if we keepfocusing on teams of one
and, you know, theanxiety of what's going on
with all of these Claude typeexperiences or Chachi PT, right?
And if we keep ignoring teams of many,we're missing an incredible opportunity.
See, when I look at what'sgoing on in enterprise, the firms
that are getting the calls aren'tactually better at WordPress.
In fact, they're often worse.
But they speak the language of the problemsthat enterprise is trying to solve.
And the challenge I have is, we're noteven sure what that language is, right?
We hear a Gentic and wehear AEO, and we're not sure if
that's our problem to solveor if that's someone else's.
Right now, somewhere, anenterprise is trying to figure out
how to make their websiterespond to an AI agent in real time.
And the people in that roomaren't WordPress people, right?
Not because WordPress can't do it,but because nobody from WordPress
showed up able to speak thelanguage of where enterprise is.
It's the problem I had,it's the learning I had to do.
So about a year and a halfago, I want to tell you the story.
Salesforce, you may know Salesforce,big sponsor of us here at Work Camp.
Salesforce came toWordPress VIP with a concept.
They had this idea for somethingthat they were calling adaptive websites.
And in fact, at that time, theydidn't even call it adaptive websites.
They didn't have a name for whatthey wanted, but they had this idea.
They wanted an AI agentto actually build a page.
And this was a year and a half ago,so you can imagine where we are now.
They were thinking aboutthis a year and a half ago.
So you're on a site, right?
You interact with an agent in achat box, and the page actually
adapts and changes as you'reconversing with the agent.
Similar, if you're familiar withCanvas mode and chat GPT, right?
Or in cloud where you type somethingin and then it renders something for you.
That was sort of whatthey were thinking about.
And they wanted thepage to rebuild around what
you were asking forevery time you prompted it.
But what they wanted was tohave it powered by your content
from WordPress and the dataa customer has in Salesforce.
But nobody knew what it looked like.
We had no plan.
Salesforce had the vision.
WordPress VIP had theplatform, but nobody had
built it, or even reallyknew how to build it.
And so, I did, and we didat WordPress VIP, we did
what you do when youhave a big problem to solve.
You go to RT Camp.
And you say RT Camp, can youhelp us figure out what's going on here?
Right?
And of course, RT Campgoes, sure, we can figure this out.
Right? No, they did.
They came in and you do that because anagency that understands or can think through
your problem and help you find an answeris an agency that works well in enterprise.
And so, we used to joke as wewere going through the process
that we were building theplane as we were trying to fly it.
Have you heard that saying before that verymuch felt a lot like what we were doing?
And I didn't really needRT Camp to build a website.
Did I? Right?
Like that wasn't the actualproblem I needed to have solved.
I mean, we did build a websitebecause that's what you do.
But it wasn't actually about web design.
It wasn't about features in WordPress.
I didn't come in andsell me on, you know,
like performance orCMS, anything like that.
That problem had already been solved.
What I had was a totally different problem.
And it was something thatwas about content, right?
How it becomes structured data thatpowers AI context and agenda workflows.
What does it mean when an AI agent isconstructing the experience in real time?
It was about data, it wasabout content and intelligence
and what could happen whenyou bring them all together.
I want to show you a littlebit of what we built together.
Is it demo working? Whoa.
Take a look at this.
So this is a little micrositethat we built together.
So RT Camp is an agencythey work with one of our
customers at WordPressVIP called Cox Automotive.
And it was a mutual customer client of oursas well as a mutual customer of Salesforce.
And so we had thisreally unique opportunity
to do something coolwith Cox Automotive.
And they came in asour guinea pig to test out
this idea that we hadaround adaptive websites.
And so this is amicrosite for them for an
event that they go toevery year called NADA.
It's a big show for people who sellcars and the products around selling cars.
And so we built thislittle microsite for them.
And what we did was we connected theirWordPress website content to Salesforce.
And then from Salesforcewe brought that into
agent force, theiragent take experience.
Connected it to Salesforce'sintelligence that they
have in their CRM systemand what they have about users.
And then we let the AI do the workof figuring out what to show the user.
So let me show you a littlebit of what this looks like.
So here on the siteI've got this chat open.
And we're going to askabout a service here.
So tell me about digital retailing.
And right away you can seethe web page is actually adopting
and changing based on whatI have written into the prompt.
Right.
Fully adapted here.
It's now telling me aboutdigital retail products.
I can take a look at someof these different options.
I'm going to click on Kelly Blue Book here.
And the page changes again.
Now what you may not understand is thatthis is actually being delivered by AI.
So as I click through, thepages are being constructed by
AI, by agent force, toenable us to be able to do this.
So I can see a little bit of informationhere about Kelly Blue Book.
That looks great.
But you know what?
It's not actually enough.
I need to know a little bit more.
Let's dig a little bit deeper here.
So I'm going to just say why KBB.
What's dig deep?
Great use of the English language as well.
Why KBB?
And as you can see herethe page changes again.
And it's even more depth, more knowledge.
And what's going on behind thescenes here is that we've actually
taken all of the content thatexists on a WordPress website.
And we have brought it into the Salesforcedatabase ecosystem called Data360.
That data is then made availableto the agents as we talked about.
And it's taking it and it'sre-rendering it in a way
that is specific to whatthe user is looking for.
So here we are.
We've got this page.
Let's push this a little bit moreand see if we can do something else.
How does it compare to competitors?
Let's see if that does.
Whoa, okay.
So now we're actually gettinga comparison table here that
shows us the difference betweenKelly Blue Book and competitors.
Right? Very good.
I am a buyer and I'mlooking to figure this out.
I'm not able to get this information.
But look at what's going onhere in the chat as well because
this is something that'sreally important in enterprise.
Look at the questionthat's being asked here.
We'll have KBB experts atNADA at the specific booth.
I've got all this informationthat I can send you, right?
A digital retailing success guide.
KBB integration case study.
NADA session schedulespecific to digital retailing.
So one of the most, one ofthe holy grails, if you will, or the
biggest goals that enterprisewants to achieve is personalization.
If you ever want to win anenterprise contract, tell them you have
solved personalization and that'llget you at least a conversation.
But what's happening here isthey're starting to ask me now.
Would I like to send, wouldyou like me to send these to you?
So the agent is askingif I want to receive it.
We know what, it's specificenough to what I want.
And because we've built trust togetherthrough this, yeah, absolutely send it to me.
Yeah, yes, please send.
Perfect. I'll email those to you right now.
And here's the magic question.
What's your email address?
Why is that question so important?
Because what this is doing is somethingcalled progressive de-anonymization.
And what that means is throughnatural language, not a form,
it's starting to pull informationabout the user into Salesforce.
Where that can become a lead, thatlead can then be put into a segment.
They can be re-marketed to.
They can get emails.
They can get sent to Sales Associates.
Or sales, what they calledAEs, right, account executives.
So they can follow up andsell them the software or
the service or whateverit is that they have to sell.
Perfect. All right.What's your work email address?
Well, let's say it's Sarah. Chen.
Lincoln, the city, Ford.com.
Awesome. So sent.So check your inbox in a moment.
Now to personalize yourNADA experience even more,
can you tell me yourname and your dealership?
Again, progressive de-anonymization. Sure.
All right. My name is SarahChen, and I work at Lincoln Ford.
And once again, we have more going on here.
That doesn't just sayyour schedule is ready.
It's a Sarah. Yourschedule is ready.
How cool is that?
We're able to see exactlywhat happens when an
agentic website isworking the way it works.
And all the kudos for this, allthe credit goes to the team at RT
Camp who understood the problemand came up with an answer for us.
You can go and switchback to the slide deck here.
Think. There we go.
So this adaptive website thingis a really exciting example of
what's possible when agencies,platforms, and customers get together.
And often in enterprise, this is the kindof challenge that we are asked to solve.
It's not just a websitechallenge, but it's how the website
unlocks and solves other problemsand delivers other outcomes.
And we're just scratchingthe surface of the kinds
of challenges thatenterprise customers face.
Like I said earlier,personalization is a big one.
Content governance is a big one.
AEO, GEO, whatever it'scalled today is another one.
Bot traffic is a big challengefor a lot of media customers.
AI enhanced editorial workflows.
These challenges areeverywhere in enterprise right now.
And if we keep trying to proveWordPress based on features, we're
actually missing the deeper problemsthat enterprise is trying to solve.
So I want to ask you a question.
What is your agency's solutionfor these kinds of problems?
How are you thinking aboutdigital asset management?
What about data? Do youhave opinions on where
AI fits best in enterprisecontent workflow?
How are you helping enterprises fitWordPress into the AI stack of the future?
These are all real questionsthat enterprises are asking today.
A couple of weeks ago, I wasat a customer on site, which is
where I go and I hang outwith a customer in their office.
And you want to know what they saidto me? They said, we have got 1,500
cloud code licenses that we've givento all of our team across the company.
But we need to figure out is how to make cloud code work withWordPress in a way that allows our editorial teams across eight or
nine different brands work together seamlessly so that they canget content into WordPress, go through our compliance workflow.
And then on the other side ofthat, we've got content on a website.
I mean, that's justthe kinds of things that
they're thinking throughand trying to figure out.
You need to have an answer.
You don't necessarily needto have a finished product.
They're not asking you to come with asolution already prepared and ready to go.
But you do need to have a point of view.
And you need to have a willingnessto engage with the problem.
That's what gets you in the room.
It's not proving WordPress, right?
Having an opinion aboutwhat WordPress makes
possible, that's whatgets you in the room.
See, what happens whenmore WordPress agencies
are solving problemsbigger than a CMS?
What happens when aWordPress is the foundation
for bigger, more complexenterprise problems?
What happens when westop proving WordPress and
start proving whatWordPress makes possible?
Imagine if WordPress agencieswere the first call for these
problems instead of somethinglike Accenture or Deloitte?
I don't believe AI is replacing WordPress.Full stop.
I actually think it's makingWordPress much more valuable,
more malleable, moreobvious to enterprise buyers.
This is the most incredible time and seasonfor open source that I have ever seen.
And you know what the flag bearerof open source is? It's WordPress.
Our whole ethos is that we areopen and we work with everything.
Enterprise needs andopen, intelligent content
experience platform thatcan move as fast as marketing.
That can move as fast as AI.
And partnerships matter more than ever.
The Asian force projecthappened because of partnership.
VIP Salesforce, RT Camp, Cox.
None of us did this alone.
It was only becausewe were able to come
together and worktogether that it was possible.
Now, if this is something thatyou're serious about, like if you really
want to explore what it looks liketo solve these kinds of problems,
I want to encourage youto come and hang out with
us at the A4A boothover in the sponsor area.
Because we're serious about partnership.
We're serious about working withagencies that want to solve big problems.
My name is James and I work with theworld's biggest brands at WordPress VIP.
Are you ready tojoin me? I hope so.
I have a question about the demo.
All right.
I was pretty amazed.
Can you share a little bit of technicalinfo on how that was working?
Why did it feel so fast?
Was everything local?
Was the model local?
Was the data local?
What can you share?
Cheeky questions.
So that was a demo inthe fullest sense of the term.
It was a proof of concept.
But the underlying technologyis all real and it all works.
But for the sake of not wanting tohave any technical hiccups, it's all local.
So basically how this works is, and Rahi,who actually helped build it, is here.
Rahi, right here.
Rahi helped build it.
So you can give him a round of applause.
Because this is his technicalmasterpiece from RT Camp.
And basically how itworks is, Salesforce has
the ability for you to createa connector in Data360.
And what we've doneis work with them to build
that connector to be able tosee and read WordPress content.
So if you are a Salesforceuser, you go into Salesforce.
And you select the WordPress connector.
It looks at the REST APIand pulls content in that way.
You can actually selectposts, pages, different
types of things in apipeline that you bring in.
And you can set it up so that youcan watch that content over time.
Now this is reallyimportant for teams that are
working with big, a large amount ofcontent, because it's always changing.
It's always adapting.
And so it's really, reallybeneficial when you
are taking that dataand making it available
to agents that you alwayswant to have the most
up-to-date version ofthe content possible.
And so in other systems, you might haveto do timed or scheduled imports, right?
And those might fail regularly.
And so this system actuallyis a lot more asynchronous
and it allows it to happenin a much better way.
And so the contentcomes into Data360 into
their VectorDB RAGsetup that they've got built.
Normally, if you were to dothat without the connector,
you would have to set up your own pipeline,figure out how that's all going to work.
Set up both sides of that and thenmake sure that they can come together.
That's probably goingto cost a lot of money.
It's going to require six months of work,but because we worked on this connector,
it's a lot easier for enterprises to doit and it saves them a lot of money.
And that's great for them.
It gets WordPresscontent into the database.
And then from there, if you'refamiliar with Salesforce and Agentforce,
they have a whole system whereyou can actually design agents.
And you can decide what datasources they have access to.
You can help them figure out and train themon what kinds of questions they can answer.
One of our early demos, weactually had a movie website
where we had brought in somecustom post type with movies.
And that went into the agent and the agent.
You could ask the agent aboutdifferent what movies were on the website.
And it would pull it upand it would give you links
and send you off to itand do different things.
So it's really, really great.
But what's really coolabout this is once the content
gets from your WordPress website into Data360,it's not just available to Agentforce.
It's also available to everythingthat Salesforce has available to you.
So that's part art for email.
Marketing cloud next that theyrun a bunch of other services.
And so all of a sudden, you now havethe power of all of your WordPress content
that you've been investing in for years andyears and years available to be able to use
any way that you want.And if you are a marketing
executive, if you are workingwith a team of marketers
and you are building many segments andrunning many campaigns all at the same time,
that kind of flexibility andthat kind of opportunity,
leverage your content in a bunchof different ways is really great.
And then when you add AIon top of it, that can actually
use that content to buildthose campaigns autonomously.
And to do that kind of workautonomously, it's an incredible level up.
So that's a little bit ofthe technology around
it, probably a bit moredetailed than you wanted,
but there you go.
Any other questions? Anything else?You can ask anything.
Yeah, go ahead. Microphones there.Very excited to answer.
We've got a few minutesleft, so this is good.
Yep. We have.
Hi, my name is Driland I work at Artigam.
I'll be digging thisup with Raheel a lot
later, but I wanted toinquire about security.
So enterprise has a lotof concerns with security.
And since this deals with AIand it is still kind of a black box.
So what goes in AI, what comes out of AI?
How do you ensure or canyou expand on the security
guardrails on this connectorthat you demoed? Absolutely.
A very big thing that happens in enterpriseis that they're very risk-averse, right?
And so everything that we cando to de-risk something matters.
Now, the nice thingabout this setup is the
agent experiencesactually inside of Salesforce.
And Salesforce has worked reallyhard to build in its own set of guardrails.
It's actually developed itsown pseudo-language for
agents, where it buildsdeterministic pathways in
and really is able to lockdown the kinds of answers
that are possible forthe agent to actually give
and tries to make itpossible for the agents -- well,
tries to force the agents to give thesame answer over and over and over again.
And because of that,it's much more palatable
to an enterprise thatis risk-averse than, say,
just giving it cloud code under the hoodand saying, "Cloud, go run into your thing.
" So there's a lot of extraconstraints and things
that go into that toensure that it's protected
from prompt injectionsand a lot of other
things that couldpotentially happen as well.
And then on top of that, if you'reworking with a platform like WordPress VIP,
there's lots of othersecurity things that
happen there as wellto sort of support that.
And lots of cool stuff that we'rebuilding, I could tell you all about it.
But that's a differenttalk. That also helps
enterprises really feel confident andcomfortable with AI in a WordPress environment.
>> Thank you. Thank you for your question.
>> Action here.
I run an agency andwe do some WordPress
work also, but we alsowork on Ruby on Rails.
>> Oh. So I think thisis probably related to the
question that was asked bythe RT-CAM team member.
One of the, we alsowork with some enterprise
customers, but that's moreon the Ruby on Rails side.
But one of the primary concerns thatthey have had is using open models to,
even if we are buildinga specific model on top of
open models, they are notvery comfortable with that.
And we have actually gonedown the route of getting
a GPU on digital oceanand training it from scratch,
which is expensive takes a lot of time.But is this, can you also expand a shell,
some of your insights on how you havebeen able to manage that at WordPress VIP?
>> That's a good question.And I think it's really dependent
on the risk appetite of thecustomer and the specific use case.
One thing I will sayis the worst model you
will ever use is themodel you're using today.
Because every day they are gettingbetter and smarter and more capable.
And the model that we'reusing, the models we're
using now like Opus4.6 is incredible, right?
Especially when you think back toeven a year ago and where things were at.
And I think what's happeningis over time what I am
seeing at least is, youknow, this time last year,
there were, like, legal teams were like,you can't use our content for anything.
We don't want you havingany AI processing at all.
There was a lot of fear and,like, legal constraints on it.
And as we're going through renewalseason with a lot of these customers
this year, we're actually seeing alot of those restrictions get lifted.
And in fact, we're hearingstories of, you know, Claude, like,
just vanilla Claude being usedin our customers that last year.
We're, like, highly restricted and didn'twant anything to do with them. And so I think
what's happening is it's less, it's less aboutworrying about which models are being used.
So much as it is, that just generallyacceptance of AI and that AI
makes mistakes is that peopleare becoming more tolerant of that.
And they're leveraging disclaimers, right?And things like that to support things.
But they're also being reallycareful about the use cases.
So we're not seeing a lot of transactionalthings at enterprise level, right?
Which might be more of aRuby on Rails type experience,
but we're seeing a lot moresupport related agents, right?
So they're, they're leveragingit for customer support
questions and queries thatcome from documentation.
They're using it for operationsthat may be on the back end dealing
with their internal teams as opposedto customer facing applications.
So that tends to be where it's starting to go. Andas they gain confidence and as the models continue to
get better, I think we will start to see more, like,appetite for a little bit of extra risk around it.
Somebody at some point isgoing to take a step forward.
And what we are hearingfrom a lot of enterprises
is that we don'twant to be left behind.
The other thing you have to remember isthat an enterprise, everything is slower.
So they're talking now aboutsomething they're going to
release next year or 18 monthsfrom now or two years from now.
And so that's just because it takes them that long to get everythingin order to go through compliance, to go through purchasing
processes, to get the technology system and stack that they've builtall working together to deliver the kind of thing that they want.
So because it's more complex and there's all theseother layers that they have to think about, they're
recognizing that, yeah, in a year or two, the modelsare going to be way, way, way better than they are now.
Hopefully, we'll be in a place wheresomebody has solved this already.
And we'll be able tolaunch on time with what
we think we're goingto be able to launch with.
So that's probably the best wayI can answer that. I don't know if
that's helpful, but that's at leastwhat I'm hearing and seeing.
Thank you. Great question. Thank you.
So another one in the back here, point out.
Yeah, this a place from Goilevel.
It's a CRM tool for agenciesand businesses worldwide.
So I'm pretty intrigued with the adaptivepage builder in the website, right?
I wanted to know, like,what is the underlying
page builder thatyou're using for it?
And kind of like, do you have,like, set templates that the year
uses over time to kind of generatethe pages based on the prompt?
So I'm going to let you in onsome secret information here.
So, because this is a placewhere I want to see this go
as opposed to where maybeSalesforce was to see it go? Yeah, yeah.
Salesforce with AgentForce, they actually
have a whole templatingsystem that they've built.
So one of the thingsthat Salesforce has to
think about is theyhave to be CMS agnostic.
So the adaptive websites experiencecan't just work for WordPress.
It has to work for site coreand Adobe Experience Manager
and some of these otherplatforms that are out there as well.
HTML or React or Headless, right?Whatever you've got.
And so because of that, in order tomake this work, the initial application
that they're looking at is almostlike an overlay of your website.
So it would be templatesthat you pre-build with hotspots
in it where you would putcontent and you would put images.
And those images would changeand they would adapt, right,
as the page changes or thequery changes from the user.
But where I see the potentialfor this and where I think
my friends and compatriotsover at RT Camp, see it going.
Or the question they're asking is,well, what if we didn't have Salesforce?
Could adaptive websites besomething that WordPress just does?
Could we leverage theexisting Gutenberg WordPress
editor to be able to do thesame kind of templating?
What would it look like if we couldget the same kind of technology
or the same kind of applicationout of what WordPress already does?
I think they're on the way todo that. Which is really cool.
I might say thingslike a secret. I'm sorry.
But this, to me, when we think abouthaving answers, this is having an answer.
This is what WordPress making thingspossible that aren't currently possible.
And this is what I love aboutthis community and where we're
going and what AI enables usas an ecosystem to be able to do.
Because Salesforce is stuck withSalesforce ways of working. We're not.
We can literally doanything and try anything
and see where WordPresstakes us. It's awesome.
So, yeah, thank you.
[BLANK_AUDIO]