►
Description
Discussion around improving about.gitlab.com/solutions/aws
A
Hi
this
is
danielle
and
I'm
here
with
alicia,
we
are
working
on
improving
the
aws
partner
page,
which
is
the
solutions
page.
We
have
some
notes
from
our
last
conversation
and
what
we're
going
to
do
today
is
kind
of
live
jam
on
an
mr
probably
going
to
pull
up
some
other
examples
for
inspiration,
and
I
think
some
of
the
things
we
might
not
want
to
change.
You
know
we
want
to
share
this
video
with
other
folks
on
the
team
and
get
some
help.
A
A
Totally
so
why
don't
we
start
by?
I
think
you
were
giving
a
good
summary
right
before
we
started
the
call
of
just
kind
of
like
some
of
the
main
criticism
of
how
this
page
could
be
improved.
So
why
don't?
I
share
my
screen
and
why
don't
we
talk
about
that
again
because
I
think
that'll
help
just
set
context
for
anybody
else
who
watches
this
video
so
go
ahead.
B
Yes,
so
this
is
kind
of
our
main
call
to
action
when
and
when
we
do
trade
shows
or
any
type
of
email
or
any
type
of
content
where
people
are
like.
How
does
gitlab
support
aws?
What
does
the
partnership
look
like
we
kind
of
direct
people
to
this
page.
As
you
can
see
here,
it's
got
a
lot
of
good
information,
but
it's
very
very
text.
B
Heavy,
like
you'll,
see
that
we're
a
devops
competency,
partner,
you'll,
see
we've
put
a
lot
of
our
joint
aws
and
gitlab
benefits
and
you'll
see
how
our
marketplace
partner
our
joint
capability,
so
meaning
the
integrations
we
support,
which
is
really
what
a
lot
of
people
want
to
focus
on,
and
our
customer
success
stories
and
our
joint
solutions
in
action,
which
we
feature
a
lot
of
white
papers,
webinars
we've
done
with
aws
and
then,
of
course,
at
the
bottom.
Try
get
love
free.
B
B
If
that
means
doing
some,
I
would
say
like
images
and
make
it
a
little
bit
more
exciting
and
maybe
tell
a
little
bit
better
story
and
have
people
walk
through
initially,
I
want
to
say,
since
a
lot
of
people
that
come
to
this
page
are
probably
looking
at
the
integrations
we
support.
I
would.
I
would
think
that
we'd
want
to
move
that
up
a
little
bit
higher
and
if
there's
a
way
we
can
support
visuals
on
that.
B
Besides
we
right
here
we
have
the
icons
so
you'll
see
we
have
like
the
ec2,
the
eks,
the
fargate
lambda
icons.
That
aws
has,
for
these
integrations
there's
a
way.
Maybe
we
can
make
it
a
little
bit
more
visual.
I
don't
know
exactly
what
that
looks
like,
but
that
it's
so
text-heavy,
it's
kind
of
hard
to
read
it.
Just
I
guess
if
I
was
like
just
if
I
was
like.
Oh,
what
integrations
does
gitlab
support
with
aws
and
I
looked
here.
B
A
For
each
one,
but
I'm
noticing,
like
one,
is
a
blog
post
but
like,
for
example,
it
looks
like
most
of
these
are
like.
Let's
look
at
the
lambda,
one
looks
like
it
takes
us
to
docs.
Okay,
so
I
guess.
Can
I
ask
you
a
couple
of
clarifying
questions
just
to
like
draw
you
out
a
little
bit
more
on
on
some
of
your
thoughts,
yeah
so
going
back
to
the
original
page,
and
I
want
to
get
back
to
the
joint
solution
capabilities
section
in
a
second,
but
I'm
just
curious.
A
Like
do
we
have
a
goal
for
this
page
that
we're
measuring
like
where
we
say
like
if
x
happens,
then
the
odds
of
y
which
I'm
guessing
is
leads
or
or
whatever
like?
Are
we
counting
how
many
times
talk
to
an
expert
gets
converted
or
how
many
times
people
sign
up
for
a
trial
for
this
page
or
anything
like
that?.
B
We're
not
really,
we
haven't
really
been
measuring
that
it's
just
kind
of
a
like
an
overall
page
where
people
are
like.
Oh
can
I
get
more
information?
How
you
supported
us
here,
here's
something
that
has
everything
that
you
might
need
to
know.
So
we're
not
really,
I
think,
as
far
as
call
to
action,
we
haven't
really
been
measuring
that
we
haven't
really
been
we.
B
We
feature
this
page
in
a
lot
of
our
path
factories,
so
we
can
see
if
people
do
kind
of
come
to
this
page,
but
I
think
that's
where
it
tailors
off
with.
It
goes
to
talk
to
an
expert
and
you'll
notice
this
for
more
than
just
our
aws
solutions
page,
we
also
have
a
vmware
tanzu
solution,
page
a
red
hat
solutions,
page
hashi
and
a
google
cloud.
It
all
goes
to
this
contact
sales
and
I'm
not
really
sure
exactly
what
happens.
B
A
And
then
down
here
what
we
were
talking
about
the
solutions
capabilities,
I'm
kind
of
curious,
like
I
don't
totally
know
the
intent
or
like
you
know
where
this
is
getting
used,
but
I
could
imagine
sending
someone
to
a
docs
page
if
they're,
not
a
developer,
isn't
like
particularly
actionable
I'm
curious.
Do
you
have
thoughts
on
like?
Is
this
the
ideal
experience,
or
is
there
some
interstitial
page?
We
want
to
have
that
more
explains
like
why
aws
lambda,
plus
git
lab,
is
a
great
combination.
B
No
evidence,
of
course,
but
we
definitely
need
to
start
figuring
out
how
we
can
kind
of
start
tracking
this
better,
but
I
think
it
can
be
twofold.
I
when
we
go
to
trade
shows,
for
example,
we
just
finished
up
with
aws
re
invent
a
lot
of
that
is
developer
focused
and
the
leads
are
more
technical
leads.
I
think
they
will
find
this
stuff
interesting,
like
figuring
out
how
you
can
deploy
lambda
with
git
lab,
I
think,
from
a
technical
piece.
B
That
is
something
they
are
interested
in,
but
I
also
think
that
you
we
because
we
use
this
page
in
so
many
different
facets
and
different
activity
go
to
market
activities
and
we
direct
people
a
lot
of
different
types
of
leads
and
people
to
this
page.
I
think,
maybe,
if
we
could
separate
from
the
more
technical
like
sending
people
to
docs
who
might
be
interested
in
how
we
support
it.
Technically
and,
like
you
said,
the
business
aspect,
I
think
that
would
be
more
beneficial,
because
this
is
an
all
encompassing
page.
So
we
need
to.
B
We
want
to
have
all
this
messaging,
but
I
think
it's
hard
to
tailor
it
because
it's
not
unless
we
did
like
a
specific
page
just
specifically
for
technical,
aws
information
and
then
one
for
specific,
just
business,
quote-unquote
business
information.
I
think
when
I
don't
think
that's
what
we're
we're
looking
to
do
at
this
time.
I
think
I
know
I'm
kind
of.
A
Rambling
right
now,
but
I
think
it's
great
it's
okay,
like
we're
just
trying
to
figure
it
out.
I
think
the
question
I
have
is
I'm
asking
you
a
little
bit
about
calls
to
actions
and
goals
it's
like
if
we
don't
figure
out
that
it's
really
hard
like.
I
think
one
of
the
reasons
these
pages
have
gotten
so
verbose
is
it's
like
we're
trying
to
satisfy
everybody,
and
so
it's
hard.
So
I'm
wondering
if
we
have
some
like
fundamental
clarifying
work.
A
B
Right,
I
want
to
say
we
should
lean
more
technical,
okay
in
this
page,
I
I
mean,
but
also
like
even
just
showing
like
in
this
corner.
You
see
where
devops
competency
partner,
that's
important,
because
it
gives
someone
that
might
be
interested
in
get
lab.
Who
is
focused
on
them.
It
gives
them
a
little
bit
more.
Like
you
know
like.
Oh,
you
are
a
sought
out,
devops
competency
partner,
so
it
might
someone
that's
digesting
this
content.
That's
like
okay,
aws
has
vetted
them
out
to
be
a
top.
A
So
do
you
think
that
I'm
curious
of
all
the
things
we've
actually
got
a
lot
of
calls
to
action
here
right
we've
got
talked
to
an
expert.
We've
got,
learn
more
oops,
and
then
we've
actually
got
this
one
here,
which
is
check
out
gitlab's
offerings
on
the
I
didn't
realize
this
is
actually
a
call
to
action.
This
is
our
marketplace
listing
and
then
we've
got
each
of
these
learn
mores,
which
are
all
calls
to
action
right.
So
do
we
know
like
what
the
most
valuable
cult
like
of
any
call
to
action
on
this
page.
B
Probably
sign
up
for
a
free
trial
gitlab,
if
I,
if
we
use
this,
we
use
this
page
a
lot
I
want
to
say
mostly,
for
we
have
an
aws
nurturer
campaign,
and
so
we
reference
this
page
a
lot,
because
we
want
to
get
people
to
ultimately
convert
into
an
mql.
We
want
them
to
start
a
trial
of
get
lab
and
we
want
them.
You
know
automotive
to
be
a
customer,
so
I'm
thinking
at
the
end
of
the
day,
we're
being
like
hey
look
at
all
this.
You
are
an
aws
shop.
A
That's
super
helpful,
so
what
I'm
thinking
is
what,
if
I
think,
rather
than
trying
to
reorganize
this
all,
I
think
what
I'm
probably
going
to
do
suggest
we
do
is
share
this
with
the
web
team
share
this
video
with
them,
so
they
can
understand.
It
sounds
like
there's
a
bit
of
reordering
that
we
want
to
do
probably
bringing
some
of
this
up
higher
and
then,
obviously,
when
I
look
at
this,
I
see
you
know
all
this
stuff
is
blocked
down
below
the
full
and
there's
this
big
block
of
text.
A
Probably
this
you
know,
can
live
somewhere.
It's
probably
important
to
say
these
things,
but
maybe
not
here,
so
I'm
thinking,
maybe
what
we
want
to
do
is
we
want
to
make
sure
like
every
journey.
Every
part
of
this
journey
leads
to
that
probably
either
the
primary
goal,
which
is
the
free
trial,
or
maybe
we
say
like
a
secondary
goal,
is
that
they
go
to
the
aws
marketplace.
A
A
Let
me
show
you
an
example
until
really
recently
in
docs
we
didn't
have
this
get
free
trial
button,
believe
it
or
not,
and
so
you
know,
you'd
get
here
and
you'd
pretty
much
be
at
a
cul-de-sac
or
you
wouldn't
necessarily
create
a
trial.
So
the
good
news
is
that's
been
addressed,
so
those
pages
are
better,
but
I
am
concerned
about
you
know
some
of
these
other
pages,
but
I
guess
the
free
trials
here
in
the
right
corner,
but
it's
just
like.
Well,
I
don't
really
know
this
was
sort
of
a
little
bit
of
non-sequitur
right.
A
B
If
you
scroll
down
to
what's
another,
why
we
want
to
support
that?
You
know
the
ultimate
goal
is
to
for
them
to
sign
up
and
become
customers.
Is
we
want
we're
like
hey?
Look
at
all
these
joint
solutions
in
action
in
this
customer
success
story?
This
could
you
know
we're
giving
examples
to
kind
of
convert
them
into
the
funnel,
even
more.
So
that's
why
we
have
all
this
at
the
bottom
as
well.
It
just
supports.
A
That
that
almost
feels
like
an
incomplete
page,
though
right
like
it's
not
like,
like
we
have
a
list
because
we
didn't
have
time
to
actually
like
have
the
page
have
like
a
graphic
to
like
show
off
this
video.
I
mean
we
can
do
all
these
things.
I
want
to
make
sure
you
know,
like
I'm
trying
to
open
this
door
of
like
if
these
are
great
pieces
of
content.
Let's
have
them
featured
more
on
this
page
visually,
so
that
they're
more
compelling
like
if
I
see,
there's
a
how
to
deploy
aws
from
gitlab.
A
To
me,
I'm
like
is
that
not
like,
if
that's
a
white
paper,
is
that
not
the
most
valuable
thing?
If
I'm
like
up
here
at
this
first
one,
I
think
it's
interesting
to
think
like
how
can
these
things
be
part
of
the
journey?
I'm
guessing
all
wouldn't
have
made
them
or
they
wouldn't
have
been
solutions
in
action
if
they
weren't
things
that
you
know
are
helping
in
the
sales
conversation.
So
I'm
just
wondering
how
do
we
show
them
off
more
than
just
a
link.
B
Yes,
I
I
agree
with
that,
and
we
also
have
more
content.
We
want
to
add
to
this
page
believe
it
or
not,
from
reading
more
demos
and
more
technical
stuff
to
support
our
story,
so
I
think,
like
you
said,
doing
something
a
little
bit
more
visual
to
show
off
the
story,
instead
of
it
just
being
a
bunch
of
links,
because
you
know
it's.
A
I
don't
think
we
really
have.
I
think,
like
you
and
I
having
this
conversation
is
like
a
beginning,
but
I
think
at
the
very
least
we
could
create
either
an
embeddable
video
with
you
know
that
just
you
can
see
like
oh
there's
a
video
here
I
can
watch
or
we
can
create
some
kind
of
graphic
for
you
know
kind
of
representing.
What's
in
that
white
paper,
those
things
seem
pretty
simple
to
me.
I
think
the
big
question
I
have
is
just
of
all
this
content.
B
A
Perfect
and
yeah,
I
would
kind
of
expect.
You
know
that
the
content
earlier
in
the
drip
gets
more
clicks
just
because
more
people
are
still
engaged.
But
what
will
be
really
interesting
is
like
which
ones
drive
conversion,
and
can
we
like,
if
they
visit
this
page
and
they
and
they
view
that
content?
Can
we
accelerate
their
their
journey?
Basically,.
B
A
B
B
Okay,
so
one
it's
kind
of
slow.
So,
but
this
is
one
page
I
just
wanted
to
pull
up.
This
is
the
datadog
aws
go
together,
it's
not
perfect,
but
this
is
a
page,
I'm
kind
of
familiar
with,
because
it's
I
was
at
datadog
previously,
but
one
thing
that
they
do
here
is
they
kind
of
show
their
dashboard.
So
it's
a
little
bit
more
visual.
They
show-
and
I
know
day
dogs
a
little
bit
more
of
it's
a
different
solution.
B
So
it's
a
little
bit
more
visual
product,
but
they
kind
of
show
their
integrations
that
they
support
with
and
additional
resources.
So
I
guess
it
can
take
well
that
doesn't
help,
but
they
have
the
resources
where
people
can
go
to
their
blog
page.
So
I
guess
it's
a
little
bit
more
digestible.
It's
a
little
bit
short
it
might.
We
definitely
have
a
lot
more
content
we
want
to
put
in
our
page.
A
So
when
you
think
about
the
conversation
about
say,
say
someone
says
they're
going
to
sign
up
for
git
lab
and
they
want
to
use
aws.
Is
the
person
visiting
this
page
not
already
a
gitlab
user,
so
we're
trying
to
both
convert
them
to
gitlab
and
have
them
start
using
aws?
Or
is
this
page
proof
points
because
they're
already
a
customer
and
they
realize
they
want
to
integrate.
A
Stories,
one
thing
I'm
wondering
is:
if
we
should
have
a
so
like,
I
noticed
their
url
here
is
partner
aws.
I
wonder
if
we
should
have
partner
pages,
but
then
also
solutions
pages
and
not
try
to
cover
both
things
in
one
right.
So,
like
the
partner
page,
is
sort
of
like
a
shingle
where
we're
saying
hey,
we
work
with
this
company,
we're
credible
here's
how
to
get
started.
A
You
know
please
convert
and
it's
very
much
like
kind
of
feels,
like
the
new
user
experience
versus
solutions
being
like
a
deep
dive
like
oh
okay,
you
want
to
do
this
now
and
you
need
to
know
how
or
you
have
like
specific
questions.
We've
addressed
with
content,
I'm
just
wondering
if
there's
a
need
to
separate
the
two
things
in
your
mind,.
B
There
probably
is
because
now
I'm
thinking
about
it,
I
think
there
is
a
different.
Let
me
pull
up,
they
also
have
their
solutions
pay.
I
guess
this
would
be
their
kind
of
solutions
page
where
it
is
look,
you
could
do
all
your
aws
monitoring
and
it
kind
of
was
what
we're
showing
like.
It
shows
what
they
support.
Lambda
ec2
ecs.
B
A
I
mean
the
truth
is
making
another
page
and
breaking
that
out.
That's
not
a
lot
of
work.
We,
I
think
we
have
basically
all
the
content,
it's
more
of
like
a
curation
effort.
That
needs
to
happen
now
to
like
pick
and
choose
like
what
are
the
most
important
things.
What
are
the
goals
to
prioritize
like?
How
do
we
make
it
a
journey?
I
think
you
have
so
much
here
like
even
just
that
list
of
links
is
awesome,
but
I
think
the
thing
we
need
is
some
guidance
on
like.
B
A
B
The
one
on
gitlab
on
aws
yeah,
that
was
right
when
I
joined
we
were.
We
were
starting
to
set
that
up,
because
when
I
joined
so
we
hired
or
gitlab
hired
pete.
Who
is
our
alliance
manager
for
aws
here
and
he
was
like.
We
need
one
of
these
pages,
so
I
think
that
we
just
stood
it
up
very
quickly
so
that
we
have
something
because
he's
like
this
is
what
we're
missing
here.
So
it
really
was
like
a
quick
lift.
We
were
like.
A
Cool
that
makes
sense
yeah,
I'm
just
thinking
for
different
campaigns,
we'll
have
different
intentions
or
different
audiences,
so
maybe
that's
a
low-hanging
fruit
to
split
them
out,
and
I
think
this
fits
with
kind
of
we've
been
exploring.
You
know
like
what
should
the
what
should
about
get
lab.com
partners
like
what
should
live
kind
of
under
that
section
of
the
site
versus
solutions
right?
This
is
really
helpful.
A
I
don't
have
like
a
lot
of
contact
with
like
the
rest
of
the
partner
organization
kind
of
the
one,
the
part
that
kind
of
I
guess
falls
outside
of
marketing
like
michelle
hodge's
organization,
but
I
just
want
to
make
sure
that
you
know
we
okay,
one,
second,
that
we
take
advantage
of,
like
all
the
people
who
have
ideas
that
want
to
help,
because
I
think,
like
you,
have
enough
feedback
here,
we
can
make
an
iteration
and
make
this
a
lot
better
like
right
away.
If
you
want.
B
Yes-
and
I
think
that's
a
good
next
step-
and
one
thing
I
did
want
to
say
that
we
should
probably
include-
is
we
want
to
start
incorporating
partners
in
some
of
the
use
cases
that
we
support,
like,
for
example,
ci
that
we're
driving
that
campaign?
Some
of
these
can't
these
use
cases
that
we
highlight.
I
think
we
could
do
a
better
job
of
maybe
incorporating
this
on
incorporating
those
use
cases
and
how
we
do
that
with
partners
on
this
page.