►
Description
Handbook page:
https://about.gitlab.com/handbook/engineering/ux/experience-baseline-recommendations/
Issue:
https://gitlab.com/gitlab-org/gitlab-design/issues/480
A
Hi
and
welcome
to
the
experience
baseline
at
baseline
effort
for
the
verify
stage
group
focusing
in
on
setting
up
get
lab
CI,
so
the
experiment,
baseline
effort,
including
the
recommendation,
has
come
out
of
it.
It's
done
because
of
certain
reasons.
Let
me
explain
why,
by
reading
out
this
little
section
from
our
handbook
page
as
UX
practitioners,
we
must
think
strategically
about
fixing
usability
challenges
within
the
gate
lab
product.
Creating
an
experience
baseline
with
associated
recommendations
enables
us
to
identify
scope
and
track
the
effort
of
dress
muse
ability
concerns
within
a
specific
workflow.
A
A
But
what
we'll
be
doing
is,
let's
show
you
the
journey
of
this,
of
the
experience
baseline
in
this
video
and
it
click
through
video,
basically,
which
will
be,
and,
at
the
end,
we'll
be
giving
a
grade
using
this
grading
rubric.
This
will
essentially
set
up
the
baseline,
which
we'll
be
trying
to
improve
with
your
recommendations
that
follow
it
so
for
this
after
I
set
up
an
issue
that
includes
all
information
that
comes
out
of
this
effort,
I'll
be
sure
to
include
it
into
the
YouTube
video
description.
So
it's
easy
to
find.
A
One
thing
to
be
known
to
be
noted
out
is
that
the
job
to
be
done
where
we're
going
to
focus
in
on
is
when
I
have
created.
My
project
I
want
to
set
up
an
automated
testing
inside
get
lab,
so
I
can
assure
every
commit
before
merging
our
assumption
is
that
we're
going
to
perform
as
our
dev
on
dev
ops,
engineering,
persona
user,
the
matches
that
persona,
in
other
words,
and
with
that,
let's
move
on
to
the
customer
journey
inside
this
testing
project.
A
Looking
further
I
see
that
we
have
some
options
here,
including
enabling
all
the
DevOps
adding
two
entities
clusters
and
eventually
setting
up
ci
City,
which
is
basically
what
I'm
trying
to
do
here.
This
seems
to
be
the
most
obvious
point,
but
at
the
same
time,
I
would
say
that
there
it
is
one
of
many
options
and
it's
quite
subtle
subtly
presented
within
the
product.
A
A
A
A
A
So,
let's
consider
to
this
eigen
is
not
visible
and
there's
no
indication
of
something
happening
in
the
background
other
than
that
with
that
I'm
left
in
this
state,
where
I'm
unsure
how
to
proceed,
for
which
I
ventured
into
the
left
sidebar
for
that
left,
sidebar
there's
only
one
true
indication
for
CI,
CD
or
CI,
specifically,
which
is
the
sea
ice
beam
and
menu
island
bar
kind
of
interested
in
my
pipeline
seat.
Then
he
was
running.
A
So,
let's
click
on
that
and
with
that
I'm
moved
apparently
to
the
pipeline
ELISA
page
I
can
see
that
it
failed.
It
was
triggered
by
me
indeed
I
added
the
killaby
I
yeah
also
apparently
runs
off
this.
This
file
being
added
with
it
being
pushed
triggered
the
pipeline,
and
there
are
some
stages
and
within
that
stage,
apparently
got
a
single
one,
which
has
been
failed,
as
both
jobs
are
filled.
Added.
A
Moved
into
the
pipeline
detail
page,
it
seems
and
see
this
indication,
apart
from
the
status
buttons
that
I
move
into
the
failed
jobs
tab.
Let's
do
that
and
it's
nice
to
see
that
I'm
able
to
see
exerts
showing
me
the
job
failed,
a
summary
of
what
information
it
tells
me
why
this
job
failed.
Apparently
there
are
some
modules
not
found
which
is
actually
the
same
in
both.
A
So
what
I
need
to
do
I
think
is
going
back
to
the
git
lepsy
I
am
oh
I
know,
let's
see
what
it's
missing,
because
it's
missing
some
some
modules.
So
let's
do
that.
There's
no
clear
path
to
that!
Get
lab
CI,
yeah,
no
configuration
but
I
know
that
probably
can
go
to
the
repository
to
the
project
homepage
where
the
projects
were.
Cluster
is
also
shown.
A
So
I
clicked
on
that
see
that
my
CI
semi
configuration
is
set
up
here
as
well.
That
button
has
changed
it's
quite
nice,
actually
click
on
it
and
I'm
back
to
the
place
where
it
was
before.
So
if
we
can
see
here,
it's
it's
expecting
some
node
modules
or
some
these
files
actually
inside
every
job,
there's
some
different
ones
but
they're
in
both.
So
let's
edit
these
out
and
see
if
we
can
get
the
pipeline
green.
A
A
We're
going
to
move
back
so
here
we
see
an
example
when
it
doesn't
mediately
show
the
pipeline
status
within
this
view,
which
is
what
I
explained
before
so.
With
this
we
got
no
indication
of
the
pipeline
being
started
of
running
or
anything
like
that.
The
only
next
key
we
have
is
lead
again
that
CI
CD
sidebar,
which
we'll
click
on
and
after
that
we
see,
indeed,
that
our
pipeline
is
running,
which
is
good.
A
A
A
Or
give
up,
CI
isn't
set
up
and
actually
triggers
after
every
commit,
which
is
quite
nice.
So
with
that
the
experience
baseline,
walkthrough,
video
or
review
of
the
customer
journey
along
this
job
to
be
done
is
completed,
and
a
last
note
of
that
is
that
I've.
Given
this
experience,
an
average
workflow
clearly
needs
some
improvements
here
and
there
there's
some
shortcomings.
A
We
don't
may
take
the
use
a
little
bit
longer
to
complete
the
test
and
shoot,
and
sometimes
it's
not
really
clear
how
to
proceed.
So
it
might
be
easy
for
the
user
to
abandon
the
process
or
try
again
later
there
are
some
unnecessary
complexity
or
necessary
steps.
I
think
the
mismatch
between
the
template
and
the
project
is
also
something
to
worry
about,
but
hey
that's
up
for
recommendations
and
see
how
we
can
improve
this
baseline
experience.
Thank
you
for
following
along
be
sure
to
check
out
the
issue
always
feel
free
to
leave
any
feedback.