►
From YouTube: Dashboard working group - final read out
Description
Deck: https://docs.google.com/presentation/d/1aKwDedARPW9rto_3cgGHZSiXyloParEy3-s_gprXlig/edit#slide=id.g12b319f6181_0_0
Final MR: https://www.google.com/url?q=https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/3260/diffs
Pajamas: https://design.gitlab.com/patterns/dashboards
A
We
wanted
to
progress
towards
a
consistent
UI
in
our
dashboards
and
the
nomenclature,
a
big
thanks
to
the
working
group
Team.
Without
them,
this
would
not
have
been
possible.
There
was
so
much
discussion
and
amazing
output
by
everyone
on
the
team.
So
thank
you
so
much
so
what
brought
us
together
was
the
question
of
having
so
many
different
uses
of
dashboards
in
gitlab
and
wanting
to
align
them
in
some
way.
A
We
came
up
with
four
goals:
one
align
on
priorities
and
unblock
feature
teams
to
build
with
dashboards
home
pages,
landing
pages
or
user
page
Concepts
and
know
what
that
is:
create
a
solid
nomenclature
and
usage
guide
for
dashboards
Define.
What
a
dashboard
is,
and
even
more
importantly,
what
it
isn't
and
determine
the
correct
naming
and
use
for
observability
and
new
graphs
inside
of
dashboards.
A
As
a
team,
we
made
three
phases
to
our
work.
First
was
investigation,
then
we
mapped
all
the
pieces
and
then
we
Define
all
of
the
objects
so
that
that
was
the
core
phases.
We
go
through
the
first
phase
started
in
December
and
we
gathered
all
dashboards
at
gear
lab
into
one
big
long
list.
So
you
can
see,
we've
got
a
list
of
30
here.
We
also
had
some
other
internal
tools
and
graphing
tools
within
this.
A
Here
we
are
Illuminating
six
of
the
top
ones,
and
you
could
see
with
the
color
coding
here
that
mapping
those
regions
on
the
dashboard
is
vastly
different.
Even
amongst
these
top
six.
So
we
could
align
all
30,
but
we
chose
the
most
important
and
then
use
those
as
guides
as
we
move
forward
into
this
into
a
definition,
phase
and
mapping
out
UI
components.
A
So
we
took
all
the
large
regions
and
then
mapped
smaller,
so
in
a
spreadsheet,
We
Had,
Each,
dashboard
item
from
the
dashboard
itself
down
to
panels
down
to
filters,
and
we
thought
through
every
component
that
may
or
may
not
be
included
based
on
what
what
we
saw
from
the
observability
team
from
value
stream
dashboards
from
everything
else
among
skit
lab
and
the
core
areas
are
the
dashboard
and
the
panels.
And
then
we
had
a
lot
of
discussion
around
filters.
Should
they
be
on
panels?
Should
they
only
be
Global?
A
Can
they
be
both
we
landed
on
both
and
a
lot
of
the
different
elements
are
all
listed
there.
The
way
we
did
it
was
we
had
an
agreement,
con
column
and
basically
the
ones
we
didn't
have
agreement
on.
We
would
sync
and
we
would
talk
them
through
in
the
at
the
end
of
the
definition
when
we
were
ready
to
move
forward,
we
took
it
to
an
MR,
and
that
was
our
exit
criteria
to
complete
the
working
group
was
to
have
a
pajamas
Mr
up,
and
so
here
you
can
see.
A
We
now
have
a
full-fledged
dashboard
section
in
pajamas
that
describes
all
of
the
concepts
that
we
came
up
with.
So
we've
got
the
definitions,
layout
guidelines
and
behavior
for
all
of
the
different
parts
of
the
dashboard.
So
I
suggest
you
go
and
look
at
that
and
give
your
feedback.
If
you
have
anything
that
you
see,
you
can
make
better
foreign.
A
Field
definition
of
dashboards
was
that
we
did
have
a
legacy
definition
of
dashboard
and
pajamas.
That
was
wrong
based
on
our
new
new
understanding,
so
that
was
a
really
cool
thing
to
update.
So
before
we
were
calling
up,
the
home
page
link
a
dashboard.
We
made
a
modification
and
we
also
gave
a
very
precise
definition
of
a
landing
page.
A
landing
page
is
the
page
directly
tied
to
a
link
in
the
navigation.
A
Typically,
a
landing
page
is
action,
oriented
and
contains
overview
or
summary
content,
but
it
can
also
be
a
dashboard
for
analysis,
oriented
tasks
so
that
definition
took
a
lot
of
time
to
get
to
having
that
definition
helped
us
answer
what
a
dashboard
is
not,
which
was
another
major
part
of
this.
So
looking
at
the
gitlab
app
currently
I'm,
showing
current
behavior
when
you
hover
on
an
avatar
right
now,
it
says
dashboard.
A
A
The
tldr
rules
for
this
are
that
when
you
click
the
Avatar,
the
link
is
called
your
home.
Page
landing
pages
are
landed
on
directly
from
navigation,
so
it's
a
very
broad
term
and
the
two
general
types
of
landing
pages
are
analysis,
oriented
which
are
dashboards
or
landing
pages
that
are
action
oriented
which
might
be
something
like
an
issue
list
where
you
take
action.
A
Next
steps
we
want
to
circulate
the
definitions
within
product
and
design,
which
is
this
video
and
start
conversations
with
consistent
terminology
begin
to
gradually
convert
existing
dashboards
to
the
standard.
We
created
an
issue
to
update
the
current
dashboard
setting
to
be
home
page
and
we
could
consider
future
iteration
on
the
current
homepage,
behavior
that
aligns
with
the
new
navigation.
So
that's
something
we
want
to
look
at.
Do
we
want
to
change
that?
Avatar
behavior?
Is
that
something
we
could
iterate
on
in
the
future?
A
We
hope
that
all
of
you
can
participate.
Give
us
feedback.
Look
at
the
pages
make
Mrs.
We
did
the
best
that
we
could
with
what
we
had,
but
we're
sure
that
there's
going
to
be
more
insights
as
we
go
along,
so
we
look
forward
to
hearing
what
you
all
bring
forward,
and
hopefully
we
can
all
take
the
next
steps
to
start
driving
consistency
in
the
dashboards.