►
From YouTube: Settings UX - Create:Editor
Description
As part of the overarching initiative to improve the GitLab Settings experience, we will collect existing user feedback and proposals in order to drive user experience and SUS score improvements for settings. This is a conversation with Create:Editor
More on https://gitlab.com/groups/gitlab-org/-/epics/3535
A
C
I
can
go
over
a
few
things
that
we're
looking
at
right
now,
I
think,
would
probably
be
the
most
useful
not
to
say
we
haven't
done
other
stuff
before,
but
it
was
pretty.
You
know,
run
in
the
mill
kind
of
stuff
of
you
know
looks
like
every
other
settings,
it's
just
it's
just
another
setting
in
there.
I
don't
think
nothing
really
in
the
past
was
standing
out
is
super
special,
so
we
have
a
couple
things
going
on
right
now
related
to
settings.
C
So
there's
a
lot
of
like
kind
of
this
is
how
it
exists,
and
I
I
think
if
we
were
to
redo
it
today
from
the
ground
up,
we
wouldn't
do
it
this
way,
but
we're
kind
of
stuck
now,
because
this
is
how
they
exist
and
there's
ones
that
are
out
there
in
the
wild
and
it's
kind
of
a
struggle
of
what
you
do
about
that.
I'm
trying
to
pull
up
the
the
issue
for
it
right
now,
so
I
can
show
you
what
I'm
talking
about.
A
A
B
C
C
Let's
take
a
look
here
in
13.5,
maybe
it's
actually
back
in
the
backlog
now.
So
I
don't
know
when
we're
gonna
get
to
this,
but
this
is
what
I
was
talking
about
is
that
this
is
a
this
is
how
basically
project
settings
would
work
right.
Is
that
normal
files
and
entities
in
a
project
file
kind
of
follow
the
developer,
maintainers
and
authors
unless
you're
controlling
them
some
other
way,
which
has
not
been
the
case
in
snippets,
so
we're
talking
about
adding
an
option
to
make
them
follow
that.
C
D
C
What's
odd
about
this,
is
this:
this
exists
outside
of
the
settings,
so
snippets
have
always
kind
of
been
weird
in
that
sense
that
you
kind
of
would
expect
that
to
bend
in
settings
themselves,
and
there
are,
you
know
some
some
snippet
settings
that
are
there
but
kind
of
what
has
made
them
a
bit
of
an
outlier
a
little
strange,
but
I
think
we
would
just
pull
them
back
into.
You
know
the
normal
snippet
model,
but
again
these
are
out
there
in
the
wild
and
you're
gonna
break
things.
C
C
There's
there's
various
reasons
why
we
find
we've
found
a
couple
of
use
cases
where
people
actually
do
want
to
switch
back
and
forth.
You
know
it
we
kind
of
thought,
maybe
initially
this
would
be
kind
of
thing.
You
said
it
and
I
forget
it,
but
there
are
some
use
cases
where
people
do
want
to
go
back
and
forth
between
them.
So,
unfortunately,
what
we're
looking
at
now
is,
if
you
want
to
make
the
change
here,
you're
forced
to
go.
A
C
C
So
what
we're
talking
about
trying
to
do
is
have
where
you
can
set
it
in
the
web
ide,
but
it
actually
sets
this
setting
here,
so
you
would
be
able
to
do
it
both,
and
I
think
that's
an
important
part
for.
I
think
I
think
that's
we're
using
this
one
kind
of
as
an
example,
but
I
do
think
that
solves
a
lot
of
settings
problems
is
that
you
know
settings
are
hard
to
find
and
there's
various
ways
that
I
think
we
could
solve
for
that.
But
one
of
those
is
in
a
lot
of
situations.
C
I
think
it
makes
sense
to
bring
settings
closer
to
the
thing
that
they're
affecting,
and
I
think
this
one
is
a
pretty
obvious.
One
of
you
know
if
I'm
setting
the
web
id
essentially
to
dark
mode.
Let's
let
you
do
that
right
there
in
the
web
id.
So
we
have
an
issue
open
to
look
into
doing
that
here
in
the
near
future.
So
that
should
be
an
interesting
one,
one
that
I
think
that
would
maybe
set
a
precedence
that
maybe
some
other
teams
could
follow.
A
That's
super
interesting
because
when
we
looked
into
the
themes
or
like
the
the
the
most
relevant
topics
or
issues
that
we
find
in
settings,
it
really
goes
around
discoverability
of
settings
overall
usability
of
yeah,
just
the
the
pages
are
not
standardized
or
you
know
buttons
that
appear
here.
Another
page
appear
there
etc,
but
also
the
global
versus
item
or
menu
settings
or
feature
settings
because
of
certain
features,
and
it
seems
so
interesting
to
see
web
ide
there.
A
C
A
Yeah,
that's
I'm
actually
working
on
something
related
to
this
right
now,
with
group
releases
and
environments.
At
the
group
level,
we
want
to
have
the
ability
to
manage
releases
across
multiple,
multiple
repos
or
projects
within
a
same
group.
That's
definitely
it's
current
one
of
the
current
challenges
in.
A
So
this
there's
some
sort
of
miscommunication
there
and
one
of
the
yesterday
I
had
a
chat
with
juan
and
we
came
up
with
a
very
interesting
topic
on
identifying
patterns
for
settings
and
recommendations
from
a
design
point
of
view,
not
only
the
look
and
feel
of
the
components
or
the
behavior
of
components
specifically,
but
how
would
they?
How
can
we
provide
guidelines,
for
I
don't
know
in
pajamas
or
whatever
you
know
for
settings
patterns?
A
C
You
know
like
radio
buttons
and
check
boxes
and
single
selects
or
radios
and
multi
selection
check
boxes
and
that
kind
of
stuff
but
yeah?
No,
I
I
definitely
if
you
look
at
the
settings
page
right,
we're
intermixing,
radios
and
toggles,
and
I
think
my
least
favorite
thing
of
settings
is
in
the
visibility
part
where
we
have
a
toggle
and
then
a
drop
down,
and
it's
really
the
combination
of
those
two
things
that
is
driving
what
happens
in
that
setting.
B
C
Yeah
so
I'll
tell
you
what
got
me
exactly
it
was.
It
was
this
kind
of
of
text
right
here
was
share
code
share
code
pace
with
others
out
of
git
repository,
it's
interesting
phrasing
in
its
own
right,
but
I
didn't
get
the
sense
from
this
that
I
was
turning
off
snippets
the
feature.
I
got
the
sense
that
I
was
turning
off
the
ability
to
share
it
right.
C
In
between
the
title
and
then
the
toggle
itself
is
a
little,
it
makes
you
feel
like
you're.
Turning
off
that
functionality,
I
guess
in
a
sense
you
are
right,
but
it
I
and
snippets
is
a
good
example
of
like
it
makes
you
feel
like
you're.
Turning
off
the
sharing,
not
the
entire
feature
of
snippets,
but
also
just
in
general,
the
combination
of
a
toggle
and-
and
this
I
feel
like
you-
could
consolidate
those
into
two
right
like
yeah.
A
C
Consolidate
that
into
one-
and
it
could
probably
be
a
drop
down
that
is,
you
know
on
for
everyone
with
access
on,
for
whatever
the
other
one
is
here
only
project
mender
or
all
for
everybody
right.
I
don't
know
that
we
need
two
items
here.
I
think
maybe
the
toggles
are
nice
because
they,
you
know
they
they're
visually
easier
to
see
if
something's,
on
or
off
but
kind
of
feels,
like
maybe
we're
over
complicating
this
a
little
bit.
A
A
It
was
a
chat
box,
but
you
could
not.
You
just
couldn't
understand
what
would
a
checkbox
did
here,
so
we
don't
really
have
that
in
the
as
one
of
the
teams
that
we've
identified,
but
it's
definitely
something
to
worth.
That
is
worth
adding,
because
I
understand
that
we
do
have
technical
writers
to
to
review
the
merger
quest,
but
I
personally
have
also
problems
when
I
have
to
understand
the
technical
part
of
the
settings,
but
then
the
language
is
just
too
I
don't
know
it's
just
feature
centered.
You
know
like.
A
C
C
So
yeah,
I
think
generally
for
me,
I
think
settings
comes
down
to
two
and
maybe
a
third
thing,
the
third
thing's
a
bit
of
a
blue
sky
idea,
but
okay.
Well,
I
guess
three.
Definitely
three
things:
one
yeah!
I
can
clean
up
the
ui
right,
standardize
on
ui
elements
and
instead
of
having
each
section
having
its
own
personal
design,
we
should
just
have.
C
C
I
do
think
contextual
settings
are
going
to
be
very
important,
just
kind
of
see
that
trend
all
over
the
place.
I
think
android,
if
you
have
an
android
phone,
is
great
examples
of
that.
You
know
or
my
favorite
example
that
is
like
when
you
open
something
it
will
ask
you,
do
you
want
to
open
this
in
the
app
or
do
you
want
to
open
it
in
the
web,
and
then
it
remembers
that
setting
and
I
it
would
be
impossible
to
find
where
that
setting
is
in
the
like.
C
C
So,
in
my
opinion,
the
only
real
way
to
solve
that
is
with
searchable
settings
like
if
we,
if
you
know,
if
you
look
at
slack
or
even
vs
code
and
things
like
that,
I
think
a
lot
of
like
once
you
go
to
a
certain
level
of
settings
you
just
need
to.
They
have
to
be
searchable,
it's
just
the
only
way.
I
think
that
you
can
really
navigate
around
that
problem,
yeah
and
then
the
third
slash.
Fourth
thing.
C
I
guess
fourth
thing
since
I
did
say
three
that
I've
been
thinking
about
like
I
said
that
is
a
very
blue
sky
idea,
but
being
in
the
editor
world,
I
am
now
there's
this
very
common
like
much
like
we
have
infrastructure
as
code
right,
so
your
yaml
file
isn't
a
bunch
of
settings.
It's
essentially
just
a
code
file
right.
C
So
I
guess
what
I
would
be
interested
to
see
is
what
that
really
solves
is
let
you
let
your
settings
be
your
settings
and
they
can
move
from
project
to
project
and
they're
version
controlled
and
all
that
wonderful
stuff,
but
I
guess
to
see
if
that
would
be
valuable
or
not
would
be.
You
know,
are
people
having
to
reset
the
same
settings
from
project
to
project
and
is
that
a
pain
point.
A
C
I
haven't
looked
into
like
if
that's
an
actual
problem
or
not
it's
just
something.
I
see
a
lot
in
editors,
yeah
like
vs
code
itself,
is,
is
that
right,
it's
a
it's
a
json
file.
It
gives
you
an
interface
to
edit
the
settings
and
I
don't
think
we
should
ever
go
away
from
having
an
interface
to
set
the
settings.
But
what
the
interface
essentially
is
doing
is
writing
a
json
file.
A
A
So
there's
this
like
combination
of,
for
example,
I
don't
know
deploy
phrases
where
you
say
your
project
settings.
I
want
to
enable
the
property
that
my
phrases,
but
on
the
ci
file,
you
specify
the
dates
or
you
specify,
for
which
I
don't
know,
pipelines
or
jobs
are
not
going
to
be
running
and
one
of
the
things
that.
A
It's
a
bit
tricky
to
solve
the
trick
itself,
but
it's
a
well
it's
a
challenge
is
that
when
we
want
to
do
this
configuration
the
group
level,
there
is
no
code
base
in
the
group.
There's
no
code
base
outside
the
project
context,
so
I'm
just
curious
to
see
like
what
this
settings
living
as
code
would
look
like
for
web
id,
where
it's
like.
Where
does
the
settings
for
code
web
ide
would
live
or
where
would
the
user
go?
A
C
C
Let's
share
my
desktop,
I
guess
so,
if
you
go
into
get
this
out
close
that
if
you
go
into
settings
and
bs
code
is,
I
think,
is
a
good
example
for
a
lot
of
the
things
that
I
was
talking
about,
because
it
is
just
like
ridiculous
in
the
number
of
settings
that
it
has
and
it
has
plug-ins.
So
it
has
to
support
like
you
know
many
different
ones
and
things
like
that,
but
it
does
have
search
which
is
nice,
you
know.
C
So
if
you
want
to
change
something
like
theme
just
search
for
theme-
and
you
know
you
get
all
that
it
tells
you
where
it
is
in
kind
of
the
file
train
and
all
that
stuff,
but
getting
back
to
the
original
point
of
being
able
to
set
this.
So
there
is
a
user
interface
to
set
this
right,
visual
studio,
dart
and
all
that
good
stuff.
C
C
It's
like
a
yeah
and
it's
pretty
common.
You
know
like
things
like
another
example.
This
would
be
like
an
editor
config.
You
know
so
there's
like
the
age-old
debate
of
tabs
versus
spaces,
and
should
there
be
two
spaces
or
four
spaces,
and
you
know
instead
of
engineers,
arguing
about
that
a
lot
of
times
nowadays,
you'll
just
include
like
an
editor
config
file
in
your
as
part
of
your
code
and
then
that
editor
config
makes
you
have
whatever
two
spaces.
C
A
C
B
C
I
you
know
we're
ui
folks,
so,
like
it
kind
of
scares
me
a
little
bit
to
think
about
settings
as
code,
but
I
do.
I
know
this
with
working
with
the
yaml
stuff
right,
the
in
the
ci
yemel-
I,
I
would
dare
say
it's
probably
two
to
one
of
of
of
the
personas.
That
would
much
prefer
the
yaml
file
and
to
manage
that
as
code
than
for
us
to
have
settings
for
that.
C
But
we've
existed
for
years
without
without
there
wasn't
an
uprising
is
what
I'm
saying
of
that
living
as
code
and
a
lot
of
folks
when
I
talked
to
them
were
happy
that
it
that
it's
code
and
really
wouldn't
want
it
in
the
ui.
So
I
bet
you
there
would
be
giving
the
heavy
developer
persona
that
we
have
a
lot
of
support
for
that.
That's.
A
True,
especially
like
what
you
say
in
the
beginning
that,
even
if
we
come
up
with
the
recommendations
of
yeah,
we
will
go
over
like
60
40
that
are
so
much
complexity
that
it
just
takes
more
time
to
deliver
the
ui.
And
it's
just
I
don't
know,
we've
seen
what
happened
to
you
to
the
github
most
recent
redesign.
If
you
scroll
up
there,
then
people
are
going
to
have
an
opinion.
C
A
So
I
sent
here
in
the
in
the
chat
a
couple
of
links.
Well,
I
have
more,
but
I
just
sent
the
ones
that
were
easy
to
find
about
search
is
setting
search
in
general.
So
there's
two
big
items
later
today.
I
have
a
chat
with
with
katherine
and
I'm
gonna
talk
about
the
research
that
has
been
done
for
settings,
but
there's
two
things:
it's
a
search
like
a
global
gitlab
search
that
you
will
just
find
anything.
C
I
think
it'd
be
interesting
to
hook
it
into
the
global
search,
but
I
I
really
was
just
talking
about
like
on
the
settings
page
going
back
again
to
this.
To
me,
I
think,
is,
is
a
great
example
of
this
of
I
have
no
idea
how
to
find
anything
in
vs
code.
I
don't
I
don't
even
fool
with
this,
because
it's
just
it's
impossible.
There
is
so
many
right
and
each
one
of
these
has
just
forget
it
right.
You're,
never
going
to
do
anything
to
me.
This
entire
thing
boils
down
to
the
search.
C
B
A
C
C
A
What's
all
these
issues
in
dedicated
buckets
so
that
we
can
see
what
are
the
different
directions
that
we're
currently
taking
for
settings?
So
if
you
can
also
after
this
call,
if
you
remember
where
you
can
find
any
of
these
links,
just
feel
free
to
draw
in
this
document
or
just
send
me
slack
or
add
to
the
to
the
settings
topic.
C
C
C
C
So
if
that's
the
case,
reorganizing
stuff,
you're
gonna
have
to
duplicate
the
settings,
so
it
can
live
in
both
places
which
is
confusing
in
its
own
right,
because
then
it
does
it
there's
one
override
the
other.
You
know
I.
I
don't
know
that
you
really
want
the
same
setting
in
multiple
places,
but
you
know
there's
a
lot
of
this
should
be
in
the
ci
cd
section
yeah,
but
it
should
also
be
in
general
right,
like
I
just
think
we're
going
to
run
into
that
a
lot.
A
A
Another
thing
that
came
up
in
the
conversations
on
popular
designers
is
this
need
to
have.
I
know
just
some
entry
points
to
settings
in
the
feature
pages.
It's
like
we're
just
saying
with
the
web
id.
You
can
do
some
configuration
there,
but
I
don't
know
what,
if
you
want
to
do
some
global
configurations
or
general
configurations
related
to
web
ide,
but
that
are
don't
leave
necessarily
on
the
web
id
space
right
and
right
now,
there's
no
way
or
there's.
A
A
D
C
My
mind
goes
to
visibility.
Project
features
this
this
section.
We
were
looking
at
before,
because
it's
got
all
these
everyone
with
access
things
in
it
and
then
a
lot
of
times
related
to
that
you're
like
wait.
Well,
who
is
who
are
the
members
of
this
project
and
I
will
look
through
settings.
I
will
expand
and
collapse
all
day
long
clicking
around
here,
because
it's
members
right
it's
it's
outside
of
this.
It's
it's
not
even
a
setting,
but
yet
it
feels
to
me
like
it
is
a
setting.
D
C
C
Yeah,
so
you
have
this
section
that
kind
of
deals
with
who
can
access
it
right,
project,
visibility,
public
and
then
everyone
with
access
or
only
project
members.
Well
only
project
members
is
members,
so
I
feel
like
this
section,
has
no
association
with
this
section,
but
in
my
mind
it
does
yes,
this
isn't
technically
a
setting.
C
Yeah,
so
maybe
I
mean,
maybe
I'm
not
necessarily
saying
that
members
should
be
a
set
part
of
settings,
but
maybe
similar
to
what
you're
saying
the
docs
linking
to
stuff
and
the
the
application
linking
to
settings
and
things
like
that.
But
I
also
think
the
settings
needs
to
link
to
themselves
as
well.
A
A
Is
against
pajamas
yeah?
This
is
legacy,
and
this
is
this
is
one
of
the
settings
page
that
I
think
it
just
it's
a
little
monster.
It
just
grows
in
itself
because
it's
legacy
and
then
we
just
keep
adding
more
things
to
this
video
yeah.
Just
like
the
variables.
If
you
go
to
cicd
variables,
it
was
redesigned
by
the
meteor,
I
think
a
couple
of
months
ago
and
he
removed
that.
A
Thank
god
all
this,
if
you
expand
variables,
no
before
you
just
couldn't
fit
any
more
information
on
this
view,
and
you
had
the
same
problem,
you
had
inputs
and
the
toggles
and
checkboxes
was
a
big
mess,
and
now
we
have
in
a
different
context.
But
if
you
still
go
on
this
page
in
other
sections,
you
still
see
some
of
the
legacy
legacy
settings
yeah.
This
one
is
an
example.
A
A
C
We
do
hopefully,
I
know
there
is
talk
of
pages,
moving
to
the
static
site,
editor
group
and
then
consolidating
those
as
well,
but
I
I
I
there
is
that
point
as
well,
but
there's
this
whole
pages
thing
that
essentially
is
a
feature
that
lives
as
part
of
settings.
When
really
this
is
not
a
settings
page
at
all.
This
check
box
is
a
setting
for
sure,
but
the
rest
of
this
is
not
settings.
A
A
It's
you
trying
to
figure
out
how
to
prioritize
this,
but
hopefully
when
we
got
to
the
point
where
we
can
choose
their
action
for,
for
example,
if
the
you
know,
what's
going
one
of
the
big
things
I
can
solve,
we
can
solve
this
search.
For
example,
then
we're
gonna
start
the
conversations
with
the
broader
design
group
and
identifying
dris.
Let's
see
that
was
the
initial
ideas
to
come
up
with
these
standards
or
you
know,
validate
good
users,
talk
to
people
and
push
for
implementation.
C
C
Maybe
a
more
consistent
holistic
idea
of
like
things
that
we
let
people
set
right.
I
think
there
is
a
large
variance
between
in
some
groups.
You
are
allowed
to
very
much
customize
what
shows
up
and
in
other
groups
very
much
not
able
to
customize
things
that
show
up,
and
maybe
that's
okay.
Maybe
that
is
the
nuances
of
those
groups,
but
you
know
just
in
general,
like
what
what
are
we
even
setting?
I
guess
is
the
question.