►
From YouTube: Sprint 0 CMS
Description
Review of our plan for this sprint. The issue I mention that we're blocked by is here: https://gitlab.com/gitlab-com/gl-security/security-assurance/field-security-team/third-party-vendor-security-management/-/issues/333
A
Okay,
so
we
have
the
digital
experience
team,
the
sub
team-
that's
focused
on
our
cms
okr,
so
we
wanted
to
just
recap
what
our
plan
is
for
this
next
two
week:
sprint
with
the
aim
of
wrapping
up
this
body
of
work
by
next
wednesday.
So,
let's
start
off
with
engineering
lauren.
Could
you
cover
off
what
we're
planning
on
doing
and
why.
B
C
While
lauren's
taking
care
of
the
engineering
side
of
things,
I'm
helping
the
team
integrate
the
cms
to
the
topic
sections
as
first
content
release,
we
chose
the
topic
pages
because
they're,
lightweight
and
cert
will
serve
as
a
good
proof
of
concept
before
we
integrate
the
pages
to
the
rest
of
the
site,
we're
talking
also
with
our
content
partners
to
make
sure
that
their
needs
are
being
met
in
terms
of
the
types
of
functionalities
they
need.
On
these
pages,
we
want
to
help
them
streamline,
streamline
and
standardize
their
content
to
help
them
reach
their
goals.
A
Awesome
so
how
this
sprint
relates
to
our
overall
eight
okay,
our
goal
is
overall,
we
want
to
get
nitpify
set
up
as
our
cms,
so
first
step
is
getting
it
set
up
locally,
so
we
can
demo
how
it
will
integrate
into
our
topics
pages.
We
want
to
get
it
set
up,
so
we
can
push
it
to
production,
we're
currently
blocked
by
security.
A
I'll,
add
the
security
request
in
the
description
of
this
video
once
we
do
have
that
set
up,
it'll
be
available
for
oauth
and
we'll
be
able
to
deploy
to
production
and
collaborate
even
further
with
our
content
creation
team,
because
they'll
have
access
on
their
own
to
the
admin
section
and
yeah
we'll
be
working
towards
that
full
featured
cms
running
on
netlify.
So
we
are
very
excited
to
see
what
we're
going
to
be
able
to
get
done
by
next
wednesday,
and
we
will
report
back
in
our
demo
video.
So,
let's
get
after
it.