►
From YouTube: UX Showcase: Dark Mode for the WebIDE
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Imagining
that
imagine
a
light
version
of
vs
code
right
in
your
browser.
It
allows
you
to
edit
files
to
commit
these
changes
that
he
made
in
the
files
to
create
new,
merge
requests
and
to
also
already
preview
changes
form,
for
example,
simple
JavaScript
files.
You
can
see
the
status
of
the
pipeline's
that
are
currently
running
and
the
project
right
in
the
UI.
A
You
can
also
use
an
integrated
terminal
too,
for
example,
one
tests
and,
if
you're
wondering,
why
are
we
carrying
about
the
web
ID
so
much
it's
one
of
the
differentiators
that
sets
us
apart
from
our
competitors,
it's
something
in
our
core
of
create
that
we
offer
and
that
we
make
available
to
users
that
our
competitors
currently
don't,
and
we
can
see
that
it's
working
really
well.
We
can
see
that
the
numbers
are
rising,
the
numbers
are
growing
and
the
data
here
is
a
bit
misleading.
It's
not
jumping
as
much
as
it
is
here.
A
That's
due
to
how
many
new
sources
of
data
are
currently
coming
in,
but
we
see
really
horizon
the
usage
of
the
web
ID
and
that's
great.
So
we
really
want
to
make
sure
that
users
experience
perience
using
it
and,
if
you're
wondering
about,
why
do
we
then
care
about
dark
mode
for
the
web?
Id?
If
you
look
at
the
most
uploaded
issues
for
all
of
gitlab,
you'll
see
the
dark
mode
for
the
entire
gate.
A
Love
UI
is
number
two
and
that's
gonna
be
a
big
issue
that
we
are
going
to
be
working
on,
but
we
wanted
to
see.
Can
we
bring
this
down
to
a
small
iteration?
Can
we
make
this
happen
just
in
the
web
IDE,
because
that
mode
is
not
only
a
popular
topic
to
talk
about
it's
also
important
for
accessibility
and
to
make
sure
that
users
who
have
trouble,
for
example,
working
and
lower
lights,
have
less
strain
on
their
eyes.
A
A
The
ark
mode
is
something
that
users
really
love
to
see
coming
to
products,
and
we
want
to
push
users
to
try
out
the
web
IDE
to
keep
using
it
or
to
start
using
it
when
I
started
looking
at
how
to
design
a
dark
mode.
This
has
actually
been
my
first
time
working
in
this
space
and
we
looked
at
what
color
preferences
do
we
already
have
in
all
of
gitlab?
What
do
we
have
to
take
into
account
because
we
are
not
building
something
from
the
ground
up?
We
have
to
take
into
account.
A
A
So
we
wanted
to
make
sure
everything
looks
and
works
in
the
same
way
after
that
we
thought
about.
How
can
we
split
this
into
small
NB
C's,
because,
even
though
getting
that
one
to
the
web
IDE
is
a
limited
space,
but
it's
still
big,
and
so
we
had
a
look
at
first
making
the
dark
syntax
highlighting
applicable
in
the
web
IDE,
and
this
is
what
we
already
released
in
12.8.
We
got
a
lot
of
great
feedback.
A
We
got
a
lot
of
really
great
response,
even
though
it's
a
bit
jarring,
it's
looking
at
a
dark
blob
inside
a
white
UI.
It's
not
that
a
cyclic
pleasing,
but
even
doing
this
already
gave
our
users
first
preview
at
what
we
wanted
to
do
and
at
12
to
10.
We
are
now
working
on
the
base
UI
and
the
left
sidebar
before
in
13
dot
o.
A
When
we're
going
to
release
it
will
also
have
the
right,
sidebar
and
dropdowns,
hopefully
in
dark
mode,
whereas
for
smaller
things,
we
are
even
going
to
pull
these
out
of
the
scope
like
modal's,
because
we
can
still
take
care
of
these
later
on.
They
shouldn't
be
that
jarring
to
the
user.
Experience
that
we
can't
already
get
it
out
to
the
users
without
having
this.
A
So
when
looking
at
how
to
design
the
UI
for
this
I
did
a
lot
of
research
and
I
also
got
a
lot
of
great
help
from
Jeremy
elder
and
our
team,
which
has
been
tremendous
and
what
we
really
saw
is
creating
a
dark
mode,
is
tougher
than
you
would
expect
in
the
beginning.
It's
definitely
not
just
inverting
the
colors
and
be
done
with
it.
There's
a
lot
more
to
it.
It's
way
tougher
to
create
depth
and
the
UI
it's
way
tougher,
to
create
any
kind
of
have
a
focus,
active
state,
four
buttons.
A
A
As
you
can
see
here
and
figman
the
prototype,
that's
publicly
available,
you
can
have
a
look
at
what
does
the
file
look
like
when
I've
made
a
change
to
the
file?
How
does
it
change
the
icons
when
I
want
to
commit
this?
How
does
this
work
and
what
we
also
wanted
to
show?
How
would
popovers
work?
How
would
having
over
a
button
work,
and
how
would
this
all
feel-
and
this
is
really
were
figma-
also
shines?
A
What
I
showed
and
the
color
starts,
there's
also
a
couple
of
different
different
variables
that
we
have
defined
and
these
variables
are
almost
one-to-one
applicable
to
how
it
works
in
the
code.
As
you
can
see
here,
these
color
Styles
side
by
background
I
can
highlight
background
text
is
exactly
what
Himanshu
you're
not
sharing
each
time.
Sorry
I'm
not
showing
my
screen.
Okay,
let
me
try
to
do
that
again.
A
A
That's
exactly
what
Himanshu
the
engineer
who
built
this
into
our
code
base
used
as
a
base,
and
he
defined
these
variables
to
be
used
in
different
places,
and
this
is
how
we
collaborated
from
figma
to
code,
not
only
by
this.
We
also
had
a
couple
of
collaboration
sessions,
but
this
really
helped
him
already
understand
how
my
UI
is
built
while
he's
starting
to
implement-
and
this
really
shows
the
strength
of
having
a
design
tool.
That's
already
thinking
a
bit
further
around
implementation.
A
All
of
this
set
I
wanted
to
thank
you
all
for
for
listening
and
I
wanted
to.
Thank
also
all
of
you,
because
there's
been
a
lot
of
great
feedback
on
the
Sigma
file
that
I
shared
a
couple
of
weeks
ago
in
the
UX
Channel
and
where
a
lot
of
great
comments
came
in
I
wanted
to
especially
call
out
Jeremy
and
Himanshu,
who
have
been
amazing
and
who
were
great
people
to
collaborate
with
while
working
on
this.