►
From YouTube: Leftnav layout proposal
A
Hey
there,
my
name
is
michael
and
I
work
within
the
editor
group
here
at
gitlab
and
today,
what
we're
going
to
talk
about
is
the
left,
nav
and
more
specifically,
how
we
handle
the
left
nav
in
different
scenarios.
A
So
this
issue
was
brought
up
by
maria
a
few
months
ago,
and
the
idea
is
that
we
shouldn't
have
like
these
list
page
in
the
navigation,
because
it
overcrowded
navigation
and
doesn't
offer
additional
value.
Also,
it
causes
some
kinds
of
issues
where
there's
multiple
ways
to
click
to
an
issue
area
within
the
menu.
A
So
this
is
the
link
that
we're
talking
about
here.
Click
on
issues
will
take
you
to
the
list
or
clicking
on
the
list
will
take
you
to
the
list.
So
what
I
did
was
I
started
prototyping.
What
this
might
look
like
so
here
remove
the
list
page
and
clicking
on
issues
takes
you
to
issues.
So
if
we
go
ahead
and
kick
off
that
prototype,
that
pigment
do
its
thing
cool
so
with
project
overview.
Traditionally,
the
first
link
there
is
details
here,
it
will
be
project
overview.
A
So
if
I
just
click
through
some
of
these
things,
repository
like
files
is
the
first
item.
Normally
here
is
just
repositories.
Issues
merge
requests.
I
just
added
a
few
more
links
in
here
to
like
pad
it
out
just
to
see
how
that
would
look.
Requirements
is
an
interesting
one.
A
At
the
moment
it
has
a
sub
menu
called
list,
and
one
of
the
proposals
and
issues
is
potentially
to
remove
that
sub
item
and
just
have
requirements,
as
is
it's
not
bad
ci
cd
at
the
moment,
there's
no
like
list
page
for
a
ci
cd.
So
what
we
can
do
is
default
to
the
first
page
here
and
then
over
time.
We
can
look
at
introducing
a
dashboard
view
or
some
other
view
to
get
a
nice
landing
experience
to
these
different
areas
and,
as
we
click
through
here,
security
and
compliance.
A
A
But
if
we
look
at
operations
and
we
open
it
up,
operations
is
quite
unique
because
it's
quite
a
long
sub-menu
at
the
bottom
of
the
page
and
thus
pushes
a
lot
of
the
content
down
and
that,
if
you
see
like
every
time,
I
click
on
something
like
the
menu
kind
of
changes,
so
the
positions
of
stuff
changes
so
from
a
usability
standpoint,
things
keep
on
moving
for
you.
I
didn't
really
notice
this
until
I
started
looking
into
this
issue
a
little
bit
deeper,
so
I'm
I
did
some
exploration
on
this.
A
That's
fine
operations
is
what
we
just
talked
about
and
said
that
hey
this,
pushes
the
content
down
and
changes
the
position
of
where
I'm
used
to
clicking,
because
every
time
it
opens
and
closed
opens
and
closed
it
changes
potentially,
where
your
head
area
hotspot
would
be
to
hit
issues
or
repositories,
and
things
like
that,
so
I
thought
of
laying
out
the
menu
in
a
different
way
where
we
would
click
on
the
different
areas,
as
you
have
right
now,
but
for
each
section
it
would
open
up
in
its
own
like
side
menu.
A
The
beauty
of
this
execution
at
the
moment
is
that
it
takes
up
the
same
amount
of
space
as
the
current
expanded
menu.
So
from
a
layout
standpoint,
things
could
stay
the
same
and
from
a
from
a
menu
standpoint,
we
can
simplify
some
of
the
interactions.
A
There's
some
awkwardness
with
this
top
area
here,
whether
we
leave
it
or
not,
whether
clicking
on
it
takes
your
project
overview,
is
something
that
I'm
still
working
out.
So
if
we
remove
it,
we
have
a
nice
kind
of
clean
left
menu
with
a
home
icon
as
the
first
thing
and
all
the
different
areas
within
a
project
could
be
accessed
here,
and
you
have
clear
menus
over
here.
A
A
So
if
we
compare
and
contrast
some
existing
pages
and
how
that
looks,
is
on
the
left
hand,
side
here
is
our
current
experience.
Now,
let
me
see
if
I
can
minimize
myself
cool.
So
this
is
our
current
experience
where
we
have
ci
cd
and
all
these
other
things
potentially
distracting
you.
A
This
is
probably
something
to
be
solution
validated,
but
the
idea
here
is
that
if
we
just
keep
it
focused
on
ci
cd,
then
you
have
your
the
same
menu
and
even
allows
you
to
add
a
lot
more
many
more
menu
items
here,
if
you
really
needed
to,
but
it
keeps
you
focused
on
the
ci
cicd
area
and
all
the
other
areas
are
tucked
away.
One
of
the
things
that
we
don't
want
to
give
up
is
the
ability
that
we're
a
web-based
application.
A
A
So
nothing's
unlocked
there.
So
if
I
show
you
a
walkthrough
of
this
in
a
prototype,
we
can
see
how
this
pans
out.
A
I've
combined
the
idea
of
home
and
project
overview
into
one,
because
the
idea
of
having
the
project
overview
here
helps
identify
where
you're
at,
because,
with
this
current
execution,
you
don't
really
have
a
strong
presence
of
the
project
name,
but
we'll
go
into
that
in
a
bit
more
detail
in
a
little
bit
so
clicking
on
the
different
areas.
A
A
This
similar
execution
would
be
there
with
this
items
on
the
left
hand,
side
and
the
panel
here,
this
220
pixels
would
work
in
mobile
as
well,
where
it
gets
interesting
here
is
pages
that
don't
have
a
sub
menu
like
wiki,
so
wiki
is.
It
could
be
something
like
this
or
snippets.
A
We
could
consider
putting
like
a
title
so
that
you
know
where
you're
at
so.
I
believe
security
does
this
like
a
security,
dashboard
and
they're,
putting
a
title
at
the
top
for
snippets
and
wiki
and
then
settings,
and
we
get
into
this
kind
of
layout
as
well,
so
especially
from
settings.
The
sub
menu
is
no
longer
away
at
the
bottom,
but
it's
high
at
the
top,
so
people
can
find
what
they
need
to
the
theory
or
hypothesis
is
that
people
can
find
what
they
need
easily
here,
but
yeah.
A
The
links
for
the
prototype
and
comments
to
this.
It
will
be
placed
in
the
comments
below
a
little
bit
of
future.
Thinking
is
addressing
the
project
name
so
like,
as
I
said,
we
have
the
small
little
avatar
at
the
top
here,
which
is
kind
of
both
pro
project
overview
and
kind
of
a
sign
posting
of
which
project
you're
in
one
idea
to
make
the
project
name
more.
A
Prominent
is
to
put
the
project
name
at
the
top,
along
with
the
breadcrumbs
so
traditional
breadcrumbs
with
a
project
name
at
the
top,
and
some
of
you
might
be
curious
and
wondering
like.
What's
this
drop
down
doing
here
and
the
idea
of
this
drop
down
would
pull
up
a
list
of
recently
visited
projects.
A
This
would
allow
users
to
switch
contacts
project
contacts
with
while
they're
on
issues,
so
that
will
maintain
their
position.
This
is
something
that
will
be
solution
validated
again,
because
we
did
a
past
exploration
of
this.
The
execution
of
the
layout
was
still
in
its
infancy,
so
we
needed
to
refine
that
so
this
might
be
a
way
forward
for
that
and
in
the
world
of
groups.
How
that
would
work
is
the
group
name
would
be
there
clicking
on?
That
would
show
you
recently
visited
groups,
so
these
are
some
ideas
at
the
moment
and
yeah.