►
From YouTube: CMS Implementation: Topic Page Template
Description
UX Designer Tina walks through how the topic page will be implemented in the CMS so that the content team can self-publish with a module structure and design.
A
All
righty,
so
I
also
want
to
thank
you
for
taking
the
time
to
fill
out.
My
survey
being
new
to
gitlab
in
this
project
is
really
important
for
me
to
kind
of
get
a
good
sense
of
what
the
content
team
is
working
on
and
the
struggles
for
each
section
and
obviously
there's
a
recognition
for
a
need
for
a
cms,
and
we
decided
to
go
with
the
topic
pages
as
a
first
content
release,
because
it's
just
a
leaner
approach,
since
the
blog
is
so
much
bigger.
A
That
being
said
from,
you
know,
reviewing
all
of
your
thoughtful
answers
on
the
survey.
We
also
realized
that
these
pages
are
entry
points
and
get
a
lot
of
traffic
so
best
to
not
treat
them
like
a
blog
page
layout.
A
So
that's
kind
of
the
overview
of
what
we
heard.
You
can
feel
free
to
take
a
look
at
the
survey
report
on
your
own
time
and
share
that
also
with
brie.
A
So
what
I
want
to
talk
about
with
you
today
is
we've
kind
of
narrowed
down
a
content
block
wish
list
what
I
mean
by
content
block
it.
I
just
mean
you
know
you.
Some
people
call
them
modules.
Some
people
call
them
components,
but
just
kind
of
little
design,
layouts
that
you
can
add
to
elevate
your
content
without
having
to
ask
a
designer
or
engineer
or
anyone
like
that
to
build
that
for
you.
A
Obviously,
we
want
to
keep
this
cms
integration
lean,
so
we're
not
gonna
deliver
a
ton
of
stuff,
so
the
how
the
process
will
look
it'll,
be
kind
of
like
a
first
release.
It's
just
going
to
be
a
standard
blog
like
layout
with
just
the
title,
a
standard
wysiwyg
where
you
can
put
videos
and
images
and
standard
type
styles,
and
all
of
that,
and
then,
as
that
is
testing
test
it
being
tested
and
pressure
tested.
A
A
A
So
this
is
just
the
bottom
half
of
the
survey
where
we
just
listed
some
of
the
must-have
components
based
on
some
of
your
answers,
and
then
we
separated
by
must
have-
and
this
to
be
determined
is
just
because
we
know
you're
working
on
integra
in
testing
for
surveys
and
quizzes,
so
we're
just
going
to
kind
of
keep
that
on
the
side.
For
now,
so
we
have
headless
sorry
image
list
header
options
which
is
kind
of
taking
cues
from
the
issues
that
you're
having
with
the
blog.
A
A
So
we
understood
that
that's
pretty
important
content
cards,
cta
blocks
call
outs
which
are
kind
of
more
like
block
quotes,
but
we
separated
them
because
we
understood
from
your
answers
that
you
wanted
those
to
have
a
little
bit
more
emphasis,
two
column
layouts
and
a
sidebar
navigation,
which
probably
should
have
been
the
first
thing
on
this
list.
But
this
isn't
in
order
of
priority.
A
Does
that
feel
kind
of
right
for
a
must-have
list?
Yeah
I'm
impressed.
A
Well,
they're
gonna
come
you
know,
as
I
said,
in
iteration
yeah
great.
So
let's
take
a
look
at
at
some
of
those
in
action
then.
So
this
you
have
a
link
to
this
big
file
on
the
sidebar.
Here,
it's
separated
by
big
picture
and
lean.
So
today
we're
going
to
focus
on
the
lean
stuff.
A
You
can
take
a
look
at
the
big
picture,
stuff,
that's
still
kind
of
being
reviewed
by
engineering,
that's
kind
of
more
of
the
ux
content
or
wish
list
things
that
the
way
you
know
we
think
that
content
should
be
presented,
but
then
there's
also
reality.
A
So
one
thing
that
we
kind
of
that
was
flagged
was
the
need
for
a
what
has
been
called
a
sidebar
for
navigations
for
related
links
for
cluster
articles.
Thinking
about
that,
we
thought
that
it
could
be
interesting
to
put
that,
in
fact,
in
the
header
area,
to
bring
more
emphasis
to
it.
Often
the
way
sidebars
are
used
are
just
you
know,
for
the
types
of
pages
where
you're.
A
Looking
for
additional
information,
like
you
know,
a
company
privacy
policy,
for
example,
you
would
go
there
and
then
you
use
the
sidebar
nav
to
navigate
those
items.
A
A
There's
a
lot
of
rationale
up
here.
We
don't
have
to
go
through
it
item
by
item,
but
if
you
do
want
to
go
over
this
with
your
team,
all
of
that
information
is
there
the
the
wise
moving
on
to
this
section,
so
we're
calling
this
embedded
blocks
so
for
this
first
iteration
again
to
keep
it
lean.
We're
not
gonna
kind
of
create,
like
a
squarespace
type
designer
where
you
can.
A
You
know,
have
like
a
modular
like
access
to
move
things
around
a
page,
but
what
we'll
start
with
is
giving
you
kind
of
a
couple
embedded
blocks
that
you
can
turn
on
or
turn
off
if
you
need
them,
so
as
you
create
sections
by
default,
there'll
be
these
three
blocks
and
then,
if
you
don't
need
them,
you
just
turn
them
off.
So
what
we've
narrowed
down
for
those
blocks
for
this
first
round
would
be
this
list
for
benefits
or
for
you
know,
whatever
I've
seen
them
use
so
many
times
and
don't
forget.
A
B
Okay,
so
for
something
like
the
benefits,
module
or
block
that
you're
calling
it.
A
Yeah
so
they'll
definitely
be
a
field
for
title,
a
field
for
the
description
and
then
a
field
for
an
image
whether
that's
going
to
be
pulled
from
a
library
or
not.
I'm
still
unsure
about
that
part,
but
they'll
definitely
be
an
opportunity
to
upload
an
image.
A
So
there's
a
small
chance,
you
might
still
have
to
go
through
a
designer
if
you
need
something
to
be
turned
into
an
svg
or
cropped
if
it
doesn't
connect
to
a
library,
but
the
details
of
that
is
still
to
be
determined,
but
yeah
you'll
have
all
those
fields.
There's
no
code,
no
coding.
A
This
is
something
new
that
doesn't
exist
just
because
you're
using
crosslinking
so
heavily
on
these
pages,
and
it's
not
you
can
see
these
cards
below
it's
not
always
going
to
a
blog.
Sometimes
you
want
to
mix
and
match
related
articles.
Sometimes
things
are
on
the
solutions
pages
on
the
customer
pages,
so
we
thought
it'd
be
interesting
to
have
a
kind
of
a
fixed
layout
at
the
bottom,
where
you
can
have
a
list
of
just
resources,
and
these
would
be
all
links
to
go
that
go
to
various
places.
Videos
case
studies.
A
B
A
And
I
find
that
when
those
cards
are
being
overused,
like
people
will
just
suffer
from
card
that
blindness,
similarly
to
the
side
nav
you
kind
of
get
real
blindness
and
don't
look
at
the
stuff
in
that
side.
So
we
want
to
avoid.
We
want
to
avoid
that,
and
that
brings
us
to
these
cards.
These
are
self-explanatory.
A
One
thing
that
we're
working
on
is
we.
It
would
be
neat
if
you
could
mix
and
match
these
easily
and
that
they're
consistent.
So
that's
still
something
that's
kind
of
a
work
in
progress,
and
how
can
we
have
a
case
study?
Look
like
a
blog
card
like
if
you
just
don't
necessarily
want
these
to
all
be
from
the
same
source,
so
that's
kind
of
a
work
in
progress
for
now,
but
that's
the
idea
for
this
component.
That
would
be
the
update.
A
We
also
had
a
lot
of
conversations
about
removing
the
bylines
when
blogs
are
presented
here,
just
because
it's
inconsistent
when
they're
mixed
in
with
other
types
of
articles
and
bylines,
also,
especially
when
there's
a
date
can
date
things
and
sometimes
an
article
that
was
written
last
year,
can
still
be
relevant
to
this
page.
And
you
don't
want
something
that
says
like
2018
on
it.
So
we're
open,
obviously
to
not
doing
that.
It's
just
something
that
we
thought
looked
a
little
bit
cleaner
as
well.
B
A
B
To
be
honest,
I
could
see
us
using
this
section
more
for
like
what
you
said
case
studies
and
potentially
related
articles
outside
of
the
main
topic
as
a
way
to
get
people
reading
further
into
other
things
that
we
do
so
I'm
trying
to
think
of
like
if
somebody's
coming
in.
So
let
me
take
a
step
back,
we're
moving
a
lot
of
content
off
of
our
blog
into
these
articles.
B
So
that's
how
I
would
see
us
using
this,
whereas
the
resources
section
above
actually
what
she
pointed
out
need
devops
buying
here,
is
how
to
come
in
stakeholders.
B
I
see
this
section
is
like
what
are
the
top
three
things
we
want
them
to
engage
in
a
blog
like
that,
it
would
be
the
blog
we
want
them
to
read,
because
it's
part
of
the
buyer's
journey
versus
just
at
this
using
these
cards
to
say,
here's
three
related
blog
posts.
It's
a
lot
more
like
strategic
visibility
of
content.
So
that's
how
I
see
us
using
these,
so
the
byline
and
dates,
and
all
that
stuff
not
being
there
is
definitely
no
problem.
Great.
A
Also,
I
know
that
the
topics
pages
specifically
are
not
necessarily
about
selling
git
lab.
It's
not
necessarily
a
part
of
this
user's
journey,
but
I
see
it
in
many
of
the
pages.
A
B
Got
it
yeah?
I
could
see
us
using
this
also
to
point
to
our
solutions,
solutions
pages,
which
is
like
the
consideration
version
of
this,
where
we
actually
start
to
explain
how
gitlab
solves
whatever
thing
the
topic
is
talking
about,
so
that's
great,
so
that
would
be
customizable.
It
wouldn't
just
be
pulling
in
the
try.
Git.
A
Lab
yeah
again,
it
would
maybe
just
default
to
this
or
anything
you
know
you
can.
You
know
your
team
can
decide
would
be,
would
be
the
most
commonly
used
things.
You
don't
always
have
to
enter
it
every
time,
and
then
you
would
edit
the
field
edit
this
field
and
then
change
the
button
url
and
the
the
copy.
That's
in
it.
A
Okay.
So
these
are
editor
items,
so
these
are
just
things
that
are
just
standard.
A
You
usually
send
like
available
in
a
wysiwyg
or
any
any
type
of
editor,
so
full
width
image,
one
column
like
inline
image,
video
pull
quote
and
block
quote,
and
then
just
your
standard,
typography
styling,
so
lists
bullets,
all
of
that
links
right
and
then
moving
to
this
side.
So
this
is
just
what
we've
talked
about
just
you
know
in
in
real
use.
So
this
is
an
article
using
some
of
the
components
we
just
discussed.
A
So
this
is
how
it
could
look
with
the
title
description
and
then
the
links
on
the
side
here,
optional
image
right
underneath
I
know
that.
There's
some
conversations
about
the
blog
that
if
there
is
no
image,
we're
gonna
have
to
find
a
way
to
display
some
default
images.
I'll
have
to
follow
up
with
where
that
project.
B
Is
at
I
think
that
conversation
is
mostly
around
sharing
on
social
because
they
need
an
image
for
social.
Okay.
We
don't
need
an
image
to
publish
to
the
blog,
so
I
wouldn't
I
don't
think
that's
a
concern
here.
We
might
do
paid
advertising
around
these
pages
to
help
get
the
traffic
up,
but
I
don't
see
us
sharing
these
pages
much
on
social.
So
I
don't
think
that
would
be
a
huge
issue.
So.
A
What
about
then,
these
cards,
though,
because
if
you're
gonna
be
sharing
them
inside
the
gitlab
universe,
right
they'll
still
need
an
image.
So
when
we
create.
B
A
A
good
question:
normally
it
would
just
pull
the
default
image,
but
obviously
it's
gonna
have
to
be
built
in
a
way
that
you're
gonna
have
to
upload
an
image
which
kind
of
defeats
the
purpose
of
this
being.
You
know
a
lean
process
for
your
team,
because
you'll
still
have
to
source
an
image.
So
that's
definitely
something
we
have
to
think
about
with
the
cards.
Specifically,
I
did
like
toy
around
with
the
idea
of
having
cards
without
images
but
yeah
it.
A
B
Yeah,
that's
a
good
point.
You
know
I
like
what
I'm
seeing
here
with
the
image
right
there
and
that's
kind
of
how
our
blog
is
going
yeah.
The
thing
that
I'm
thinking
about
with
the
whole
image
is
like
right
now.
For
example,
our
blog
everything
we're
using
is
from
unsplash,
so
it's
super
generic.
B
A
Okay,
yeah,
it's
true:
it
is
early
in
the
process.
So
I
think
that
it's
just
good
to
know
that,
for
the
build,
we'll
probably
have
to
just
have
an
option
to
upload
an
image
yeah
all
those
pages
that
might
not
have
images,
because
I
know
also
some
of
these
cluster
child
articles.
Don't
have
images
at
all
right,
so
yeah
standard
body,
I've
narrowed
the
columns
quite
a
bit
just
to
give
it
a
lot
like
a
more
of
an
editorial,
feel
it's
easier
on
the
eyes,
it's
easier
for
scanning.
A
This
is
how
resources
could
look
at
the
bottom,
your
related
reads
and
then
the
cta,
so
how
the
templates
will
work
for
this
first
iteration
is
that
your
templates
will
come
with
all
of
this
stuff,
and
if
you
don't
want
this,
you
have
to
check
it.
You
don't
want
this,
you
uncheck
it!
You
don't
want
this,
you
uncheck
it,
but
you
can't
really,
unfortunately,
for
now
move
anything
up
the
page.
B
A
Great
there's
just
a
couple
more
things
to
go
over
just
this
is
just
how
it
would
look
stand
alone
with
no
image.
A
Sorry,
not
no
images,
no
related
links,
the
use
of
these
so
just
kind
of
the
same
idea
just
to
give
a
feel
of
the
header
that
the
headers
can
still
look
nice
without
the
related
links.
A
This
is
just
a
pressure
test
to
show
we
are
in
the
middle
of
discussing
how
we
want
to
deal
with
the
survey
pages
if
those
are
going
to
be
a
separate
template
or
if
you're
going
to
be
able
to
load
the
survey
inside.
So
since
they're,
not
those
questions
aren't
being
answered.
This
is
just
you
know
what
we're
working
with
as
a
template.
We
figure
that
whenever-
and
you
can-
you
would
know
better
than
than
me
whenever
you
do
want
to
launch
a
quiz
or
a
survey.
B
Yeah,
this
is
a
good,
so
this
the
quiz
or
survey
the
most
likely
destination
for
these
would
be
on
a
topics
page
and
the
topics.
Page
content
itself
is
shorter
than
like
a
web
article,
because
it's
just
the
topic
and
you
go
to
the
other
web
articles
to
dig
deeper,
so
there
might
be
more
text
around
it.
So
I
don't
know
if
you
can
just
add
it
as
a
block.
B
Okay,
the
whole
idea
behind
the
quiz
is
to
see
if
we
can
get
people
into
a
funnel
of
like
you
landed
on
this
topics
page,
but
do
you
belong
here?
Can
we
point
you
somewhere
and
just
to
get
them
to
where
they
need
to
go
quicker.
A
Okay,
that
makes
sense
video.
A
So
using
a
similar
layout
for
whenever
you
want
to
just
show
videos,
maybe
you
want
to
have
a
whole
funnel
to
watch
more
webcasts
this.
This
could
be
how
that
could
look,
and
one
thing
I
notice
is
that's
missing
from
here:
I'm
just
going
to
go
into
the
big
picture
section
for
a
second
is
that
you
do
have
the
opportunity
to
put
links
and
buttons
in
there
it
okay
yeah,
so
they
would
be
underneath
these
I'll
add
them
to
one
of
these.
A
To
give
an
example,
I
just
thought
like
for
some
of
these
cluster
articles
when
there's
also
a
link
to
go
to
download
an
ebook
and
then
there's
related
links,
there's
just
a
lot
you're
asking
the
user
to
go
in
a
lot
of
directions
and
just
like
the
first
three
seconds
so
but
yeah.
B
B
So
this
is
us
saying
hi
for
the
first
time,
so
I
really
like
that
thought
process
of
not
overwhelming
people
and
keeping
them
focused,
because,
ultimately
we
want
to
rank
really
high
for
these
pages
and
that's
going
to
be
a
combination
of
traffic
and
like
time
on
page,
like
how
good
is
this
content
actually.
A
Yeah,
that's
great
okay,
great,
so
that's
everything
that
I
wanted
to
review
for
this
for
this
meeting,
we'll
probably
meet
again
in
two
three
weeks
when
there's
more
things
to
go
over,
I
know
that
lauren's
getting
close
to
installing
the
admin
so
we're
soon
going
to
be
able
to
play
around
in
there
for
reals,
so
that's
very
exciting
and
feel
free
to
leave
comments
in
in
the
figma
file
using
the
commenting
tool.
I
I'm
not
sure
I'm
sure
you've,
you
guys
all
use.
B
Yeah,
I
think
I
definitely
have
I'm
able
to
use
it.
Okay,
I'm
not
sure
about
the
team,
because
what
I'll
do
is
I'll
share
this
video
and
this
agenda
too,
with
bray
and
the
rest
of
the
content
marketing
team,
because
they're
the
ones
actually
writing
the
articles.
B
For
me,
like
this,
looks
great
it's
for
us,
the
number
one
thing
was
like:
can
we
get
these
live
and
looking
good
on
our
own
yeah
and
this
checks
all
of
those
boxes?
It
gives
them
some
good
custom
customization.
So
I'll
share
all
this
with
them
too.
To
leave
any
comments
in
case
there's
something
I
missed,
but
to
me
this
is
like
seems
like
a
good
start.
B
We
have
a
lot
of
topic
pages
and
web
articles
to
even
get
in
there
and
then
my
vision
is
probably
you
know
like
six
months
we
come
back
like.
Is
there
something
that
we've
run
into
now
that
we
can't
do
yeah
that
we
want
to
do,
and
that's
probably
going
to
be
more
around
getting
people
into
funnels
and
like
getting
more
advanced
at
that?
But
again,
that's
like
six
months
to
a
year.
Out,
probably,
we
need
to
get
these
pages
up
and
people
on
them.
Yeah.