►
From YouTube: Navigation Update: 2021-09-29
Description
Last weeks update:
https://www.youtube.com/watch?v=f03CnWkEhGE
Links referenced in video:
- [Research] Evaluation of navigation proposals impacting the location of Deployments, Infrastructure and Package&Registry items in the left sidebar: https://gitlab.com/gitlab-org/ux-research/-/issues/1592
- [MR] Draft: Move Pages menu entry to top level: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70808
- [MR] Add guidance around top-level menu item additions: https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests/2553
A
Hey
everyone:
this
is
tori
davis.
I
am
the
product
design
manager
for
the
foundations
group,
I'm
going
to
go
over
just
a
few
updates
from
navigation
since
the
recording
last
week.
If
you
didn't
see,
last
week's
video
I'll
go
ahead
and
link
it
in
the
video
description
here
so
for
this
week,
I'll
start
by
updating
everyone
on
requirements.
A
A
A
So
next,
just
a
quick
update
on
the
research
that's
happening
regarding
deployments,
infrastructure
and
package
and
registry
anna
is
working
on
the
script
for
this,
and
I
have
a
meeting
with
her
tomorrow
just
to
discuss
any
lingering
questions.
A
The
goal
is
to
get
this
script
complete
prior
to
next
wednesday,
and
anna
has
also
been
working
with
adam
on
ways
to
speed
up
the
recruitment
process,
because
for
a
similar
study
we
did
a
few
milestones
ago.
I
think
it
took
around
six
weeks
to
recruit
all
the
participants
that
we
needed
and
we
hope
that
using
another
tool
will
really
speed
up
the
recruitment
process
and
just
make
it
easier
and
faster.
A
So,
lastly,
for
today
I
wanted
to
highlight
this
recent
proposal,
which
was
to
move
pages
from
a
sub
nav
item
within
settings
to
a
top
level
navigation
item,
and
the
reasoning
was
twofold.
The
first
was
that
we
wanted
to
highlight
the
new
jam
stack
functionality,
that's
being
worked
on,
and
the
second
was
to
ensure
that
there's
space
within
the
navigation
to
build
out
future
functionality.
A
This
proposal
was
closed
because
it
reflects
really
the
same
reasoning.
That
requirements
was
introduced
at
a
top
level
menu
item
originally,
which
we
just
moved.
They
are
looking
at
whether
pages
would
be
better
suited
within
another
area
such
as
maybe
deployments
as
a
sub
nav
item.
A
As
a
result
of
this
merge
request,
I
started
drafting
some
guidelines
in
pajamas,
which
includes
documentation
for
proposing
new
top
level
menu
items.
So
this
merge
request
states
that
new
editions
are
very
deliberate.
They
should
they
should
be
informed
by
data
that
supports
that
their
key
or
foundational
functionality
within
our
devops
platform.
A
So
if
we
want
to
improve
discoverability,
then
we
should
look
for
other
opportunities
within
the
product
to
really
intelligently
highlight
those
features
to
users,
and
if
we
believe
that
there's
going
to
be
additional
functionality
for
a
given
feature,
then
we
should
be
forward
thinking,
but
we
shouldn't
over
optimize
our
navigation
for
what
may
be
what
we
may
need
later.
So,
as
features
are
developed
and
added,
we
can
look
into
what
changes
may
need
to
occur
to
support
that
growing
feature.