►
From YouTube: Navigation Update: 2021-11-05
Description
[Epic] Projects - Visibility Settings - Consistently allow for features to be disabled and removed from the left nav: https://gitlab.com/groups/gitlab-org/-/epics/3719
A
Hey
everyone,
I'm
tori
davis
and
I'm
the
product
design
manager
for
the
foundations
group.
Today,
I'm
going
to
give
an
update
on
navigation
and
it'll
be
focused
on
visibility
settings.
I
did
two
previous
video
updates
on
how
our
visibility
settings
affect
the
navigation
within
projects.
So,
if
you
haven't
had
a
chance
to
look
at
that,
you
may
want
to
okay.
So
let's
start
today
by
looking
again
at
this
epic,
that
is
for
consistently
allowing
features
within
our
project
navigation
to
be
disabled.
A
A
quick
shout
out
to
anup
for
leaving
this
comment
here
after
my
last
video,
where
he
asked
about
the
cognitive
load
of
adding
all
of
these
features
to
the
visibility
settings
and
if
there
are
any
downsides,
he's
exactly
right.
Even
if
we
look
at
the
visibility
settings
that
we
have
today,
we
have
this
long
list
that
can
be
hard
to
parse
and
especially
hard
if
we
continue
to
add
more
options.
A
So
for
that
reason
I
went
ahead
and
I
created
this
design
issue
where
we
can
look
at
it
more
holistically
and
where
we
can,
I
ideate
on
a
new
ui
that
really
supports
adding
more
visibility.
Settings
as
well
as
takes
takes
into
consideration
all
of
the
dependencies
that
that
occur
when
enabling
and
disabling
some
of
our
settings
within
the
navigation.
A
A
So
these
two
design
issues
are
are
two
that
we
want
to
tackle
coming
up
before
doing
that,
I
did
go
ahead
and
create
some
sub
epics
within
the
main
visibility
setting,
epic,
that
we
were
just
looking
at
so
there's
sub
epics
for
each
of
the
different
navigation
sections
that
you
find
within
a
project
and
then
within
those
sub-epics
there's
issues
for
allowing
users
to
disable
the
individual
sub-menu
items
within
each
of
these
sub
epics.
I
pinged
the
designers
who
are
the
dris
for
these
areas.
A
I
provided
a
summary
of
the
objective
and
then
I'm
asking
each
of
them
to
review
whether
or
not
it
makes
sense
for
each
of
these
specific
areas
to
be
disabled
individually
and
if
so,
then
we'll
want
to
list
out
any
dependencies
that
there
may
be,
and
it's
also
really
awesome,
because
the
designers
have
already
started
adding
a
lot
of
thoughts.
So
just
shout
out
to
them.
Thank
you
so
much
for
for
taking
a
look
at
this
and
and
helping
out.
So
let's
look
at
an
individual
issue
within
each
of
these
individual
issues.
A
I
list
the
problem
to
solve
and
link
to
the
main
epic,
the
user
experience
goal
is
listed
and
then
there's
a
section
for
further
details,
which
is
where
we'll
want
to
list
the
dependencies.
So,
for
example,
when
disabling
pipelines,
you
would
also
want
to
disable
editor
jobs
and
schedules
in.
I
think
it
was
the
last
video
that
I
did.
A
I
talked
a
little
bit
more
about
some
of
the
dependencies
that
I'm
aware
of,
and
this
effort
is
really
to
get
all
the
teams
who
are
closer
to
these
sections
to
provide
their
expertise
from
there
we'll
be
able
to
map
all
the
dependencies
and
go
back
to
this
more
holistic
design
exploration
issue.
To
start
creating
an
experience,
that's
really
just
more
intuitive
and
thoughtful,
and
doesn't
it
doesn't
introduce
that
cognitive
load?
That
anup
was
was
talking
about
in
his
comment.