►
From YouTube: CMS Content Migration working session
Description
Tyler Williams and Lauren Barker's first working session for content migration of Agile Delivery topics page to new Netlify CMS template. This resulted in identifying bugs in the content type configuration that need to be addressed before additional Digital Experience team members assist with other topic page content migrations.
A
B
B
So
hopefully
this
kind
of
illustrates
what
I
mean
by
that,
where
netlify
cms
like
lives
on
top
of
the
files
in
the
repository
in
this
project
and
we're
going
to
move
this
content
into
a
file
that
netlify
cms
expects
to
exist.
And
then,
when
you
do
your
stuff
through
netlify
cms,
it's
just
modifying
that
file
for
you,
and
so
this
is
just
some
good
exposition
to
understand
a
little
bit
under
the
hood
that,
like
the
same
workflow
of
content
creation,
editing
is
happening
there
just
with
like
a
nicer
tool.
B
So
hopefully,
that
makes
that
clear
and
gives
you
a
sense
of
like
where
things
are
and
if
things
break
for
you
or
if
you
run
into
challenges.
Maybe
this
will
also
give
you
some
idea
of
like
where
to
look
first
right
so
that
it's
not
just
like.
Where
does
my
content
live?
Where
did
it
all
go?
So
I
think
that's
that's!
B
The
first
thing
you
know
stick
around
and
watch
some
of
the
technical
details,
but
then
for
folks
looking
for
to
dive
more
into
like
the
development
work
on
netlify
cms
and
the
tools
we're
building
out
for
the
content
creators.
I
think
really
the
the.
Why
here
is
that
we're
taking
existing
content
which
lives
in
a
variety
of
different
formats
across
the
repository
or
normalizing
it
into
a
way
that
netlify
cms
can
consume.
B
A
B
A
B
B
A
B
B
A
B
B
C
B
B
A
B
Excellent-
and
I
can
just
I
can
probably
just
copy
paste
from
here
right-
that's
going
to
be
the
easiest
cool,
so
I
guess
this
is
also
good
for
me
and
for
other
folks
who
are
going
to
be
doing
this.
So
title
is
just
our
header
here,
right,
cool
and
then
do
we,
it's
probably
easiest
to
get
into
from
the
source
for
the
seo
description.
B
C
B
A
B
A
A
B
A
B
A
B
A
Is
new,
so
it
goes
into
a
new
section
called
benefits,
so
you
can
delete
the
h2
in
the
body.
Oh,
I
see
yep
and
then
we
have
a
new
field
down
here
for
benefits
and
we
will
add
each
one
of
these,
and,
oh,
I
see
add
the
title
description
and
then
for
the
image.
For
now.
I
think
you
can
just
use
a
relative
link
to
that
image
and
we'll
need
to
configure
so
that
those
icons
show
up
when
you
click
on
choose
an
image,
but.
B
C
A
B
A
A
A
D
C
A
B
A
B
I'm
saying,
as
you
can
see
before,
I'm
so
spoiled
the
the
like
get
lab
like
editor
in
mrs
and
issues
has
that
nice,
like
auto,
like
if
I
highlight
something
and
I
hit
like
an
open
bracket,
it's
like
cool.
I
know
you
want
an
end
bracket
on
your
highlight
selection.
It's
like
I
know
that
you
are
a
developer
and
I
always
I
always
miss
that
in
places
where
I
don't
have
it.
B
B
A
A
A
B
A
A
B
C
B
As
another
piece
of
like
as
we
get
like
on
a
related
note,
as
we
do
these,
I
know
they're
we're
doing
a
large
batch
this
week
in
the
next
week,
and
it
strikes
me
that,
like
we'll,
probably
have
to
make
a
couple
choices
like
this,
where
we
may
move
things
around
these
things,
I
imagine,
are
going
for
review
with
whoever
owns
the
content.
Is
there,
like,
I
guess
like
do?
A
I
think
some
pages
are:
it's
gonna,
be
a
quick
migration.
Okay,
so
the
goal
is:
get
the
initial
migration
out,
get
that
review
app
up,
so
you
so
we
can
hand
over
that
review
app
to
the
content
team
and
they
can
take
a
look
at
the
new
page
and
they'll
supply
us
with
edits
to
there's
a
resource.
These
resources
should
actually
be
suggested
content
right,
but
this
initial
migration.
B
Good,
it's
not
far,
I
feel
like
you
know.
This
is
all
somewhat
straight.
It's
one
of
those
things
where
it's
like
on
its
surface
you're
like
yeah,
that's
really
straightforward,
but
it
would
be
very
understandable
if
someone
else
had
a
different
perception
and
thought
that
and
like
wanted
something
much
more
specific
right.
C
B
B
B
A
A
C
A
B
B
B
A
B
A
A
B
I
think,
hopefully
too
we're
kind
of
deep
in
the
video.
So
who
knows
who's
made
it
this
far,
but
hopefully
this
video
can
be
useful
for
content.
Folks,
we
work
with
so
they
can
get
a
sense
of
like
where,
like
what
we
did
right
and
so
like
when
they're
giving
feedback,
they
can
understand
like
what
we
had
to
make
choices
about
and
like.
B
A
B
B
A
B
Wow
it
feels
like
lose-lose.
It's
like
it's
like
either
adding
more
stuff
to
the
repository
or
having
to
search
through
the
whole
thing
I
feel
like.
Perhaps
we
should
find
and
replace
right,
okay,
oh
here's!
The
question,
though
so
I
think,
find
and
replace
is
right
because
then
we
don't
add
more
stuff
to
the
repository
and
we
get
things
where
we
probably
want
them
to
go.
B
Yeah
I
just
I
was-
I
was
wondering
if
it
if
it
makes
sense,
it
looks
like
it's
only
used
in
like
what's
going
to
be
cmsible
anyways
but
like
I
was
wondering
if
it
still
made
sense
to
have
duplicates
because,
like
some
places
referenced,
it
that
were
not
like
part
of
like
like
didn't,
want
to
be
using
it
as
the
cms.
But
I
see
now
that
that
is
not
the
case
here.
So
cool
yeah
we'll
find
and
replace
this.
That's
not
bad.
It's
like
three
instances
cool,
so
I
am
moving
source.