Subscribe
Share
Share
Embed
Beyond the CMS is about content operations and the future of content: how enterprises create it, scale it, and get it found by people and AI. Hosted by Chris Bryce, Partner at Dotfusion, the show has just passed 50 episodes of conversations with the people building that future.
It started as a show about CMS platforms, and that conversation never stopped. Guests have come from Contentful, Storyblok, Agility CMS, Squiz, Bloomreach, ButterCMS, StreamX, BILDIT, CrafterCMS, React Bricks, and Magnolia, talking through what headless and composable architecture actually gets you. But the range has grown well beyond platform comparisons. Recent episodes cover Answer Engine Optimization (AEO) and how AI search engines decide what to cite, MCP (Model Context Protocol) servers that connect AI agents directly to a CMS, agentic content operations workflows, accessibility, and what it takes to govern content at the scale of a university managing tens of thousands of edits a week. Episode 50 brought on Olivier Dobberkau of the dkd/TYPO3 Association to dig into semantic search and retrieval-augmented generation (RAG).
The CMS is still the hub. It's just not the whole story anymore. If you're a CMO, IT Director, or Chief Digital Officer trying to figure out how your content gets made, published, and found, by people and by AI, this is where those conversations happen.
#contentoperations #answerengineoptimization #aeo #aisearch #headlesscms #contentful #storyblok #agilitycms
Speaker 2: Um,
Speaker: All right We are live.
Welcome, uh, welcome everyone
who's taken a moment of their
day on this beautiful Thursday in
Toronto, Eastern Time, lunchtime.
Uh, and for anyone else joining in other
parts of the world or in the future,
uh, we hope you get a lot of value
out of the conversations we have here.
Um, if you are tuning in live, we do
have the technology to see questions
that are posted on LinkedIn normally,
uh, and we'll do our best to answer
any questions you might have.
If you're watching this in the future on
YouTube, I do kind of monitor the comments
there as well, and always happy to share.
Um, the whole idea behind
this podcast came from like
listening to The Car Guys on NPR.
. And it was really cool…
And then like, "The carburetor's
broken," and these guys just knew
how to like kind of fix everything
or talk about the concepts.
And I, I like that idea of a kind
of down-to-earth discussion, uh,
moment in time to talk about content
platforms, the future of content itself
from thought leaders in the industry.
And we have one of the great
thought leaders in the industry
joining us today, uh, Joyce Peralta.
She's the manager of digital
communications at McGill, uh, in Montreal.
Thanks for joining.
Speaker 2: Thanks Chris.
I'm really happy to be here today and
excited to have this conversation.
Speaker: Awesome.
Um, we, we were just chatting before
we turned the show on live, and your
comment around the velocity that things
are changing struck me when I was
thinking about the name of the show.
Speaker 2: Hmm.
Speaker: So three years ago, when we
started Beyond the CMS was a little
bit more about forward future thinking
outside of the platforms itself into what
will the world be like in the future.
Um, and you had- Mm-hmm … a really
great kinda starting conversation
point around it's not so much really
about the platforms or the tech but
it's really focused on the content.
Um, maybe a great way of starting
things off is just to ask you to kinda
describe a day in your life and what
are some of the projects you're working
on in the greater concept experience?
And um, go from there.
Speaker 2: Fantastic.
Uh, well our, our team at McGill, our
web services team, is comprised of
actually two teams in the background.
Half of our team is in IT and they're
our developers, and the other half
of the team, the team that I sit
on, is the communications team.
And our two teams together work to
both provide a platform for people
to build websites at McGill with
central platform, uh, with a template
and with, uh, some resources and
train- training attached to it.
Uh, and also all of the support
that's required to help people build
great websites using that platform.
So, uh, we, uh, provide, uh, we
write articles, we have community
events, we provide consultation
support, and we also define the
standards for our digital spaces.
The, the standards and,
and the governance.
So we work with, um, contacts from
across the university because we're
not the people necessarily that, uh,
come up with i- information security
rules or- Mm-hmm … uh, requirements
for accessibility or brand usage.
But we bring all the people together
across the university who manage
those best practices, and we produce
resources for how those best practices
need to play out on our websites.
So that encompasses a lot.
I think that was a, a summary.
Yeah.
But hopefully that kinda
answers your question.
I … It's not exactly day to day,
but kind of big picture, I guess.
Speaker: Yeah.
So is it safe to say that to some
degree you're kind of responsible for
the content and the model supporting
that content for the entire university?
Is it…?
Speaker 2: Yes.
Okay.
Well, our, our web services team is.
And- Yeah … I, I think that's
an interesting distinction to
make, 'cause when you're talking
to me I'm, I'm in communications.
But IT and our IT side of our
team is also a very important
part of this- Mm-hmm … equation.
And, and we talk about
ourselves as a unified team.
So our, our unified team, yes, we are,
are responsible for those things: for
providing the platform, for providing
all the resources that are needed
to create and deliver great content.
Uh, but yeah, I guess the important
distinction is it's not … All
of that doesn't sit in one team.
Hmm.
And it actually isn't limited
just to our teams either.
I think the real strength of our
governance and our standards and our,
our processes is that we work to produce
our, our resources for governance and
our resources for content creation
in a federated manner with input from
departments across the university.
So, uh, for example, we'll work with our
equity team and our translation team.
And so w- This isn't a sense of
just one department dictating what
i- what is the way to do things.
It's really just, uh, an idea that we're
bringing all of the different subject
matter experts across the university
together so that we are collabority-- co-
collaboratively producing- Hm …. uh, I
think resources and guides and the tools
needed to create great visual experiences.
Speaker: Super cool.
I think, um, in our kind of c-
pre-show chat, you had mentioned that
some other universities or higher
ed institutions reach out and just
kind of wonder, like, "How are you,
how are you doing all of this?"
And something that seems to me smart
and important is this collective nature
of comms, IT, extended teams overall.
Can you share a little bit about
your vision for the, I guess you'd
call it migration, transformation
Speaker 2: Well, sure.
So yeah, I think a lot of people are
talking about transformation these days.
And initially when we s- when we started
down this path, I think there was a
lot of uncertainty about what this
transformation was going to look like.
But I feel like we had a good base to
start with because we've worked so hard to
produce this, these foundational resources
and this foundational, uh, governance that
has buy-in from across the organization.
Mm.
So, uh, because we had processes in
place for working with our community
to transform our best practices and get
feedback about how our best practices
are working, when we started to talk
about this content model project- Yeah
and restructuring of our content, possibly
re- you know, a restructuring of our, our
platform, I think there was … It was a
lot easier to get buy-in, uh, initially
because people had trust in, uh, you
know, the fact that we were going to,
to do this in a way that would involve
voices from across the community, that
would produce a, a plan, that would
consider input from different departments.
Mm-hmm.
Um, and I think that that is
a really important base to
start the transformation from.
In terms of where we're going
with the transformation, I, like
I said, we're, we're real fans of
doing things in an iterative way.
So in terms of where things are going to
end up, there's uncertainty and ambiguity.
And I think this comes up at a lot of
conferences, is this conversation about,
you know, if, if somebody's telling you
they know how this is gonna turn out,
then you really have to ask yourself
if they're s- Hmm … you know, if
they're trying to sell you something
or if they really are being realistic.
And I think that's something that we're,
that, that we sh- should acknowledge.
I, I … We have a, you know, a sense
of what we need to do and the problems
that we need to address in this moment.
But how things are gonna play out
eventually, there's, there's some
uncertainty there- Hm … because
the way people are using our
platforms and are interacting with
their content is evolving right now.
Uh, so I think that eventually we're
going to end up, um, in a place where
there's gonna be a very different way
of- Mm-hmm … us creating content, of
managing content, of delivering content.
But exactly what that looks like
now, um, we're not sure about.
But I can say we're recognizing that
in order to make that transition, we
really need to have very structured
content production workflows.
We need to have a very structured
way of storing our content, and we
have to have Platforms that allow us
to deliver content in multiple ways.
Uh, so that's where we're at right now.
We're making, uh, we're putting
a plan in place to make that
content transformation happen.
Speaker: Interesting.
Um- Just taking a step back, 'cause some
of the folks who w- will be listening to
this now or later are not from higher ed.
Can you just talk a little bit
about the, the depth and breadth
of what you're dealing with from
like a taxonomy perspective?
Mm-hmm.
I, I, I wandered around some
higher ed websites myself but it's-
Right … like how do you even
organize a user journey in all of that?
Speaker 2: It's true.
It, they're very large environments uh,
from a, a content scale perspective.
And also historically it's been
at, um, an ecosystem where we
have a, a decentr- that's managed
decentral- in a decentralized way.
Um, and that's partially because of
course in higher education we value
independent thought and autonomy.
So historically all of our departments
have had the ability to, uh, and, and
have, uh, managed their own content, and
that's meant that even if they followed
If they followed a really great
practice of doing user research
and designing a solution that is
specific for their department, that
they've produced something that
likely isn't similar to all the other
departments across the university.
Sure.
So what we have is hundreds, maybe
thousands of different content
models across our organization.
So we have a thousand websites on
our central platform at McGill.
Oh my god.
We have another 500 custom websites,
and we have internal platforms, uh,
s- services running in the background.
Some of them interface with
our public, um, websites.
So … And all of those different, uh,
you know, uh, websites and, and platforms,
they might potentially, they do have
individual content models, um, and,
and in- individual content structure.
And right now there's a lack of
connection, uh, between those, those
different, uh, content structures.
So what it means is if people try and
navigate our content as a whole, which
is how people interact with our content.
They don't just come to one website
and just stay on that one website.
They'll go from website to website
as they try and complete their tasks.
What it means is every time they land
on a different website, they're faced
with a different content structure,
and they have … And sometimes with
different information that contradicts
the last website that they were on.
Speaker: How
Speaker 2: do you keep your
Speaker: hands wrapped around everything?
Speaker 2: Yes.
Yeah, yeah.
So that's, uh, I, I think that
maybe gives you a picture of, of
what, uh, the current situation is.
We also have … You know, we
have all those websites and,
and different, uh, platforms.
They're also constantly being
updated, so on our central Platform,
our central public web platform.
We ha- we- we're tracking 6 to 8,000 edits
per week happening on those platforms.
So they're constantly,
um, evolving as well.
The content's constantly evolving as well.
So there's a lot that we need to
consider in making this transformation.
Um, and I think part of it is recognizing
also that this has happened because
we've never considered having a, a s-
a content structure for the university,
and that has left people to, of course,
follow their own best practices when
creating their own website solutions- Mm
web solutions.
So this is nobody's fault.
It's just that maybe it's our fault
'cause we're the team that provides-
Hm … the central resources.
But we never had this, we've never had
this conversation in the past in terms of,
you know, what should … What, what does
our, what does our domain model look like?
What domains do, do we talk about?
Uh, you know, how should that
information be structured?
Uh, we've never had that conversation.
So, so yeah.
Speaker: In, um … And I'm making
some assumptions here as I try to
understand the different properties,
but an example of that might be, like
a website for a particular department?
Hmm.
That would be o- oh, the right
way of thinking about it.
And Department A may have a
fundamentally different mandate of
communicating than Department B.
Thus, it's almost like there's
this calibration that you're
architecting that uh, acknowledges
keeping things open right?
Yet having a model, which is a little
bit contradictory at the same time.
And it looks like you're trying to
figure out that balance through an
open dialogue and feedback through the
communities of property owners and users.
And it's quite an interesting dynamic
of, of what you've got going on there
Speaker 2: Yeah.
That- Do you- That, that's it exactly.
So as we've been working on this content
model project, we've been talking with
different departments to identify what
are the types of content that we talk
about, and what terminology do we use
when we're talking about that content.
So as we worked on the … Uh, as
part of the project, we talked with
about 50 subject matter experts
across the university about how they
structure content on their websites.
And, uh, as an example, uh, two of the
types of content that we talk about a
lot are, of course, programs and courses.
At a, at a university that's, uh,
you know, not, not a surprise.
But one of the surprises is we
use for program components s- we
counted 61 different terms that
people use to describe program
components across their websites.
So on one website it
might be specialization.
On another site they m-
it might be called track.
On another website it might be called
option or it might be called area focus.
Mm-hmm.
So as people go from, for example,
a prospective student goes from
website to website, they're trying to
identify what program they want to,
to be-- to register for, to apply for.
They have to figure out every time
they land on a, you know, on a, on a
p- different website, what are they
calling the program components - Mm-hmm
on this website?
Um, and that's, that's what's making
it really difficult for people
to navigate our content, for our
content to be navigated as a whole.
And we're seeing now with AI
its, uh … AI is really kind of
amplifying those inconsistencies
because AI, of course, also isn't
able to distinguish between- Right
w- w- these terms that are being
referred to in, in different
ways on different websites.
So it's producing inaccurate results.
Um, and i- you know, an important
distinction there is it's not
producing inaccurate results because
the information is inaccurate,
it's because it's inconsistently
presented on different websites, and
that's what's causing the problem
Speaker: Right?
I was just thinking, uh, if you
extend that journey beyond the
experience they have on your
properties, what if I'm looking to go
to three different universities- Mm.
… all of which are using synon-
synonyms that are confusing.
What do you actually do?
It's almost like there should be
a global head of higher ed models
Speaker 2: Yeah.
I agree.
For-
Speaker: Higher ed library
that everyone can use
Speaker 2: Yeah.
For content structure- Yeah … and for, I
think design could be interesting as well.
Like a, a consistent design
system across universities-
Yeah … I think would be neat too.
You know.
Speaker: How are you factoring in, uh,
producing content also for the robots?
Is that as part of your model kind of
under the presentation layer as well?
And that just gives you another
whole container of things to manage.
Speaker 2: Mm-hmm.
So in the rollout of our content model,
we're, we're contemplating different
possibilities for improving our content
to align with the content model.
And one of the things that we were
considering was producing a separate
repository of data just for AI.
Uh- Interesting … but we've, we've
s- we've dismissed that because
we're recognizing that's just going
to elevate the governance issues
that we have, the content as, um,
synchronization issues that we have.
And, uh, I'm seeing, for example, I saw,
uh, Dreis Bitart talk, uh, recently on
his blog about how he created, uh, a
markdown version of his website for AI to
see what the difference would be in terms
of how AI crawled his website versus the
separate, uh, version of his content.
Um, and the results were very
interesting in that, uh, it showed
that the, the websites were still--
The majority of the time, the website
was still the information that
was accessed, uh, by the AI bots.
So- Okay.
So still prioritizing the
Speaker: human there.
Speaker 2: Yeah, exactly.
Yeah.
Yeah.
Which we should do anyways.
Like, like- Sure
you know, we, we-- These are problems we
should have addressed a long time ago.
I- Mm-hmm … it's interesting
that it's AI now that is making us
have this, I think, um, you know,
elevated interest in addressing this.
But, uh- Yes … I'm happy that
we're gonna address it at all
because we really should have
done this, um, yeah, a while ago.
Speaker: Are you able to share maybe
how your team is leveraging, if you
are AI, to help you, like, grasp
this huge amount of content you have?
And, you know, are you using it to
suggest thematic content models for you?
Like, how does a team even sort
through all that information to
come up with the appropriate smaller
set of models that will work across
an organization of your size?
Or are you using AI tooling
for that work as well?
Speaker 2: So in the content
model project, I used AI a lot.
Uh- Nice … so I used it, but
I, I didn't use it to generate
ideas or to provide suggestions.
I more used it to help, uh, you know,
um, process the notes that we were
taking at meetings, identify patterns
in the information that we were
collecting and the, the data that we were
collecting, uh, you know, reformatting,
um, reports and things like that.
Mm-hmm.
So it wasn't so much, uh, using AI to
help us identify the, the problems.
We, we talked to people to
identify those problems.
Okay.
But once we collected that data, we
used AI a lot to help us, you know,
sort out the information that we were
collecting and identify, um, and,
and present that information in a
way that we could analyze it and, uh,
determine what a good solution would be.
So, so yeah, I don't
know if we're using it.
We, we are considering … One of the
things that we're considering, and
it's gonna take a lot of investigating,
is using, uh, some kind of semantic
search replacement tool to update the
information across our websites But
there's a lot of questions to ask because
we ultimately don't wanna create a second
repository of information, so we are
still gonna have to update our websites.
Um, and then that if we're gonna use a
semantic replacement search replacement
tool, there's a lot of con- questions that
we have to ask about change management
in terms of, uh, you know, working with
departments to adjust their workflows
and to incorporate this, uh, semantic
search, uh- Mm-hmm … solution into their
workflows and if that's something that's
going to be acceptable, um, to people.
Uh, I think that's-- these are things that
we're, we're gonna have to talk about.
And there's also the question we're asking
about whether, uh, you know, AI i- in,
in this solution is going to be able
to draw correct conclusions across our,
across our content, um, body as well.
So we're more thinking now i- if we're
gonna do this in a very, you know, uh,
in the least risky, most thorough way,
it'll be more of a concept by concept
approach where we're working with our
departments to restructure our content,
uh, concept by concept and, uh, consider
all of the related information or
related changes that are gonna need to
take place to make that transformation.
Like what governance do
we need to have in place?
What are our-- what should
our workflows look like?
Um, what kind of changes do we need
to make to our infrastructure to allow
this to happen, um, in terms of, you
know, people creating content, the
content being stored, and then it being
delivered across our organization?
But that is gonna be a very long
drawn out uh, kind of, uh, rollout.
That I, I was speaking with our, uh,
senior developer about it and we were
thinking that approach could take years.
Uh- Wow … five years
or more potentially.
So, uh, in presenting, uh, options to our
stakeholders which we're gonna do next
week, we're gonna talk about You know,
the, the what do we wanna prioritize here?
Uh, you know, doing this in a, a
thorough way that considers change
management complications and all of
the, you know, um, different changes
that we're going to have to make from a
governance perspective, an infrastructure
perspective, capacity perspective.
Or are we gonna do this kind of a more,
you know, a, a more accelerated way?
But-
Speaker: Mm
…
Speaker 2: there's gonna be a lot of risks
I think that we might, uh, have to deal
with, and a lot more challenges, um, that
we'd have to deal with if we were going
with some kind of accelerated format.
Or they could just expand
the capacity of our teams.
Right.
That that's an option too.
We're gonna present that option as
well is, is if we want to do this more
quickly, uh, another option is get more
people on board so that we can roll
this out, um, in a quicker fashion, so.
Speaker: Very cool.
Well, um, I was listening to you
speak a few weeks ago in Montreal, and
kinda what stuck with me is the, the
pattern of openness that you and your
organization are really committed to.
Um, something that we haven't talked
much about on this show is open
source software, and we were talking
a little bit earlier about that.
Do you wanna chat a little bit about your
stack and infrastructure and some of the
pros and cons and challenges and amazing
things you've discovered along the way?
Speaker 2: Hmm.
Well, I, I can talk about it from
our content perspective because
w- we're not, I'm not on the
development team though I used to be.
Okay.
Um, but, uh, I'll say i- in
general we're … So we use Drupal.
Um, and I find that In, in this process
that we've been on, not just with
this content transformation process
that we're looking at, but even in
the past when we were looking to kind
of lay the foundations and adjust
our, our governance and adjust the
service connected to our platforms.
I was constantly interacting
with the Drupal community to get-
Mm-hmm … insights from other people's
perspectives, uh, and to take some of
those lessons, and take a lot of those
lessons actually- Mm-hmm …. bring them
back to our university, and use them.
I know when we first started doing our
governance, um, revisions, I sent surveys
out across to, across higher education
to numerous universities to get input
on what other universities were doing.
Mm-hmm.
And the majority of the responses
that we received were from the
Dru- Drupal EDU Slack group.
Um- Right … so people in the Drupal
community, um, sharing insights
on, on their governance, and how
their governance works, and how it
was reflected in their platforms.
And that is, I think, one of the
very important things, um, about
open source, that allows us to move
forward more quickly on initiatives.
It allows us to leverage the benefits
of the work other people are doing.
Uh, and I think e- on, on another scale,
i- in our university, we have a very,
uh, engaged community of practice.
And I think part of that is that
we're on an open source platform
that allows us to have conversations
about our resources and our platforms
and our tools in an open way.
We're not, you know, communicating
with, uh, like, you know, a closed
organization that doesn't wanna
have open conversations with us.
Yeah.
We can have conversations
that are very open.
And yeah, I just think there's so
many, so many strengths to being
on an open source platform, and I'm
really glad our institution is, is
part of an open source community.
Speaker: Oh, super cool.
Um Something else I wanted to chat with
you about, you had mentioned earlier that,
um, one of your, uh, great things that
you do is recruit folks and users and, uh,
different members in different communities
that might be experiencing your sites.
Um, and they provide
really amazing feedback.
What's like some of the interesting
feedback you've gotten from
your, your user feedback groups?
Speaker 2: So we have
three main feedback groups.
We have our web advisory committee,
which a lot of universities have,
and they provide feedback on our
governance and, uh, initiatives to
improve the health of our ecosystem.
We have our site manager and editor
community and our, our community of power
users, people across the units who are
very active users of our platform who
meet with us on a monthly basis to talk
about changes in the platform and what
their, um, what their thoughts are in
terms of e- you know, suggestions and
things that we can do for improvements.
And then the, the one that we were
talking about, which I really, really
love, is our student usability panel.
Yeah.
And we're in the process of
recruiting, uh, new students for the
student usability panel at th-…
We do that at the start of every
school year as the other students
graduate the previous years,
so we bring on new students.
And they're a group of students who are…
reflect the, the diversity
in our community.
So we have, uh, a number of different
audiences represented, different
programs, uh, different, um, uh,
yeah, different perspectives.
Mm-hmm.
And we bring the students together and we
have conversations About, uh, everything
from use of AI, their use of AI to
our new course catalog platform Mm-hmm
or room booking platform.
Um, or accessibility and inclusion,
how they feel about accessibility
and inclusion in our digital spaces.
And there's, a, there's a lot
of really interesting insights.
I think in particular with this
conversations, it's, it's an
evolving conversation in terms of
how people are, are interacting
with our content these days.
So we've been asking, of course,
specifically about use of AI,
um, in our student population.
And over the years that we've been
having this conversation, 'cause we
have it every year, we can see the
evolution of how student usage, um,
has changed and is changing and, and is
evolving, um, in terms of how they're
using AI to interact with our content.
And I think that's a, a really
valuable um, uh, perspective for us
to be able to, to, uh, experience.
So I'm really, really glad- grateful.
Um- Hmm … they're such a great
group of students, and I really
love … It's one of my favorite
things about, about my job- Yeah … I
think, is the student usability panel.
Speaker: That's awesome.
You, you also mentioned something
that I hadn't thought about
before, and that's, um, I think you
suggested there might be a growing
movement, um, that is kind of against
technology- Hm … like in general.
Um, AI probably pushing-
Mm-hmm … pushing that out a bit.
Um, how's that impacting how
you're architecting the future?
Speaker 2: Mm-hmm.
Well, I, I think that how that
will, will play out in our
spaces, uh, remains to be seen.
I think- Hmm … no, well not remains
to be seen, because I feel like a, a
big focus of, of everything we do in
terms of creating our governance, in
terms of creating these experiences
with our community, in terms of having
these feedback mechanisms, I think we
really try and highlight the importance
of the human side of our technology.
Uh, and I think m- maybe it won't be
something that will be a change, but
it is something that will continue
to come about, is that we will
continue to focus on this human side
of our, of our technology and our,
our, you know, what, what drives the
way that we evolve our platforms.
So for example, with this conversation
about our content model and our need
to structure content, at, at, at th-
the root is this interest in making it
easier for people to access our content.
We're not doing this for AI
or we're not doing this to
implement new AI powered tools.
We're doing this so that people can access
our content easier, whatever that means.
So we're having these conversations
and making these changes, and
they're starting with, with people,
and discussions with people.
Speaker: Mm-hmm.
Speaker 2: So yeah.
Speaker: Super important.
I mentioned this earlier,
time just whizzed by.
Yeah.
Wow.
Um, 'cause I've
got a whole bunch of more stuff to ask
you, but maybe just as kind of a parting
bit of discussion, um, we hope to attract
folks from higher ed to be listening
to this conversation in the future.
Is there, is there some recommendations
or some big lessons learned that you've
had recently that you might wanna share
with other folks that are looking to
take on a project similar to yours but
are just at the foundational stages?
Speaker 2: I, I think a big one that I'm
hearing about from other universities that
are, are contacting us is the importance
of communications and IT working together.
And I think this, this is … If, if
you're gonna do this project, I don't
think it … There is no single department
that can define this solution for the
whole university, but especially it
can't be a Communications or an IT thing.
I think it really needs to
be IT and Communication.
So I really feel like if you
don't currently have a, you know,
healthy collaborative relationship
between Communications and IT in
your institution, I think that's
a really important place to start.
And I also feel that an- another really
key aspect of this conversation is
having institution-wide alignment around
the goal of, of the work that you're
doing, um, and recognizing that it,
uh, like I just said, it can't just
be one department that is dictating
a solution for the entire university.
You really need to work, uh, to bring
the entire university together, uh,
under, I think, a single vision for what
it is that you're trying to do because,
you know, historically it's really hard
in higher education to roll out any
initiative effectively- Mm … if you
don't have institution-wide alignment.
Um, and I think this is a, a
particular one that that's gonna
be a critical, um, success factor.
Speaker: Um, and y- you had mentioned
that other universities reach out to you.
I'm assuming you reach out to them.
Is there kind of a higher
ed portal of this kind of
information that get exchanged?
How, how does someone tap into the
greater thought leadership of- Hmm … of
this modernization of higher ed stuff?
Speaker 2: Well, the Drupal
EDU Slack group is great- Yeah
if you're on Drupal.
Yeah,
Speaker: yeah.
Speaker 2: Um, but there's also, uh,
High, uh, Digital Collegium in the
States, which is, uh, a, a conference.
Uh, it's a community, um, for m- marketers
and m- marketing and communications,
uh, folks in higher education, and
PSC Web, um, in Canada, uh, which
is a related, uh, organization.
Uh, basically there's a lot
of, you know, uh, I think, uh,
professional higher education
groups that you can get involved in.
And I, I feel like when,
you know, when I go to b-
Uh, more broad conferences like DrupalCon,
for example, or Confu, they often
will have, you know, h- summits, uh-
Yeah … with conversations, uh, about, uh
… Focused on higher education, and those
are helpful discussions to engage in.
Speaker: Very cool.
Um, well we're going to wrap things up.
Uh, thanks Joyce, uh, like a ton.
Yeah.
Really, really great
hearing your thoughts.
Um, if folks are listening and wanna
reach out to you, um, LinkedIn?
That-
Speaker 2: I'm on LinkedIn, yeah.
Speaker: Okay,
Speaker 2: really great.
Always happy to connect.
Speaker: Super cool.
Thanks for your time, and, uh, thank you
to anyone listening now or in the future.
Um, we'll be back some time
in the next few weeks with
episode 49 of Beyond The CMS.
Ooh.
Um, and, uh, have a really wonderful day.
Uh, maybe just bear with me
as I end things here, 'cause I
wanted to thank you personally.
Um, but thanks everyone, and
we'll see you in the future.
Speaker 2: Thanks
Speaker: All right.
There should be some