►
From YouTube: Left navigation improvements scheduled for 14.0
Description
Overview of improvements to the left navigation currently scheduled for the GitLab 14.0 release.
Link to epic: https://gitlab.com/groups/gitlab-org/-/epics/4843
A
Hi
everyone
I
wanted
to
talk
through
what
we
have
in
store
for
the
left:
navigation
for
the
14.0
release,
it's
kind
of
spread
between
multiple
issues
and
epic.
So
I
wanted
to
just
record
this
and
and
make
sure
that
it's
clear
what
our
goals
are
and
and
where
we,
how
we
got
here
so
based
on
the
research
that
we've
been
doing
over
the
past
few
milestones,
some
of
it's
still
in
flight
and
we're
validating
a
few
other
things
ongoing.
A
But
the
goal
overall
has
been
to
increase
the
overall
usability
of
the
left,
navigation
and
findability
of
various
features.
So
we've
identified
several
changes
that
we
can
make
to
the
information
architecture
as
well
as
some
ui
and
ux
patterns
that
we
can
update
to
improve
the
left
navigation.
We're
trying
to
bundle
this
all
into
the
14-0
release
to
reduce
the
amount
of
churn
and
change
that
happens
in
that
left
navigation.
A
So
the
largest
and
most
visible
change
will
be
related
to
the
actual
categorization
of
some
of
the
left
navigation
items.
We
ran
some
card
sorting
tests
and
found
that
the
overall
success
rate
for
our
proposals
varied.
So
we
had
some
assumptions
that
we
had
to
rethink
because
the
findability
was
actually
lower,
but
the
ones
that
were
clear,
wins
we've
documented
and
we
plan
on
implementing
specifically
around
breaking
up
the
operations
menu
and
moving
a
couple
top
level
items
around.
So
this
is
an
example
of
what
it's
going
to
look
like.
A
A
So
the
most
clear
example
in
this
issue
refers
to
the
requirements
that
has
like
a
top
level
item
and
a
list
view
those
both
go
to
the
same
place
right
now,
they're
a
little
repetitive
and
unnecessary.
So
we've
got
a
proposal
for
some
ui
changes
that
will
simplify
that,
especially
when
it's
in
the
collapse
mode.
So
this
is
also
probably
most
prevalent
here
at
the
at
the
home
page
for
the
project.
A
So
right
now,
this
project
overview
actually
has
three
different
places
that
you
can
get
to
it
and
they
take
up
the
top
three
links
in
that
left.
Nav,
the
get
lab
project
name
as
well
as
the
project
overview
and
the
details
link
all
go
to
the
same
place
when
you
click
them.
It's
a
little
repetitive
and
takes
up
an
awful
lot
of
vertical
space.
A
So
we've
got
some
patterns
to
simplify
that,
at
the
same
time,
we're
looking
to
improve
the
overall
ui
and
styling
to
introduce
a
little
more
contrast
and
separation
from
the
the
body.
Content,
reduce
visual
noise
but
maybe,
most
importantly,
reduce
the
amount
of
vertical
space
so
that
it's
more
likely
that
you
can
see
all
the
items
at
once
on
a
normal
size
screen,
and
you
can
see
kind
of
the
overall
effect
of
all
of
this
in
this
figma
file
here
and
you
can
see
what
we're
proposing
with
the
left
nav
right
here.
A
So
you'll
notice
that
we've
got
you
know
our
deployments
and
monitoring
infrastructure
categories.
Those
are
relatively
new:
we've
got
a
new
styling,
we've
got
a
more
consolidated
vertical
spacing
and
you
can
see
here.
The
difference
between
the
two
is
pretty
dramatic,
so
everything
can
fit
on
an
overall
13-inch
macbook
screen.
Whereas
now
you
have,
you
know
four
and
a
half
items
that
are
cut
off
and
one
of
those
items
being
settings
which
can
be
very
important
and
you
may
not
even
know
that
we
have
them
there.
A
So
on
the
topic
of
settings,
we're
going
to
try
and
introduce
a
couple
other
changes
into
the
left
nav
because
settings
lives
on
the
left
nav,
it's
probably
important,
to
highlight
here
related
to
settings.
One
of
the
big
friction
points
that
we've
identified,
that
we
have
a
very
clear
mvc
to
solve.
A
Is
that
merge
request
settings
are
difficult
to
get
to
they're
buried
under
general,
so
we're
just
going
to
create
a
new
top
level,
merge
request
section
under
settings,
and
this
will
make
it
much
easier
to
get
to
as
well
as
make
it
so
that
we
can
target
it
using
a
an
actual
url
rather
than
a
path
to
the
general
settings
we've
also
talked
about.
I
don't
have
a
mockup
for
this
right
now,
but
moving
some
settings
into
the
left,
nav
bar
alongside
the
features
themselves.
A
This
issue
is
for
ci
cd,
but
we're
also
considering
it
for
repository
and
merge
requests,
and
this
will
be
an
experiment.
A
What
we
would
do
is
introduce
a
link
into
the
left,
nav
that
actually
just
links
you
into
settings
right
now,
because
the
actual
implementation
of
it,
where
you
would
break
up
the
monolithic
settings
view
it
would
take
a
significant
amount
of
effort
and
not
be
ready
for
14
hours.
So
we're
going
to
try
out
an
nvc
where
we
link
to
settings
from
the
left,
nav
and
sort
of
deep
link
into
that
settings
view
and
see
how
it
helps.
A
That's
all
I
wanted
to
highlight:
there's
a
little
bit
more
in
there
and
the
the
issues
and
and
epics,
but
if
you
have
any
questions,
feel
free
to
visit
the
issues
or
hit
me
up
in
slack
thanks
a
lot.