►
From YouTube: CSM Content Migration Working Session 2
Description
Digital Experience team working session for content migration of GitOps topics page to new Netlify CMS template.
https://gitlab.com/gitlab-com/marketing/inbound-marketing/growth/-/issues/826
A
Hello
how's
it
going
hello,
I'm
laura
barker,
I'm
here
with
tyler
williams
and
we're
going
to
do
take
two
of
our
topics:
page
migration,
to
our
new
netlife
cms
template.
B
B
Specifically,
we
want
to
show
a
little
bit
for
content
creators
about,
what's
going
on
under
the
hood
in
nullify,
cms
and
sort
of
like
how
how
you
can
edit
content,
create
content
locally
using
that
tool
and
then,
but
I
think,
some
of
the
more
detailed
stuff
on
this
call
is
going
to
be
really
useful
for
the
development
team
and
people
who
are
helping
out
specifically
with
migrating
content
into
netlify
cms.
B
In
the
first
video
we
had
a
couple
bugs,
so
we
couldn't
successfully
complete
the
task
we
got
really
close
and
this
time
we
will
successfully
complete
that
task.
A
So,
like
the
the
what
technical,
what
we're
doing
we're
gonna
migrate,
existing
get
ops
topic,
page
content
into
a
data
file
using
netlify
cms
locally,
and
then
we
might
preview
the
page
locally.
If
we
have
enough
time
for
middleman
to
rebuild
and
that's
what
we're
going
to
do.
B
B
Okay,
I'm
ready
to
go
so
I'm
looking
at
here's
our
agenda
here,
but
this
is
the
issue
we
will
be
working
on
we're
going
to
be
targeting
this
gitops
page
and
get
started
so
I'm
on
master
and
the
repo
I'm
in
the
repo
I'm
going
to
pull
just
to
get
the
most
recent.
B
That
might
take
a
moment.
I've
pulled
up
our
netlify
cms
like
developer,
specific
documentation,
there's
a
markdown
file
in
doc,
and
it's
linked
out
in
the
readme
of
the
repo.
This
is
much
more
specific
to
like
folks
who
are
likely
to
be
working
with
the
code
side
of
things
on
netlify
cms.
We
will
release
a
handbook
page
specifically
for
content
editors
later
on,
but
this
has
some
useful
commands
that
I
will
be
referring
to.
So
I
got
the
poll,
and
so
now
I'm
going
to
check
out
a
new
branch.
B
I
am
for
inbound
marketing,
826
migrate,
get
ops
topic
page
to
netlify,
cms,
excellent
and
we're
on
the
new
branch
yeah,
and
so
it's
useful
to
know
that
even
with
netlify
cms,
it's
still
a
git
based
editorial
workflow,
especially
this
local
workflow.
So
we
do
still
have
to
check
out
and
commit
and
do
all
the
same
sort
of
content,
editing
things
that
we're
used
to
here.
So,
first
up,
I'm
going
to
start
the
middleman
server,
so
I've
got
to
change
into
the
marketing
directory.
B
C
B
Cool
and
so
that'll
take
a
moment
to
spin
up,
and
I
will
go
to
you
so
in
my
browser
we
can
go
to
localhost
four
five.
Six,
seven
slash
admin
trailing
slash
required.
You
will
run
into
bugs,
if
you
don't
add
the
trailing
slash
which
we
showcased
in
the
last
video,
where
I
showcased
in
the
video
with
tina
middleman
is
still
running.
A
It's
great
to
see
the
documentation
there
that
was
recently
deployed.
B
A
B
Yeah
I've
got
the
hot
corner
on
the
right
which
is,
and
I'm
like
constantly.
I
have
a
kvm
switch
on
my
work,
computer,
which
is
a
macbook
and
my
personal,
which
is
a
pc
and
the
x
button
is
in
the
top
right
for
my
pc
stuff.
So
I
always.
D
B
Up
hot
cornering
that
all
right,
we're
we're
up
and
running,
got
a
nice
little
notification,
telling
us
that
again
same
port
four,
five,
six,
seven
slash
admin-
and
here
we
are
do
we
do.
I
still
not
have
these
topic
pages.
We
would.
B
Have
seen
okay
yeah
what's
going
on,
I
wonder
so.
No
sites
marketing.
A
Yeah,
I
saw
your
comment
on
this.
It
works
for
me
locally,
but
it's
not.
B
Happening
also
look
at
the
config,
so
this
expects
it
thinks
that
it
should
yeah
it's.
It
feels
like
it's
a
something
about
like
how
it's
navigating
these
relative
file
paths.
I
also
wonder
if
oh
hey,
this
is
on
me.
B
D
B
A
B
B
No,
this
is
wow,
I
sincere
apologies
as
everyone
who's
watched
all
of
these
videos,
we've
been
making
I've.
B
Again,
apologies
and
I
will
make
sure
to
I'm
gonna,
make
a
note
to.
B
And
perhaps
perhaps
a
yarn
script,
maybe
we
just
add
something
to
the
package
json
scripts,
so
that,
like
there's
just
one
command
and
then
we
always
control
it,
and
we
can
like
ensure
that
people
are
in
the
right
directory
like
running
it
from
the
correct
directory.
Something
like
that
and.
A
Many
many
users
have
never
run
two
terminals.
At
the
same
time,.
B
B
So
now
we
can
see
like
all
this
excellent
stuff
here
in
the
topics
pages
we're
in
the
admin
panel,
and
I
am
going
to
let
you
navigate
a
little
bit
more,
because
this
is
still
a
touch
new
to
me.
Now.
A
We
are
going
to
add
a
new
topic:
okay,
yeah,
and
what
we're
going
to
want
to
do
is
probably
pull
that
get
ops
page
from
the
live
site
over
to.
So
you
should
go
side
by
side
with
the
admin
and
the
live
page
and
we're
just
going
to
cut
and
paste
that
content
into
the
admin.
A
Yeah
topics-
yeah
excellent,
cool,
great,
so
we're
gonna
start
with
the
seo
description.
This
you
either
look
at
the
code
source
or
the
generated
code
in
our.
A
Bag
yeah
and
I
would,
in
your
netify
admin,
hit
that
little
eyeball
so.
B
B
B
A
I
would
not
include,
don't
include
the
first
part.
A
B
And
then
just
forward
slash
the
first
one.
Yeah
keep.
A
B
A
Yeah
the
final,
so
this
final
url
path
is
what
the
file
name
is
going
to
be,
how
the
data
file
is
going
to
be
saved,
and
it's
also
what
that
final
slash
is
going
to
be
in
the
url.
So
for
this
one,
it's
git
ops
got.
B
It-
and
I
I
was
working
with
this
yesterday
and
like
this-
is
the
the
useful
bit
of
information
there
to
me
because,
like
for
for
different
pages,
this
is
for
the
topics
collections,
but
for
different
collections,
we're
likely
to
have
different
url
structures.
So
just
knowing
like
oh,
this
is
like
this
capital.
Url
is
what
this
value
will
be
is
useful
and.
A
B
B
Cool
then
moving
forward
title,
I'm
just
grabbing
from
the
title
here,
yeah
the
body
we
did
this
last
time.
We
did
a
link
to
we
took
this
button
and
we
turned
it
into
the
link
yep.
So
it
was
like
in
here
all.
A
And
with
the
header
the
way
this
ux
is
right
now
we
really
do
want
to
have
like
a
little
blurb
and
then
a
link,
but
we
could
just
do
the
link
for
now,
when
you
see
our
preview,
you'll
it'll,
look
a
little
wonky,
so
we'll
add
some
stuff
there.
After
we
get
the
initial
migration
done,
cool.
C
B
Excellent,
okay
and
that's
all
for
the
header
body,
correct
yeah,
cool,
really
excuse
me
related
content,
and
so
that
is
since
it's
here.
That's
these
correct!
No.
A
That
is
a
lot.
So
if
you
go
open
the
cicd
topics
page
in
another
browser
window,
we'll
see
these
related
content
links,
and
it's
in
the
header
underneath
the
more
on
this
topic
back
to
the
top.
A
A
Those
are
different,
so
if
this
get
ops
page
doesn't
have
any
of
those
header
links,
so
we
don't
need
to
add
any
and
if
none
are
detected,
then
our
template
won't
build
those
in.
B
A
Yeah
side,
rail
with
other
links,
cool.
A
Yeah
and
we're
working
with
ux
and
content
on
future
iterations
of
how
to
handle
those
cool,
excellent
cover
image.
A
Let's,
what's
in
here
in
our
topics,
page
there's
already
something
close
enough:
if
not
we'll
just
move
it.
A
B
Yeah,
it's
very
it's
I
it's
yeah,
it's
so
useful
and
then
from
here
I'm
just
copying.
So
this.
A
A
Paste
and
you're
cutting
paste
into
a
markdown
editor
here.
Don't
yeah
stop
at
the
benefits.
That's
the
next
new
block.
C
B
B
How
do
teams?
It
looks
like
an
h3
and.
A
Let's
go
back
and
do
the
the
links
in
the
content
after
this
video.
C
A
Block
styling
in
the
main
content:
oh
there,
it
is,
it's
already
block,
quoted
cool.
B
Excellent
and
then
so
we'll
go
back,
we'll
fill
in
these
links
and
it
covers
some
formatting
there
as
well,
but
we'll
do
that
off
video
and
then
benefits.
So
now,
that's
a
new
block,
correct.
A
B
A
B
B
Yeah,
let's
see,
if
collaboration
does
what
I
thought
a
little.
B
A
little
bit
of
trial
and
error-
maybe
maybe
I'll,
go
back
and
get
all
the
correct
ones
after
video,
so
we
don't
spend
a
whole
video
searching.
So
I
will
just
grab
this
first
collaboration.
One
choose
yeah.
What.
A
B
Do
you
want
to
so
that's
that's,
adding
a
benefit.
We
can
add
a
second
one.
A
Do
a
second
one
just
so
we
can
see
in
the
demonstration
the
start
of
that
block,
yeah
and
then
control.
B
B
A
Yeah,
let's
fall
under
the
resources
block,
so
the
res:
no,
not
resources
the
cta
banner
okay.
This
cta
banner
is
another
content
block
that
can
go
underneath
the
benefits
block.
Okay
and
it's
also
configured
to
add
ctas,
but
it
doesn't
have
to
have
ctas.
B
A
B
A
B
Here,
cool
and
now
we're
on
to
resources,
yeah,
so
grab
the
title
got
a
description.
Did
we
confirm
if
this
tweet.
A
B
A
B
This
looks
like
I
don't
get
my
it's
not
showing
me
my
preview
yep.
This
looks
like
blog
blog,
blog,
correct
and
then
oh
and.
C
A
A
You
know
the
actual
blog
link.
B
Yeah
yeah
so
in
the
suggested
content,
so
I
have
to
add
it
oh
cool
and
this
pulls
from
and
this
we
want
it
to
be
relative
correct.
So
it's
slash
blog
yep
cool
there's.
This
helpful
hint
text
there
and
we
would
do
that
for
each
of
these
and
it'll
pull
the
title
and
the
images.
B
A
Add
one
of
each
type
of
resource
cool.
B
D
A
B
That
makes
sense,
cool
and
then
white
paper.
This
is
white
papers
and
ebooks.
C
B
B
A
Oh
sorry
hold
on
right
now
to
it's
optional,
to
add
resources,
but
if
you
are
adding
a
resource,
it
does
need
these
fields,
so
I
can
change
those
to
required
in
the
admin.
A
B
B
I
have
I
haven't
played
with
the
like
other
options
under
publish
there's
like
create
new
and
something
else.
What
do
those
do.
A
Super
cool,
if
you
go
click
on
the
button,
so
we
can
see
what
those
other
options
are.
A
And
that's
publish
and
create
new,
so
that
will
actually
create
the
data
file
and
start
another
one,
and
oh
duplicate
will
copy
everything
that
you've
just
entered
and
opened
a
new
one
with
all
the
same
data.
A
So
you
can
just
make
sure
when
we
turn
on
the
editorial
workflow-
and
this
is
hooked
to
our
about
gitlab.com
url,
there's
going
to
be
a
mode
that
says
draft
and
when
you
click
on
that,
it's
going
to
take
all
of
your
changes,
create
a
branch
and
then
push
them
up
to
get
lab
and
then
open
a
merge
request
with
all
those
changes.
A
A
We
still
have
some
iterations
to
work
on
that
process
plus
we
need
we're
waiting
on
infrastructure
to
get
that
oauth
application
turned
on.
B
Cool
yeah,
that's
super!
That's
super!
I
was
looking
at
that
stuff
last
night.
It
looks
awesome.
I'm
really
excited.
B
B
Yeah
well
cool,
so
we
created
that
I
I
hopped
I've
gone
back
and
forth
in
this
main
view
to
see
that,
like
the
publish
options,
but
I
went
back
into
git
ops,
which
is
what
we
just
made
and
everything
is
published.
We
see
changes
saved,
published
up
here
and
then
I'm
gonna
hit.
So
this
is
the
live
on
the
right
here.
This
is
what's.
D
B
And
I'm
gonna
hit
my
localhost,
I
think
middleman
is
rebuilding
or
perhaps
something
is
off.
C
B
So
I
know
there's
something
going
on.
Oh
you
know
why?
Because
I
just
changed
the
domain,
and
I
just
I'm
not
serving
this
with
an
ssl
certificate
for
my
local
host.
It
should
just
be
now.
B
A
Is
first
iteration
through
we
can
see,
there's
still
more
work
to
be
done,
like
the
header
probably
want
some
more
content
up
there.
So
it's
not
so
blank
this
header
image
may
or
may
not
use
it
anymore.
So
this
would
be
we'd
push.
These
changes
up
once
we're
happy
with
them
up
to
an
mr
and
then
hand
that
over
to
the
content
team,
and
they
can
advise
us
how
to
continue
massaging
the
data
to
make
it
look
good,
but
this
is
the
initial
initial
migration
yeah,
the
related
blog
posts
at
the
bottom.
B
Wow
this
is
so
nice
and
this
is
yeah.
This
is
awesome.
I
have
I
really.
I
really
love
like
this
little
block.
I
love
these
icons
here,
they're,
so
fun,
yeah,
excellent,
well,
cool
and
another
note
too.
So
this
gets
saved
so
when
I
just
went
to
like
double
check
to
see
what
was
going
on
so
this
gets
saved
up.
So
you
can
see.
B
I've
got
like
my
sort
of
like
get
highlighting
going
on
in
my
left
hand
panel
here
and
so
the
data
file
at
the
root
of
the
directory,
oops
not
builds
and
then
under
topic,
because
that's
how
we've
configured
it
and
then
it
made
gitops.yaml
and
that's
what
we're
looking
at
here.
All
of
this
behavior
is
defined.
B
So
if
you
get
turned
around
like,
I
did
many
times
in
all
of
these
videos,
but
we
can
go
into
the
netlify
cms
configuration
and
see
these
things.
So
this
is,
you
know
the
folder
and
that's
precisely
where
we
are
in
getups.