►
From YouTube: Navigation updates: 2022-05-20
Description
If you'd like to contribute to the discussion, then feel free to share your thoughts in the related design issue - https://gitlab.com/gitlab-org/gitlab/-/issues/362396
A
Hi
there,
my
name
is
austin,
I'm
a
senior
practice
center
on
the
foundations,
team
and
I'll
be
talking
through
some
navigation
concepts.
Today,
one
of
the
first
things
that
we
wanted
to
look
into
since
I've
joined
the
team
is
the
hamburger
menu
that
is
in
the
global
nav.
So
when
I'm
talking
about
that,
I
am
talking
about
that
little
hamburger
icon
that
shows
up
with
the
word
menu.
A
Next
to
it
now
we've
started
implementing
some
user
tracking
to
better
understand
how
users
are
navigating
through
the
global
navigation
context,
as
well
as
that
menu
itself
so
below
I've
highlighted
a
few
areas
that
don't
have
tracking
on
them
just
yet,
but
based
off
of
just
even
some
of
our
user
research
that
we've
done
and
the
verbatims
that
we've
heard
from
that.
These
are
less
frequently
visited
areas
primarily.
A
What
we're
seeing
for
that
hamburger
menu
item
is
it's
used
for
switching
between
groups
and
projects,
but
if
we
look
through
the
click
data
users
are
primarily
using
the
user
profile
and
the
gitlab
logo
to
go
to
places
beyond
that.
They're
looking
for
their
frequently
visited
projects,
probably
their
merge
requests
and
then
beyond
that
we're
trying
to
find
usually
their
project,
sometimes
their
group.
A
So,
there's
a
strong
gravitational
pull
towards
this
menu
item,
which
we
could
definitely
find
a
better
solution
for,
at
least
in
my
mind,
so
I'm
outlining
a
few
of
the
goals
that
we
want
to
do
on
the
right
here.
First,
we
want
to
help
reduce
this
visual
clutter
if,
for
example,
these
yellow
sections
aren't
useful
to
users,
we
really
want
to
try
and
reduce
the
number
of
things
that
are
right
in
front
of
them
and
focus
on
the
most
highly
utilized
paths.
A
In
addition
to
that,
we
don't
want
to
necessarily
create
more
friction,
but
we
want
to
make
sure
that
things
are
clearly
organized,
because
that's
another
thing
that
we
hear
about
in
our
feedback
is
that
things
that
are
not
necessarily
the
same
will
appear
in
the
same
area.
So
one
way
you
can
think
of
this
is
projects
and
groups
can
be
thought
of.
As
like
a
scope
and
the
rest
of
these
list
items,
maybe
excluding
the
admin
area
could
be
considered.
A
The
key
thing
that
we
really
want
to
focus
on
is
just
that:
we're
not
going
to
negatively
impact
users
ability
to
find
their
groups
and
projects,
that's
already
challenging
enough
for
them.
So,
ideally,
they
come
out
with
a
simpler
way
to
do
that,
but
at
least
we
don't
want
to
impact
that
negatively.
A
So
the
first
idea,
I'm
going
to
be
sharing
is
one
around
using
global
search.
There
have
been
a
lot
of
improvements
with
global
search.
One
things
I
personally
have
loved
is
that
you
can
actually
search
for
your
group
or
project
or
even
recently
visited
issues
or
merge
requests
to
help
with
the
discovery
of
this
feature.
Instead
of
having
that
hamburger
menu,
users
would
interact
with
the
search
bar
itself.
This
is
a
pattern.
That's
been
starting
to
appear
in
a
number
of
products
and
to
keep
this
focus
more
on
nbc
solution.
A
We
would
keep
things
like
the
frequently
visited
list,
which
we
know.
Users
would
probably
like
more
of
a
recently
visited,
rather
frequently
that's
more
of
a
technical
hurdle
we
need
to
get
over
in
the
future
and
instead
of
giving
them
numerous
links
around
groups
and
projects
just
saying
projects
and
groups,
it
takes
them
all
to
the
same
place,
anyways
and
it's
just
one
more
click
to
whatever
filter
they
would
like
for
that
particular
scope,
noting
that
administrators
also
still
need
to
get
to
the
place.
A
They
need
to
go
we're
going
to
leave
that
here
and
by
default.
You
still
get
some
filters
currently
the
global
search
that
we
could
keep
it
initially,
but
we
could
consider
changing
or
moving
becomes
too
much,
so
we
would
want
to
basically
test.
Can
users
go
find
a
their
start
projects?
So
we'd
say:
where
would
you
go
see
where
they
click?
Ideally,
they
can
go,
find
their
start
projects.
A
A
A
So,
instead
of
having
individual
pages
for
each,
we
would
tie
them
in
a
single
dashboards
area
to
help
use
that
left
sidebar
as
an
anchoring
point
and
to
travel
between
those
things.
You
might
be
wondering
why,
underneath
the
user
profile
well,
these
dashboards
are
unique
to
each
user,
so
the
security
dashboard
is
unique
to
me,
the
environments
as
well
and
operations.
This
activity
is
scoped
to
my
activity.
The
things
that
I'm
following
these
are
part
of
my
milestones
and
it's
going
to
jump
into
my
snippets.
A
A
Next,
this
one
calling
the
navigator
so
instead
of
using
a
hamburger
icon,
which
can
be
a
bit
confusing
because
when
you're
in
a
mobile
view,
you'll
see
two
hamburger
menus
using
a
grid
of
dots
to
indicate
that
there
is
a
way
to
switch
now.
This
would
be
a
similar
interaction
to
what
we
were
seeing
with
the
global
search,
but
we're
trying
to
keep
these
two
functions
tied
closely
together.
A
So
this
would
be
the
way
you
switch
between
your
scopes
and
the
search
bar
would
be
how
you
can
continue
to
search
for
your
groups
and
projects
or
issues.
This
would
be
a
less
dramatic
change,
but
it
would
definitely
change
the
menu
to
be
more
aligned
with
our
typical
drop
down
style
rather
than
the
full
layout
that
we
have
today.
A
So
again,
we're
going
to
be
testing
similar
paths
getting
into
those
projects.
How
would
they
get
back
and
again
that
that
user
profile
dashboard
option
is
still
there
and
then
the
third
option
that
we
want
to
test
is
one
that
brings
the
scope
out
of
the
left
sidebar
so
that
it's
always
globally
accessible.
A
Is
there
any
others?
This
is
technically
the
security
dashboard.
You
get.
The
name
of
your
project
or
group
listed
there,
so
we'll
be
pulling
that
up.
This
means
that
we
have
to
give
a
landing
spot
in
the
left
sidebar.
So
as
a
parent
item
overview
will
be
put
there.
The
downside
of
that
is
we're
adding
another
thing
to
this
list,
which
we
know
is
already
pretty
long,
but
this
would
help
users
always
know
where
they're
at,
and
it
would
continue
to
use
that
top
left
side
as
a
navigational
pattern.
A
So
from
here,
if
I
was
trying
to
switch
out
this
project,
maybe
to
find
all
my
projects
using
that
same
kind
of
menu
drawer,
as
we
had
before,
I
could
go
and
explore
projects,
and
now
my
context
has
changed
again
trying
to
focus
on
like
where
are
you
at?
Currently,
there
is
a
little
bit
of
redundancy
just
given
the
fact
that
we
have
page
labels
right
now,
as
well
as
that
being
in
the
top
as
well,
but
just
trying
to
keep
that
in
mind,
you
know
users
could
still
find
those
dashboards.
A
Let's
say
we
want
them
to
find
the
security
dashboard.
This
would
be
just
trying
to
help
focus
like
what
are
the
different
scopes
you
can
have.
So
these
are
basically
the
places
that
you
might
be
able
to
find
that
left,
sidebar,
or
rather
just
the
collection
of
items
that
would
be
navigating
to
specific
tasks.