►
From YouTube: CMS Sprint 01
Description
Link to epic: https://gitlab.com/groups/gitlab-com/marketing/inbound-marketing/-/epics/192
A
Okay,
we're
recording
hello.
We've
got
lauren
here,
senior
engineer
myself
tina,
I'm
a
ux
designer
in
this
video
we're
going
to
go
over
our
first
cms
sprint
release.
This
is
an
interdisciplinary
release.
It
includes
engineering
and
ux,
so
I'll
pass
it
over
to
lauren
she'll
talk
about
some
code
and
then
we'll
go
over
some
of
the
ux
work.
That's
been
done
in
parallel.
B
All
right,
so
I'm
going
to
share
my
screen,
so
we
can
get
in
there
and
look
at
the
code
here
we
go
there
yeah.
So
here's
my
local
dub,
dub,
dub,
repo
and
first
thing
I'm
going
to
show-
is
just
where
we're
going
to
keep
the
documentation.
B
So
if
you
do
want
to
fire
this
up
locally-
and
it's
here
netlifycms.md
right
now-
it's
really
short
because
we've
just
started,
but
this
is
where
all
the
good
stuff's
gonna
go.
You
wanna
learn
how
to
do
this
and
to
fire
it
up
locally
you're,
going
to
run
the
marketing
site
in
one
of
your
terminals
from
the
site's
marketing
directory.
That's
bundle,
execute
middleman
serve
and
then
in
a
second
terminal
window,
we're
going
to
run
this
command
here.
B
B
B
Oh
so
now
the
middleman
site
has
to
fully
rebuild
before
it'll
show
up
on
this
interface,
which
takes
a
while.
So
that's
why
I
showed
you
in
the
code
directly
there.
So
that's
where
we're
at
with
the
engineering
portion-
and
it's
really
going
to
allow
us
to
start
building
this
out
and
make
it
elegant
for
everyone
and
I'll
pass
it
over.
A
To
tina
thanks
lauren,
so
seeing
as
the
primary
reason
for
implementing
a
cms
is
to
make
content
creation
on
gitlab's
marketing
site
easier.
We
need
to
make
sure
that
the
tools
we
offer
the
content
teams
are
needed
and
useful.
A
A
Can
you
see
a
google
form
screen
yep,
so
we
started
by
creating
a
discovery
survey
that
we
distributed
to
the
team
responsible
for
managing
the
topic
pages
and
we
treated
them
as
users.
We
also
wanted
to
benefit
from
their
expertise
and
deep
insight
about
their
audiences.
A
From
there
we
created
a
report,
and
the
information
that
came
out
of
this
helps
us
zoom
in
on
priorities
so
that
we
can
align
on
what's
feasible
for
engineering,
and
it
also
provides
us
with
a
point
of
reference
for
ux,
as
we
move
through
the
different
phases
of
the
project.
A
A
We
also
pressure
tested
the
blocks
on
existing
content,
just
to
make
sure
that
they
can
carry
the
content.
These
wireframes
were
reviewed
by
erica
and
there's
a
video
floating
around
of
that
of
that
presentation
as
well
on
unfiltered
for
those
who
are
interested
in
digging
in
for
more
details.
A
The
last
item
on
this
release
was
the
application
of
the
slippers
foundation.
The
work
in
process
slippers
foundation
to
the
wireframes.
Specifically,
we
applied
the
type
stack
updated
some
colors
and
we
also
use
the
spacing
guides
so
skinning.
The
wire
frames
served
as
a
use
case
of
how
the
slippers
foundation
will
function
in
a
cms
setting
that's
being
used
by
multiple
editors,
ideally
without
going
through
the
hands
of
a
designer.
A
And
when
applied
to
the
blocks
and
templates
and
spoiler
alert,
we
think
it
does
so
you
know
shout
out
to
steven
and
jess
for
their
great
work
and
support
on
this
feel
free
to
check
this
workout.
You
can
just
you
know,
send
me
a
message
on
slack
and
I
can
point
you
to
the
file
location.