►
Description
Hanif Smith-Watson shares some ideas on how we can improve /stages-devops-lifecycle/ and fully integrate our product pages with their respective stages.
A
A
I
can,
can
you
guys
see
my
screen?
Okay,.
A
Okay,
so
I
was
I've
been
analyzing
these
pages
and
just
to
see
what
we
can
do
to
improve
the
traffic
to
these
pages.
A
One
of
the
things
that
I
notice
is
these
pages
are
about
the
different
stages
of
the
the
life
cycle,
but
when
you
click
into
it,
it
doesn't
give
you
a
lot
of
information
about
the
stage
and
how
gitlab's
what
gitlab
offers
but
he's
for
the
different
stage,
and
it
doesn't
link
to
the
devbox
comparison,
gitlab
versus
other
competitors.
A
So
my
thinking
was
if
we
could
improve
the
individual
pages,
explaining
what
the
stage
is,
what
features
our
gitlab
has
for
that
stage
and
followed
by
links
to
the
different
devops
tools
that
we've
that
we
have
on
our
devops
comparison
pages.
B
A
Yeah,
these
learn
more
links.
They
point
to
docs.gitlab.com
when
you
visit,
there's
no
link
pointing
back
to
your
original
back
to
the
about
gitlab.com
page.
So
it
would
be
a
great
thing
if
we
can
include
a
call
to
action
or
a
link
back
to
about.gitlab.com.
A
B
And
hannah
looking
at
that
page
too,
I
know
one
of
the
things
that
I
think
you
mentioned
to
me
as
we,
as
you
kind
of
laid
this
out,
is
that
when
you,
when
you
look
at
that
manage
page
there's,
no
real
kind
of
like
sim,
like
really
straightforward
approach
of
explaining,
like
here's,
what's
in
the
stage
from
a
product
perspective,
like
you
know
man,
it's
issue
boards
right,
like
here's,
here's
about
get
live
issues.
B
You
know
how
you
can
use
issue
boards,
those
kind
of
things
you
know-
and
it
looks
like
this-
is
you
know
even
more
about
management
of
like
users
and
things
like
that.
So
you
know
I
know
we
have
some
product
related
pages.
Do
you
feel
like
it
makes
sense
to
maybe
move
those
and
associate
them
more
with
each
stage
and
then
have
them,
maybe
as
a
subpage.
A
Yes,
for
example,
the
ci
cd
page,
we
could
move
that
is
it
on
the
solutions.
Sorry,
it's
on
the
stages,
devops
livestock,
slash,
cicd,.
A
Yeah
we
can
move,
we
can
create
a
new
clone
structure,
so
we
will
have
verify
forward,
slash,
ci,
cd
to
and
move
that
page
under
this
folder.
A
The
verify
page
will
be
all
about
the
stage,
a
briefly
a
summary
of
gitlab,
offering
with
a
link
pointing
to
the
full
product
page
with
all
the
information.
B
When
we
talked
about
it,
one
of
the
the
ways
you
kind
of
talked
about
the
strategy
for
this-
and
I
know
this
is
something
you've
thought
a
lot
about
too,
is
that
you
know
we
want
to
have
topics
pages
that
are
kind
of
what?
What
stage
would
you
say
topic
spaces
would
be.
I
know.
C
Topics
pages
would
be
kind
of
awareness
top
of
the
funnel
so
like,
ideally,
we're
trying
to
capture
organic
traffic
from
that
element,
make
them
aware
of
the
products
the
brand
and
then
push
them
towards
as
well
solution
pages,
which
promotes
the
different
elements
of
the
product
and
solutions
we
have
for
their
pain.
C
I
know
that's
that's
pretty
much
it
like.
I
was
just
saying
the
blogs
then
for
would
be
pre-awareness
that'll,
be
the
system
set
up
like
pre-awareness
awareness
to
solutions
which
would
be
consideration
or
just
give
an
overview
of
products
and
solutions
themselves.
B
Right
and
so
topics
really
would
be
unbranded
search
right,
people
that
are
looking
for
continuous
integration,
as
a
kind
of
you
know
that
that
first
level
turn
and
then
and
then
we
see
these
pages.
Do
we
see
these
pages
like
sitting
with
the
the
solutions
in
the
use
case
pages?
Or
do
you
see
that,
as
like
you
know,
maybe
a
step
between
topics
and
solutions.
A
Yeah
I'll
see
as
a
step
between
topics
and
solutions,
we
could
target
these
pages
for
search
terms
related
to
devops
planning
tools.
For
example,
we
just
need
to
do
a
little
bit
of
research
on
the
potential
search
traffic
we
might
get
for
those
kind
of
searches,
but
when
looking
at
devops
tools
in
google
a
lot
of
the
images
they
all
have
the
full
life
cycle
and
around
the
life
cycle,
they
list
all
the
different
products.
A
So
we
could
do
something
similar
with
our
pages,
where
we
talk
about
the
all
the
planning
tools
and
what
we
promote,
get
labs
features.
B
A
B
So,
like
you
know,
if
I
I'm
just
thinking
through
like
what
I
would
google
to
get
to
these
pages
right,
if
I'm
just
a
visitor,
so
you
know
that
first
step
is
continuous
integration.
You
know
there's
a
lot
of
saturation
for
that
term.
I
think
a
lot
of
people
are
familiar
with
that
term,
but
there's
still
lots
of
people
out
there
that
are
learning
about
it
for
the
first
time.
B
So
you
know
we
want
that
topic
page
to
serve
that
need
and
then
I'm
on
the
topic
page
and
I
go
away
and
a
week
later,
I'm
thinking
like
you
know
what
I'm
ready
for
you
know:
gitlab
ci,
don't
go
google
that
do
we
see
these
stages
of
the
devops
lifecycle
pages.
Answering
that
query
or
do
we
see
that
being
more
of.
B
The
ideas
that
you
presented,
because
I
think
it
really
kind
of
gets
to
some
of
the
the
questions
I've
had
around
like
how
do
we
talk
about
our
product
in
a
meaningful
way?
While
you
know
it's
not
about
the
topics,
it's
not
about
the
specific
use
case,
but
it's
about,
like
the
site,
just
wants
to
know
what
gitlab
ci
does
right,
like
not
the
use
case,
not
just
the
benefits,
but
you
know,
like
here's,
a
just
a
literal
description
of
the
features
that
are
in
gitlab
ci
for
you
from
a
marketing
perspective
right.
B
B
Very
great
miley
anything
else
to
add.
C
No,
that's
pretty
straightforward.
I
think
in
terms
of
the
the
targeting
the
keywords
at
different
stages
is
something
I
think
from
an
intent
perspective
of
something
we've
started
to
look
at
before
and
something
we're
probably
going
to
look
at
more
in
the
new
year
with
the
product
team,
because
they
said
they
have
listings
of
specific
terms
and
terminology
for
the
products
that
they've
identified
by
buyer
journey
stage.
So
that's
something
we
can
use
along
with
this,
to
try
and
kind
of
map
out
a
more
targeted
journey
for
the
users.