►
From YouTube: Settings UX - Configure
Description
Maria and Michael discuss settings and the concept of landing pages for navigation
A
All
right,
yes,
so
today
we
have
maria
to
talk
about
settings
and
her
work
with
settings
and
if
there's
a
little
bit
of
overlap
with
time,
we
might
talk
about
some
navigation
stuff.
But
I
think
right
now
we'll
focus
mainly
on
settings
so
previously,
and
so
I
put
on
two
two
points
in
the
agenda
around
like
some
of
the
stuff
that
other
designers
mentioned,
that
you
worked
on,
such
as
standardizing
settings.
B
A
C
B
C
C
Cool,
so
I
haven't
done
any
work
on
them.
I've
seen
that
they
are
very,
very
content
heavy.
I
know
that
the
ux
research
has
proved
that
users
cannot
find
functionality
in
settings
and
they
have
required
a
search,
and
I
think
it
shouldn't
be
exactly
like
that.
So
the
way
I
view
setting
is
that
we
have
added
like
everything
there.
A
C
B
A
C
This
is
a
yes,
it's
a
well,
not
a
unique
case,
but
it's
one
of
the
cases
where
you
create
a
project.
It
might
be
an
application
project,
it
might
be
an
infrastructure
project,
so
the
functionality
of
projects
is
there
already
if
it's
a
terrafor,
if
it's
an
infrastructure
project-
and
you
write
terraform
code.
B
C
B
B
A
And
and
then
going
through
and
creating
all
these
issues
and
kind
of
like
looking
at
the
ui
right
now,
we
kind
of
lack
guidelines
on
in
pajamas
around
how
to
do
settings
to
you.
What's
a
good
example
of
settings
and
layout,
either
in
gitlab
or
outside
of
gitlab,
is
there
anything
that
resonates
with
you
as
like?
Oh,
yes,
all
our
settings
should
just
look
like
this
across
the
board.
C
B
C
A
B
A
A
A
C
I
hope
things
will
go
somewhere
with
it.
I
think
I
hope
we
adopt
the
proposal.
What
sparked
my
interest
is
that
we
have
such
a
complex
tool
and
it's
very
hard
to
find
functionality.
You
would
have
to
go
through
all
the
navigation
items
and
look
within
each
one
or
go
to
the
docs
and
get
lost
into
how
to
do
things.
C
B
C
View
them
as
a
good
summary
of,
what's
in
your
system,
also
a
good
place
to
link
different
pieces
of
functionality,
so
cross-stage
opportunities
for
user
flows
that
need
to
move
across
stages
and
and
also,
I
think,
the
main
thing
that
sparked
this
idea
was
that
our
stage
has
low
adoption
from
user
interviews.
We
found
out
that
people
who
use
geeklav
did
not
even
know
our
features
in
the
operation,
side
and
kubernetes
side.
So
I
thought
if
there
was
an
infrastructure
dashboard.
C
B
C
B
C
Deeper
to
see
which
application
is
running
on
which
piece
of
infrastructure,
so
I
thought
it
would
be
a
very
good
opportunity
if
we
introduced
at
some
point
the
dashboard
to
make
the
link
between
the
development
side
and
the
infrastructure
side
of
things.
So
that
sparked
the
idea
and
then
I
went
through
all
the
navigation,
and
I
saw
that
some.
In
some
cases
we
have
a
landing
page,
for
example,
issues
that
I
see
in
the
proposal
and
then
it's
the
same
as
the
first
menu
item,
which
makes
the
first
menu
item
redundant
right.
A
B
C
A
A
B
A
Navigation
improvements
are
part
of
the
ux
okrs
for
this
quarter,
so
we're
looking
at
different
ways
to
get
other
groups
involved
or
kind
of
tackling
key
problems.
First,
that
earlier
comment
that
you
made
earlier
about
consolidating
settings
into
one
place
and
having
search
kind
of
be
the
driver
towards
settings
is,
is
one
of
the
priorities
is
like
a
way
to
search
or
find
settings
so
that
that's
on
the
list?
A
A
As
I
like,
I
really
like
how
you
explained
it
like
showing
like
cross-stage
pieces
in
the
previous
company.
I
worked
for.
We
kind
of
did
something
like
that
to
help
exposure
or
discovery
of
new
features,
or
you
know
analytics
was
a
huge
one
to
like
sprinkle
throughout
the
whole
application.
So
that's
really
exciting,
so
I'll
probably
reach
out
to
you,
probably
in
the
future,
sometimes
for
some
feedback
on
left,
nav,
designs
or
other
navigation
things,
but
yeah.
I
just
want
to
give
you
a
heads
up
on
that.
One.
C
C
B
C
B
C
C
B
C
C
C
B
A
C
A
We
are
one
of
the
suggested
ideas
was
to
introduce,
so
you
can
see
my
figma
screen
yeah,
so
I
kind
of
had
the
same
idea
as
you
of
like
pulling
out
all
the
things
into
like
a
giant
this
on
the
side
and
potentially
so
they're
not
like
encapsulated
in
there,
whether
we
go
with
direct
to
a
search
at
the
top
or
intermediate
step,
that's
to
be
determined.
But
the
idea
here
is
probably
inspired
by
some
of
the
stuff
that.
B
A
That
would
be
this
specific
area's
settings
and
I
think
a
drawer
might
be
more
flexible
in
the
length
of
the
page,
because
some
stuff
like
what
you
just
showed
with
the
auto
devops.
It
was
like
two
radio
buttons
and
like
a
check
box,
but
there
could
be
other
things
where
it's
like
a
long
long
page.
So
it's
like
I've
seen
some
of
these
setting
pages
where,
like
they
are
definitely
pages
and
using
something
like
a
drawer,
might
be
helpful
to
surf
it
like.
A
Maybe
if
it's
too
long,
there's
a
link
to
say
like
view
all
your
settings
here
or
maybe
like
the
most
commonly
you
know
the
ones
you
would
change,
often
might
come
up
in
here
and
the
rules
around.
That
configuration
is
like
to
be
determined,
but
that's
kind
of
like
the
rough
idea
that
each
group
could
like
configure,
which
settings
that
they
want
to
pull
it
through.
A
Is
I
have
no
idea
but
yeah?
So
I
think
this
is
like
still
very
early
days.
I
just
mocked
this
up
to
like
have
something
tangible
to
talk
through
but
yeah,
so
this
idea
of
in
context
settings.
It
definitely
helps
with
something
complex
like
get
that
where,
if
we
send
you
to
settings
all
the
time,
it's
like
finding
a
needle
in
a
haystack.