►
From YouTube: Node.js Website Redesign
Description
A
We
are
live,
cool,
awesome,
hello,
internet,
welcome
to
another
edition
of
website
redesign
quote.
We
we've
added
a
couple
more
things
to
the
agenda
for
folks
who
may
or
may
not
be
following
along
lives,
but
if
you're,
following
along
on
youtube
and
you're,
not
in
the
meeting,
come
going,
we're
just
hanging
out
cool,
so
I
think
what
would
also
be
good
is
if
we
we
could
just
take
an
audit
of
where
we
are
as
well
with
implementing
the
start.
Adding
this
thing
with
implementing
the
current
mocks,
so
I
saw
that
we
got
Oscar.
A
B
A
C
D
C
A
A
A
Go
home
there
we
go
cool,
so
Oscar
he's
been
hacking
away
on
the
homepage
and
we're
looking
pretty
good
here
right
and
we
have
another
PR
set
up
kind
of
refactoring,
some
of
the
code
ooh,
my
laptop
charting
refactoring,
some
of
the
code
for
it
and
getting
it
ready
for
some
ice
and
and
but
this
thing
visually
at
least
matches
the
mocks
right,
yep
there
yeah.
We
just
need
this
like
how
do
install
section
builds
out,
which
is
actually
a
really
wealthy
little
pack,
and
we
can
make
an
issue
for
me.
C
A
A
B
A
The
mailing
list
button
and
the
like
events,
notification
up
the
top,
and
we
don't
know
how
we're
gonna
do
that.
Like
events,
notification,
it
would
be
awesome
if
we
could
have
it
wired
up
to
a
something
that
foundation
folks
can
can
can
edit
easily.
Instead
of
you
know
having
to
make
poll
requests
and
everything
become.
E
A
We
need
to
have
a
discussion
around
how
content
for
this
banner
is
going
to
show
up,
but
we
should
I
would
probably
should
maybe
bring
that
up
and
larger
Comic
Con
meeting
when
there's
foundation,
folks
on
the
line
and
see
what
their
preferred
word
workflow
is
because
I
think
that'll
be
what
determines
that
so
yeah.
If
you
could
do
me
a
favor
and
open
up
three
tickets
for
those
yeah.
C
A
C
A
The
markdown
files
are
manually
maintained
by
the
folks
at
maintain
court.
It's
there
are
better
ways
to
do
this
nowadays,
but
notice
so
hold
that
it's
that's
just
how
it
was
done
from
the
beginning.
It's
kind
of
how
it
about
to
I
have
an
open
issue
for
Kentucky
on
the
agenda
in
our
perfect
world.
How
would
we
want
to
API
documentation
to
be
maintained?
A
We're
also
not
the
right
we're,
not
all
the
stakeholders
that
need
to
be
present
for
that
type
of
conversation,
because
we're
not
the
ones
who
are
actively
maintaining
core,
and
you
know
they
matter,
for
this
I
pay
more.
They
matter
more
than
the
people.
You
know
us
or
generating
the
documentation
for
that
that
works
well,
but
I
would
personally
love
to
see
I
think
what
you're
you're
referencing,
which
is
like
inline
code
comments
that
are
yanked
out
to
generate
documentation,
yeah.
C
That's
one
aspect
for
sure,
but
also
the
rendering
pipeline
I
I,
do
appreciate
that
markdown
historically
had
to
be
server-side
rendering.
But
if
we're
taking
Mart
markdown
and
dominate
immediately
I've
been
exploring
that
for
a
while,
now
and
and
I
mean
server-side
rendering
may
not
always
be
ideal.
There
are
trade-offs
and
the
under.
A
All
documentation
that
we
need
to
write
just
like
the
folks
coming
in
can
can
easily
grok
the
power
our
conserving
all
this
we're
actually
not
consuming
the
generated
HTML
for
this.
This
page,
specifically
when
the
markdown
gets
parsed
it.
It
goes
through
two
different
steps.
The
first
step
it
gets
turned
into
a
JSON
structure
and
then
the
second
step.
A
It
gets
that
out
of
that
static
HTML,
which
is
the
current
like
old
node
donde
at
that
org
site,
the
nodejs,
a
dev
site
right
now
is
actually
consuming
the
JSON
or
sex,
and
it's
pulling
it
down
as
JSON,
and
it's
the
way
everything
gets
spat
out.
It's
kind
of
it's
like
render,
render
models.
Ask
if
you're
familiar
with
that
pattern.
There's
like
a
core
core
data
structure
for
each
thing
inside
here.
Some
of
you,
a
visual,
will
be
better.
A
So
there's
it's
just
a
giant
like
nested
array
of
objects
that
are
really
really
similar,
but
then
they
all
kind
of
adhere
to
the
same
data
schema,
and
so
you
can
write
basically
just
a
recursive
renderer,
which
problems
based
on
the
element
type
to
render
what
is
needed,
which
is
basically
how
this
thing
works
and
will
be
enough.
A
little
elegant
once
you
can
wrap
your
head
around
it.
A
The
next
step
as
to
where
you
know
to
a
hopefully
brighter
future,
so
I
very
much
went
the
just
make
it
work
route
for
the
the
current
API
page,
but
we
we
could
use
some
planning
around
how
to
you
know
some
proposal
that
we
could
bring
to
core
to
be
like
hey.
We
could
document
this
way.
Here's
how
we
could
incrementally
get
there
like,
there's
Wi-Fi,
always.
C
E
B
We've
had
an
issue:
we've
had
an
issue
for
so
long
in
our
agenda.
Two
of
just
one
would
be
the
ideal
way
to
consume
this
kind
of
stuff
and
I
wish
we
punt
it
every
single,
every
single
meeting
I've
ever
been
in,
which
has
been
for
like
six
months
or
something,
but
just
to
refresh
my
memory
Adam.
You
just
said
that
we're
currently
pulling
the
documentation
content
from
an
adjacent
in
point
correct.
That's
that's
what
we're
doing
right!
Mm-Hmm.
E
B
B
A
It's
actually
hosted
right
alongside
the
main
API
documentation,
so
every
time
that
the
node
every
time
the
know
gets
built
it
now
doing
builds.
You
know
the
code
artifacts
that
it
builds
the
documentation
artifacts,
which
is
part,
static,
site
generator,
arts
like
markdown
parser
part,
and
so
it
spits
out
basically
just
a
giant
folder
structure
of
HTML
files
and
contact
JSON
files.
So
inside
this
this
giant
directory
structure,
I
believe
it
just
lives
in
Doc's.
Intimacy
is:
if
we
go
here.
Yes,
we
can.
A
A
So
what
I'm
doing
on
the
API
Doc's
page
is
I'm
basically
hitting
that
up
as
a
fake
API
server
taste
funnel
I'm
just
hitting
this
up
in
the
fake
API
server
to
go,
get
the
content
for
each
page,
and
there
is
actually
a
page
for
for
all
of
the
content
and
so
I'm
being
a
very
bad
internet
citizen
right
now,
and
rather
than
being
intelligent
with
navigation.
A
little
bit
I'm
literally
just
hitting
up
this
all
dot
JSON
file,
which
is
a
pretty
hefty
upfront
cost.
B
A
C
Benefit
of
JSON
is
that
you
you
could
concatenate
and
and
prefetch.
There
are
so
many
optimizations
you
do
for
JSON
and
the
nice
thing
also
it
doesn't
hit
any
rendering
if
you
prefetch
or
if
you
cache,
like
I,
like
the
JSON
workflow
I,
also
for
longer
term,
want
to
consider
a
markdown
with
annotations
that
that
provides
the
rendering
context
needed
that
you
know
so.
The
markdown
source
files
are
a
single
source
of
truth.
C
A
Yeah,
there's
there
are
some
annotations.
You
need
the
current
markdown
Doc's,
which
actually
generates
the
typing
for
this
like
render
modelesque
type
of
data
structure,
but
they're
they're
somewhat
inconsistent,
and
there
is
this
very
fun
catch-all
like
other
category,
which
probably
needs
to
be
split
up
into
three
different
concepts
for
the
way
we're
wanting
to
render
this
page
module
and
other
kind
of
the
same
module
other
and
like
generic
text,
notes
on
something
are
kind
of
the
same,
all
grouped
up
into
a
single
model.
A
So
there's
some
of
those
some
improvements
to
even
just
the
current,
like
annotation
structure
for
other
other
things
missing
from
the
API
Docs
page,
there's
deep
routing
that
we
need
technically
this,
like
jump
to
a
jump
to
a
point.
It
works
with
anchor
tags.
However
I
believe
if
you
refresh
the
page
right
now,
it
does
not
work.
So
there
is
no
there's
no
deep
linking
currently
on
API
Docs,
which
is
a
must
have
sorry.
C
You
know,
and-
and
you
know
so-
it's
something
worth
actually
optimizing
at
now-
is
that
you
have
this
div
and
that
div
is
the
interface
of
the
contained
document
in
it.
You
render
with
weather
like
just
pure
api's,
so
it's
something
I
would
propose.
You
know
you
of
course,
everybody
you
know
like
I'm,
just
proposing
this
idea
and
would
really
welcome
everybody's
views
on
that
yeah.
A
Let's
get
a
look
at
an
issue
opened
up
with
the
proposal
I'm
having
trouble
kind
of
wrapping
my
head
around
exactly
what
the
implementation
you're
suggesting
is,
but
I'd
love
to
see
a
proposal
for
it.
Yes,
open
all
all
suggestions
there,
they
have.
You
want
to
get
that
written
up
about
the
real
true
Oh
other
yeah,
there's
gonna,
be
obscene
million
performance
improvement.
A
How
are
consuming
documentation
here,
but
my
laundry
list
of
like
that's
like
P,
p1
or
p2
priority
issues
like
p
0
for
me
right
now,
is
like
we
need
syntax,
highlighting
there's
some
visual
weirdness
with
you
know
how
we're
displaying
methods
and
stuff
as
some
styling
stuff.
Is
you
still
when
you
first
load
the
page,
it
does
default
to
the
correct
version,
but
it
does
not
load
the
first
page
automatically.
Like
all
these
pretty
simple
improvements.
There
is
a
code
version
switcher
which
actually
works
pretty
darn.
Well,
however,
there
is
another.
A
What
I
would
love
to
do
is
bake
in
the
latest.
Lts
so
adds
Build
time
pull
in
the
JSON
files
from
remote
and
actually
bake
it
into
the
bundle,
because,
right
now
we
cannot
ever
server-side
render
the
API
pages
because
we're
pulling
it
down.
They
sync
at
runtime
called
the
all
the
JSON
content.
If
we
bake
the
JSON
into
the
gas
we
build,
we
can
service,
ID
render
API
pages,
and
so
it'll
come
down
as
just
Raj
tml
for
sort
of
the
web
crawlers
and
for
a
faster
first
page
load
time
or
Ralphie
s.
A
C
The
staging
branch
right
now
right
this
is
this-
is
all
in
staging
right
now.
Yet,
okay,
could
you
show
me
where
the
assets
are
later
on?
That
doesn't
have
to
be
right
now,
like
just
going
through
all
like
kind
of
the
source
files
like?
Where
does
this
all
start
to,
like
the
entry
point
there?
Where
would
I
replace
it
with
a
div
and
write
some
JavaScript
code
around
that
we
can
do
that
later
on,
but
yeah
that
would
help
a
lot
of
things.
Yeah.
A
C
A
Awesome
so,
like
we
talked
about
before
that
that
spacing
stuff
is
gonna
have
to
be
fairly
generic,
and
actually
you
could
probably
you
want
to
tackle
it
now.
The
learn
page
might
be
a
good
place
to
do
that.
So
the
because
all
this
is
just
like
spat
out
rear-ended
markdown.
We
don't
have
control
over
a
class
names
on
anything,
and
so
we
have
to.
We
have
to
basically
write
like
a
node
re-rendered
markdown
reset
container
for
typography
here,
so
it
will
consistently
spit
out
h1
h2
h3,
idiotic
paragraph
tags.
A
A
code
blocks
will
always
have
the
same
markup,
but
all
we
have
really
control
over
is
slapping
a
class
on
the
parent
container,
and
then
we
have
to
make
sure
that
everything
just
based
on
the
element
types
will
get
styled
correctly,
because
we
have
limited
control
over
over
class
names
so
that
that
type
of,
like
generic
reset,
if
you
can
make
it
work
correctly
on
the
learn
page
it'll,
carry
over
to
the
documentation
page
pretty
well
and
I
can
slap
that
class
on
anything.
That
is
just
basic
text.
Content
got.
C
A
A
list
like
this,
like
I,
have
no
control
over
this.
This
list
that
came
from
raw
markdown
yeah,
so
there's
a
little
more
control
on
the
API
Docs
page,
but
we
should
probably
like
these
these,
like
headers
and
stuff
I'm
manually,
styling
and
rendering,
but
the
actual
content
I'm.
Not
so
if
you
can
get
the
learn
page
like
the
typography
over
here.
Looking
looking
correct,
it
shouldn't
carry
over
well
cool
to
be
a
clear
job,
page
yeah.
B
Yep,
it's
not
much
going
on.
You'll
see
it's
detecting
that
you're.
Currently,
it's
detecting
your
OS
that
you're
currently
on
a
Mac
machine
up
at
the
top
I'm,
rendering
I
think
we'd
said
initially
to
render
the
thought
the
first
like
25
versions
or
something
but
I
realized,
eventually
that
I
needed
to
expand
it
in
order
to
get
like
in
order
to
even
get
down
LTS
to
version
10
I
need
to
expand.
B
I
expanded
it
to
like
50
or
something
I'm,
not
sure
see
it's
just
a
just
a
table,
that's
not
styled,
but
those
links,
those
links,
work,
the
changelog
did
download
links.
They
all
point
to
the
proper
places
on
github
I
added
that
clicker
up
at
the
top.
It's
just
you
know,
there's
a
react
took
if
you
toggle
the
if
you
toggle
the
the
check
mark,
whatever
it'll
switch
from
LTS
from
current
LTS,
it's
doing
that
programmatically.
So
it's
looking
for
you
know,
based
on
the
I.
B
We're
not
currently
displaying
wet,
well
cool,
serve
some
reason:
I
thought
I
was
muted,
we're
not
currently
displaying
because
you're
on
a
Mac
it
doesn't
it's
not
currently
telling
you
hey,
download
the
Mac
version
here,
etc.
I
created
a
utility
in
order
to
be
able
to
detect
that
we're
just
detecting
Mac,
well
we're
detecting
Mac,
Linux
and
Windows,
and
then
for
mobile,
it's
just
considered
unknown,
etc,
but
yeah.
So
we
updated
a.
There.
B
Was
a
pull
request
that
is
actually
on
the
agenda
or
whatnot
that
talks
about
the
download
grid
page,
so
I
updated
that
just
a
little
bit
to
say
what
you
know
that
hey
I've
added
this
utility
function
to
check
the
navigator
etc
to
get
the
platform's
OS
yeah,
there's
still
a
lot
that
needs
to
be
happening
on
this
page.
We
need
to
determine
some
design
stuff
in
terms
of
what
is
the
for
anybody.
B
That's
not
familiar
one
of
the
things
that
we
wanted
to
do
is
we
wanted
to
create
a
illustration
of
some
way
to
explain
the
release
cycle
to
people
visually.
We
looked
at
I
think
what
was
it
backbone
backbone
had
a
pretty
cool
graphic
to
explain
the
weight
of
their
key.
They
release
candidates
go
very
well
member,
that's
what
it
was
specifically
yep.
So
that's
something
that
we
need
design
work
on
or
we
need
to.
B
Maybe
it
would
be
best
to
reach
out
probably
we,
as
we
talked
previously
been
pretty
best,
probably
to
reach
out
to
the
wider
community
and
see
if
anybody
has
an
idea
how
to
do
that,
but
but
yeah
so
I'm,
not
exactly
sure.
I've
been
I've
been
away.
The
past
couple
weeks
haven't
been
participating
too
much
here,
so
I'm
not
exactly
sure
what
I'm
gonna
work
on
next
on
this
page,
I'm
super
open
to
suggestions
or
anything
but
be
as
some
of
the
functional
parts
are
working
on
the
page
and
I
haven't
I,
haven't.
A
A
So
next
steps
for
the
for
the
page,
it
would
be
awesome
to
get
styles
in
there
and
have
it
landed
in
current,
because
we
will
let
some
point
soonish
be
at
a
place
where
we
can
merge
this
back
with
master
I.
Think
like
will
be
missing.
Some
major
features,
there'll
be
a
lot
of
dead
experience,
stuff
that
are
like
user
experience
stuff.
We
got
it,
we
got
to
rehash,
but
anything,
that's
like
obviously
broken
or
not
not
polished.
We
can
like
we.
A
If
we
can
fix,
we
can
actually
lens
the
master
and
get
it
up
on
the
main
sites.
You
can
start
playing
with
it
yeah.
So
if
we
get
like
styling
for
the
top
cards,
we
can
skip
the
upcoming
releases
section
for
now
and
and
styling
for
this
table
like
it
would
be
at
a
place
where
it's
helpful
enough
to
go,
go
live
on
the
site
and
not
act
yeah,
and
guess
we
can
continuous
feedback
on
it.
A
A
E
A
Were
you
gonna
point
out
Adam
what
I
was
gonna
point
out
and
I
can't
pop
open
the
vision
board
quickly
or
not
envision
them?
Whatever
my
wireframe
was
in
every
single,
every
single
individual
version
will
need
to
have
all
of
the
download
options
available
and
there's
there's
a
whole
bunch
of
download
targets.
So
it's
a
little
it's
a
little
more
granular
than
just
like
here's,
the
additional
download
for
LPS
or
for
current.
It's
like
here's,
the
additional
downloads
per
version
10.58.
A
D
A
C
C
And
then
let
me
let
me
think
about
that
then,
and
then
we
I'll
I'll
work
on
that
on
that
table
below,
but
everything
else
like
everything
on
top
of
that
other
than
the
also
the
illustration
I
think
we
could
still
we
could
still
do.
It
goes
I
mean
it's
fair
game
right
like
everything
else,
except
like
the
table,
the
the
top
part
with
the
toggle,
the
paragraph
on
the
cards
and
it's.
A
Actually
possible,
what
might
be
interesting
is
because
it's
because
it's
like
an
individual
version
dependent,
so
this,
like
additional
downloads,
listed
like
this
additional
versions
list
like
if
we,
if
we
expand
this
to
basically
just
be
like
that
folder,
like
infinite
scrolling
like
table
for
every
every
release,
version
kind
of
like
what
you
have
here-
John
but
like
if
you
click
this
download
button,
that
individual
table
row
expands
and
just
shows.
A
Quite
literally
this
view
or
your
your
download
site
and
like
only
one,
would
remain
this
expanded
at
a
given
points
there
yeah
there
we
go.
So
if
you
click
the
download
button,
it
would
just
expand
any
one
that
you
wanted
basis
make
this
this
view.
With
child
view
of
the
table
row
item
it
would
function,
it
would
still
work.
B
I
think
probably
the
happy
path
on
something
like
this
would
be:
I
need
to
I
need
to
download
version.
12
point
9
point
one
and
I
so
I
navigate
to
the
page.
I
find
twelve
point,
one
twelve
point,
nine
point:
one
I
click
on
it
and
then
because
it's
detected
my
operating
system
it.
It
shows
me
prominently.
This
is
the
OP.
You
know
like
Mac
version,
if
I'm
on
a
Mac
OS
of
the
proper
architecture
etc,
and
then
perhaps
there's
a
drop
down
or
something
a
big.
B
Basically,
we
can
filter
that
list
to
show
prominently
what
architecture
the
users
on,
if
we
can
detect
it
and
if
we
can't
and
then
there
could
be
an
additional
downloads
thing,
which
is,
if
you're
trying
to
download
a
version
for
a
system
you're
not
currently
on
here's,
the
rest
of
them
but
I
feel
like
most
users
likely
would
probably
be
downloading
the
appropriate,
a
Mac
version
or
whatever
for
whatever
they're
on
currently
yeah.
But
we
yeah.
E
A
B
A
Yes,
yeah
for
the
folks
not
going
that
path
like
there
should
be
like
an
option
to
click
through
to
the
exact
version
you
need,
so
we
can
play
with
that,
but
yeah
John
is
for
next
steps
and
we'll
talk
about
next
packet
on
soon
after
we
chat
about
dark
codex,
well
yeah.
If
we
can
just
get
these,
you
kind
of
have
two
of
the
four
modules
here
walked
out.
If
we
can
get
styled,
we'd
be
well
on
our
path.
The
marginal
master
to
nish
should.
C
One
when
suggestion
for
the
downloads
page
a
nice
shortcut
would
be
if
a
person
starts
to
type
numbers.
We
would
literally
just
filter
out
things
that
are
not
relative
to
that
number.
The
elements
from
the
page
that
are
not
relative
to
that
number
and
you
know
kind
of
like
a
search
box,
but
you
omit
the
search
box
entity
itself
and
maybe
just
Alan
at
aha
things
or
you
know
like
a
like
a
sticky
at
the
top.
You
show
them
what
what
numbers
are
tight.
C
So
it's
like
an
input
box
behavior
without
the
input
box
itself
like
Texaco
and
just
filter
out
things
that
are
not
matching
that
search
this
way.
People
can
zero
down
to
a
particular
version,
particular
mode
like
LTS
versus
current
by
just
typing,
the
first
few
letters
or
the
first
character
to
love
what
they
need.
A
F
C
A
C
Yeah
input
field
on
the
design,
just
in
case
beautiful.
A
B
C
A
Yeah
he
can,
if
you're,
sharing
something
other
than
just
like
the
page
and
cloud
I
got
it
up
right
now,
but
already
to
if
you'd
like
so.
C
So
we're
talking
about
dark
mode
as
a
CSS
enhancement,
not
as
a
like.
If
toggling
dark
mode
is
going
to
be
beyond
styling,
then
I
believe
you
know
that
that's
fundamentally
a
different
principle
of
dark
mode.
All
together
for
from
from
my
personal
experience,
dark
mode
in
CSS
properties
are
really
paired
up
nicely.
C
So
it's
important
to
know
that
when
you
do
dart
mode,
sometimes
it's
not
just
changing.
You
know
the
dominant
background,
the
bright
background
and
and
the
you
know,
contrasting
foreground.
Sometimes
you
know
you
do
some
subtle
things
to
take
away
the
potential
for
for
actually
creating
elements
that
are
too
painful
for
some
people
me
personally,
I
found
sometimes
checkboxes
get.
C
A
A
A
Like
open
up
Jules
and
the
things
exploding
because
I'm
sharing
screen
so
yeah
on
the
body,
we
have
a
whole
bunch
of
stuff
to
find
for
a
themed.
Color
Oscar
did
an
amazing
job
breaking
out
styles
by
not
only
into
it's
very
granular,
like
this
very
granular
color
palette,
but
then
assigning
them
actual
meaningful
names
that
we
can
use
throughout
the
site.
So
pop
this
open
I'm
on
laptop
you
got
it.
I
will
be
able
to
see
all
the
definitions.
A
Y'all
can
also
probably
do
this
locally
on
your
machines
up
there
you
go,
but
by
defining
this
kind
of
base
type
place
and
these
names
colors
or
their
other
uses,
we
can
easily
swap
them
out
in
dark
mode.
So
in
dark
mode,
we
literally
just
pop
out
a
bunch
of
colors
that
are
used
throughout
the
site,
so
there
are,
and
we
can
actually
see
that
dark
mode
definition
up
at
the
top
eye.
A
Where
we
actually
over
had
all
those
colors-
and
so
that's
the
only
thing
driving
dark
mode
is,
is
this:
we
do
have
a
couple
utility
classes.
That
also
will
do
things
in
dark
mode,
basically
just
showing
or
hiding
content
in
dark
mode,
and
you
see
that
applied
to
the
toggle
here
as
well,
so
both
icons
are
actually
in
the
Dom
and
any
given
point
and
with
CSS
we
hide
either
than
Sun
or
the
moon
depending
on
the
global
class
on
the
body.
A
Fun
fact,
because
these
are
not
necessarily
class
is
not
actually
like
type
of
the
body
tag.
You
could
slap
it
on
to
an
element
deeper
in
the
Dom
and
just
have
a
subset
become
dark
code.
It
would
still
work
just
fine,
but
what's
think
billion
that
might
as
well
just
do
it
but
yeah.
That's
where
we
are
driving
dark
mode
entirely
with
DSS.
There
is
no
JavaScript
early
after
magic
involved
in
following
class
yeah.
C
And
and
and
first
off
I'm
entirely
floored,
because
it's
the
first
time
I've
seen
someone
actually
take
this,
this
path
of
pure
CSS
with
react
and
not
be
like.
Okay,
there
are
too
many
moving
parts
code
that
don't
harmonize
with
the
CSS
property,
so
so
I'm
pretty
sure
it
was
foresight
and
and
good
planning
Oscar.
It's
like
we've
been
working
on
some
type
of
design
systems,
team
for
ya.
E
C
Ten
years
it's
it's
impressive
and,
and-
and
my
question
is,
do
you
have
some
elements
that
you
don't
like
to
see
in
dark
mode?
Didn't
you
know
that
you
accidentally
stumble
upon
some
place
where
it's
not
tied
to
the
CSS
property
correctly
or
it
redefines
the
value
of
the
of
the
CSS
property
through
skating
or
something
like
that?
Have
you
had
any
kind
of
glitches
that
are
because
we
did
this
and
react.
Css
properties
did
not
give
us
the
result,
not.
A
After
where
you
can
speak
to
the
home
page
to
this
very
desire,
did
the
only
the
only
mistakes
said
I've
seen
in
that
respect,
our
human
error
like
if,
if
I,
don't
use
one
of
the
names
colors,
but
instead
I
use
like
the
lower
level
like
black
one
black
to
black
three
instead
of
colorful
canvas,
then
it
it
doesn't
swap
in
dark
mode.
But
that's
you
know
that's
why
these
these
foundational
colors
exist
for
stuff
that
you
don't
want
to
change.
A
C
A
It's
just
force
on
force
off.
We
should
totally
add
a
like
respect:
vos
option
on
yeah
yeah
and
in
fact,
there's
there's
a
fourth
thing
to
consider
here
right
now,
if
you
put
the
site
in
dark
mode
and
then
refresh
the
page,
it
will
be
it'll
be
render
back
in
the
light
mode.
So
it
doesn't
remember
the
user
preference
than
that.
C
A
C
B
C
B
As
I
so
far
as
I
know,
it's
not
properly
implemented
in
Chrome
on
iOS,
mobile
or
whatever
I.
There
was
an
article
in
hacker
news
just
the
other
day,
and
it
only
triggered
if
you're
in
Safari,
but
that
stuff's
exciting
real
quick
before
we
passed
before
we
possibly
lose
Oscar.
One
obviously
does
Oscar
have
anything
to
add,
but
also
if
he
has
the
time
I'd
love
to
chat
about
next
hackathon,
which
week
we
can
coordinate
offline.
That's
fine
I
just
wanted
to
check
in
and
see.
If
any
see.
C
Yeah,
just
going
back
to
so
I've
questioned
on
certain
things
that
might
not
look
as
good
or
challenges.
I
noticed
that
some
of
the
illustration
on
the
walk
she
owned
the
whole
entire
page.
We're
gonna,
have
illustrations.
They
might
look
good
on
on
live
moment,
but
on
dark
mode.
They
look
kind
of
like
that,
but
they're
more
decoration
right.
So
aren't
we
talking
about
the
SVG
elements
or
are
we
talking
about
the
animated
I?
Don't
know
how
you
guys
the
kind
of
animated
stuff
in
the
back.
C
Svg's
and
then
I'm
design,
animating
them
obviously
SS,
but
those
are
the
ones
I'm
talking
about
like
if
you,
if
you
scroll
down
like
the
the
petals
or
the
leave,
some
that
are
put
there
just
just
to
you,
know
pop
it
out.
I,
don't
know
that
the
this
purple
doesn't
look
as
good
I
might,
with
my
opinion,
right,
that's
just
a
personal
opinion,
and
then
my
next
on
that
and
work
on
it.
It
could
be
something
meaning
you
can
collaborate
on
to
help
bring
me
a
little
bit
closer
to
how
the
code
yeah.
B
C
How
the
project
you
know
aspects
are
running,
I
would
love
to
you
know
address
particular,
you
know,
taste,
design,
aspects
on
dark
mode
that
you
might
be
concerned
with
yeah
as
much
detail
in
it
as
possible,
sure
sure,
and
the
only
other
one
was
done
below.
If
you
scroll
all
the
way
down.
The
totally
shows
that
I
made
those
are
like
I,
don't
know,
it'll,
look
a
start
because
I'm
all
of
contrast
and
young
and
on
the
features,
there's
three
feature
like
placeholders
that
we
have
so
I'm
gonna
have
to
create
illustrations.
E
A
C
The
bottom
one
is
easy,
though,
like
if
you
scroll
back
to
the
bottom,
so
the
elements
that
are
completely
so
that
white
rock
part
or
white
like
tab
I,
you
just
have
a
an
alpha
of
like
anything
over
C
or
you
know,
pricey
CED
de
ends,
because
on
a
bright
background
it
becomes
more
bright
as
it
can,
but
on
the
art
one,
it
just
becomes
a
little
bit
right
on
which
alpha
you
set
that
particular
element
to
yeah.
So
it's
it's
really
good
to
play
with
alpha
on
very
bright
elements.
C
In
your
current
vector,
cool
yeah,
we
go,
we
can
work
on
those.
The
only
other
thing
that
I
want
to
touch
base
on
this
is
everything
passes.
Accessibility,
color,
contrast
guidelines,
however,
for
that's
for
dark,
dark
mode.
However,
for
light
mode,
the
the
green
500
we're
calling
the
we're
calling
it
brand
500
on
white.
It
doesn't
actually
pan
accessibility
and
that
out,
that's
that's
brand,
oh
yeah,
no,
no!
No,
that
they
so
being
able
to
measure
Delta.
It's
called
Delta
II.
Well,
yeah
in
color
measurement
is
not
a
science.
C
It's
it's
more
like
people
just
guessing
who
can
who
can
prove
that
they're,
more
scientific
and
then
you
look
at
it
or
you're
like
you,
guys
are
crazy,
so
the
e
has
like
so
many
different
formulas.
At
the
end
of
the
day,
if
you
go
to
grayscale
and
you
see
it,
then
you
know
for
a
fact
that
there's
enough
contrast
and
even
for
a
colorblind
person,
that's
good
enough.
That's
a
good
enough
measuring
six.
So
if
you
can
see
it
and
you're
not
like
supervision,
you're
you're,
nobody
has
has.
C
You
know,
commented
on
how
you
can
see
things
when
they
don't,
then
then
you're
happy,
and
if
other
people
don't
complain
and
you
go
to
grayscale
and
you
still
see
the
contrast,
then
you
can
write
off
that
audit
computation
because
the
America
color,
sometimes
we
never
make
as
much
sense
as
visual
product.
You
got
it.
Okay,
then
that
makes
that
make
sense.
You
know
because
I
mean
that's
the
that's.
C
The
actual
brand
color
like
the
node.js
prank
caller,
so
yeah
I,
just
had
some
concerns
on
that
because
he
wasn't
passing
with
white
right
like
the
that
green
wasn't
passing
with
white.
So
what's.
C
C
A
A
B
Gives
me
it
gives
it
keeps
me
doing
stuff,
it
gives
me
direction,
I've
got
immediate
feedback,
and
then
it
sets
me
up
really
well.
If
I
want
to
go
and
work
on
things
on
my
own
I've,
you
know
got
plenty
of
context
around
what's
important
and
what
I
should
working
on
so
so,
even
if
even
if
you
know
you
have
your
heart
cut
off
I
found,
it
was
incredible
for
me
in
terms
of
getting
oriented
to
the
project
and
stuff,
so
yeah.
E
B
Sella
feel
free
to
ping
me
on
github
in
any
issues
or
anything
like
that.
I'd
love
to
be
able
to
walk
you
through
the
code
or
something
as
somebody
that
came
to
the
project
after
it
was
already
in
motion,
took
me
a
while
to
get
over
that
hurdle
and
onboarding
was
something
I
was
gonna,
try
to
work
on,
but
it's
one
of
the
many
things
that's
gotten
dropped.
B
C
B
Yeah
I
can
do
I
can
do
this
weekend,
probably
something
like
ping
me
in
the
agenda
of
the
issue
329
for
this
agenda
and
we
can
probably
talk
there
offline.
But
let's
try
to
figure
something
out:
I'm
in
the
Eastern
time
zone
and
I'd
love
to
sit
down
with
the
inner
otter.
I
won't
have
all
the
answers,
but
I'll
be
able
to
at
least
hopefully
give
you
something
so
perfect.
D
D
C
F
B
F
On
in
previous
version
of
flying
pages
it
currently
on
staging,
it
was
SVG
pictures
and
it's
I
decided
to
to
rewrite
it
by
pure
gif,
and
this
is
pure
CSS.
I
can
show
you,
maybe
so
you
quickly
yeah.
So
this
is
spam.
We,
the
ground,
color
yeah.
Is
there
a
reason
why
you
did
because
this
machine
is
not
optimized
stuff
and
CSS
functions
is
more
than
enough
scalable
more
flexible,
and
so
we
can
make
more
animation
stuff.
Is
that?
Because,
on
previous
version,
it
was
SVG
files
which
are
moving
only
in
fixed
places,
yeah.
C
F
C
A
C
C
Can
can
I
clarify
what
what
the
animation
intent
is?
So
are
we
saying
that
this
is?
This
is
centering
around
the
particular
focus
point
within
the
page?
So
we
have.
We
have
this
run
away
of
the
page
like
the
whole
scrollable
page,
that's
a
huge
rendering
context
right
so
SVG
or
CSS.
If
the
rapid,
the
computations
are
transformations,
are
occurring
for
the
full
run
away
of
the
page,
then
it
doesn't
really
matter
how
it's
implemented.
It's
going
to
be
eating
up
too
much
computation
for
four
areas
of
the
page
that
are
not
rendered
and
rendered.
C
If
we
do
them
as
separate
as
VG's,
then
you're,
creating
heavy
heavy
weight,
graphic
contexts
that
get
actually
layered
on
the
page,
wrapper
context
and
and
that
that
ducking
T
is
heavy.
But
if
it's
one
SVG,
that's
one
rendering
context
and
alpha
blending
over
the
page
and
if
it's
one
SVG
and
it
overlaps
the
runway.
In
my
experience
that
usually
just
triggers
re-rendering
computations
for
the
visual
view,
port
across
browsers
generally,
like
some
browsers,
are
still
a
little
bit
greedy.
C
Some
are
a
little
bit
less
greedy
and
you
see
they're
artifacts,
but
if
it
was
a
single
SVG,
not
many
instances
of
SPG's
with
you
know
subtle
changes,
then
it
could
actually
just
be
one
graphic
context
that
gets
updated
with
every
frame
of
the
link.
Yeah
I
mean
the
the
leaf
stuff
meant
to
cop,
to
accent
the
that,
like
that
section
where
you're
gonna
really
just
download
stuff,
or
we
could
put
something
else
in
there,
but
it's
not
technically
like
something
that
we
have
to
have
it's
just
purely
decoration
right.
C
So
my
take
is
like
if,
if
we're
dedicating
too
much
time
to
do
this
thing,
we
might
just
want
to
do
just
a
static.
You
know
thing
and
not
have
any
type
of
animations
or
anything
like
that
or
just
rip
it
out
completely
and
and
do
like
a
background.
Little
I
I.
A
So
I
think
the
the
active
question
here
is:
is
it
okay
if
they
are
randomly
generated?
Is
it
okay
if
they
look
a
little
different
than
the
mock
as
long
as
it's
in
the
same
spirit
of
the
of
the
intent
for
it,
and
is
it?
How
do
you
feel
about
doing
it
pure
CSS
versus
the
like,
consistent
SPG's,
because
I
saw
Alex,
you
had
you
had
a
randomization
function
in
there
too
or
or
it
right
so
like
they'll,
they'll
change
positions
a
little
bit
every
time
you
refresh
the
page
and
yeah.
F
C
C
So
so
without
the
blur
filter
it
runs.
But
then
what
you
want
to
do
is
you
want
to
have
an
help
of
an
alpha
fill
like
an
output,
radiant,
a
radial
gradient
or
something
so
that
the
leads,
though,
look
lured
on
the
edges.
If
you
want
to
blur
them
just
lure
them
alpha
blends
they're
not
really
blurring
into
something
particularly
well.
C
There
is
the
reason
for
the
blurring
was
so
I
didn't
give
a
little
bit
more
perspective,
I
guess
as
something
of
something
that
you're
focusing
there
other
things
blurred
right,
so
something
that
the
idea
was
that
one
some
of
the
petals
were
blurred.
Some
of
them
were
not,
and
some
of
them
were
more
blurred
than
others
yeah
we
depth,
but
but
yeah
like
yeah
I'm
with
with
Adam,
then
we
might
be
over
engineering
purely
illustration
right
and
I.
D
A
The
I,
like
the
idea
of
doing
it
in
pure
CSS
with
Dom
elements,
I
think
the
the
randomization
if
it
were
per.
If
it
looked
her
like
her
render
in
the
browser
it
might
be
entertaining
because
that's
each
time
you
refresh
you,
get
a
different
smattering
with
leaves,
but
I
think
on
the
on
the
per
build
basis.
You
run
the
risk
of
having
a
bad
build
where
you
get
a
bad
random
seed
and
now,
like
the
leaves,
are
like
all
consolidated
right
behind
good
the
the
dark
box
and,
like
you,
lose
balance
on
the
page.
A
F
We
can
add
some
animation
that
they
not
some
permanent
position
and
they
move
every
time.
I'm
I
mean
that
make
almost
the
same
that
we
have
already
like
on
one
scroll
move
somewhere
to
the
sleeves
and
I
think
we
I
I
just
haven't
enough
time
to
implement
that.
But
it's
just
just
possible
to
make
stuff
like
leave,
started
here
and
moving
somewhere
here,
and
this
also
will
be
randomly,
and
this
should
fit
all
the
web
page
and
make
it
more
interactive
item
not
not
interactive
but
more
interesting,
right,
yeah.
C
We
might
wanna
like
let's
tweak
that
a
little
more
because
I
for
some
people.
That
might
be
a
little
too
much
if
you
have
like
you,
know
cognitive
issues
with
them
things
moving
in
and
out
and
lost
stuff
that
might
be
participating
purposes.
That
might
be
a
little
challenging,
but
but
I
like
the
idea
of
like
making
these
a
little
more
like
if
you
hold
it
over
something
Mikey
moves
like
you
know
like,
if
you
hope,
or
you
could
try
to
hover
over
the
pedal
it
just
moves
and
it'll
be
cool.
E
D
A
Yeah
I
I,
like
the
the
intent
you're
bringing
to
all
this
like
from
a
technical
standpoint.
Yes,
CSS
and
Dom
would
be
better
Saul
I
like
what
you
said
about,
instead
of
putting
the
blur
filter
on
it,
which
does
take
off
a
lot
of
the
GPU
and
makes
it
even
harder
to
compose
together
at
the
end
of
the
day,
if
you
just
if
you
slap
a
box
shadow
on
it
and
blur
it
make
it
the
same,
color
you'll
get
the
same
exact
effect
with
the
solid
element.
F
B
A
C
Yeah,
let
me
see,
and
and
was
he
submitted,
Alexander
or
Alex
yeah
I'll-
take
a
look
at
it
and
see
if
it
looks
good
and
not
you
know
to
like
quote
unquote
too
much
for
the
user
right.
We
don't
want
to
take
away
from
the
content
we.
This
is
just
like
supporting
decoration,
so
if
it
is
too
daring,
he
might
take
away
from
the
for
making.
So
you
gotta
be
careful
with
that.
Yeah.
B
C
Good
question,
so
one
of
them
I
wanted
to
make
them
visually
different
than
all
the
other
buttons
that
people
would
be
would
know
that
these
are
more
important
in
of
like
these
are
the
ones
that
we
want
people
to
to
interact
with
with
the
most,
which
means
people
are
coming
to
this
website,
to
either
download
the
thing
or
learn
more
about
nodejs.
All
the
other
buttons
are
just
practically
supportive
buttons
for
actions.
Yeah.
F
C
That's
part
of
it
like
visually.
The
my
thought
was
visually
one
these
to
be
to
be
visually
different,
so
that
people
can
know
that
they
that
there
is
a
difference
in
importance.
This
subscribe
button
is
not
asked
important
in
this
page
as
the
two
buttons
on
top
and
I
wanted
that
roundness
to
signify
that
and
actually
they're
actually
I
believe
they're
taller
too.
So
it's
it's
a
it's
just
a
visual
thing,
like
you,
xee
yeah,.
F
C
I
mean
like
you
know,
you
can
go
both
ways
right,
they're,
very
subjective
things
we
could
potentially
like
do
tests
once
we
once
we
really
eaten
and
see
a
which
one
do
you
think
what
I
want
to
do
is
I
want
people
to
engage
these
buttons
more
than
the
others
right.
So
how
do
we
actually
that
that's
that's
the
best
quote-unquote
UX
problem
that
I
once
solved
so
something.
A
That
the
rounded
buttons
also
help
get
a
allow
them
enable
them
to
do
is
stand
alone.
A
lot
of
the
like
they're,
not
locked
up
with
anything
right.
They
are,
they
are
in
their
own
space.
They
have
to
command
their
own
attention,
the
the
more
squared-off
buttons
you
can
pair
it.
With
the
text
box.
You
can
pair
it
with
texts
that
are
like
it
kind
of
it
brings
itself
back.
You
know.
C
So,
just
to
point
out
traditionally
for,
for
you
eyes
not
just
well,
there
has
always
been
two
classes
of
of
buttons
in
any
user
interface
a
slightly
wrong,
because
you
know
they
got
rid
of
all
the
button
aspect
of
a
button.
But
if
you
always,
if
you
look
back,
there
has
always
been
a
button
in
the
toolbar.
C
That
is,
you
know
very,
very
distinct
from
the
button
that
ears
on
a
dialogue
or
a
button
that
appears
in
a
palate
where
you're
setting
properties
and
then
you
can
see
so
I
think
what
we're
seeing
here
the
round
button
is,
is
a
call-out
button.
It's
kind
of
like
this
is
an
action
that
you're
taking
for
a
particular.
C
And
the
section
here
talks
about
a
particular
thing
and
it
gives
you
options.
They
are
really
next
steps
here,
you're
going
to
go,
do
something
where,
as
utility
buttons
or
you
know,
widget
buttons
are
associated
to
a
particular.
Action
are
related
to
the
input
field
or
related
to
a
small
widget
within
within
the
bigger
page.
C
So
so
those
are
like
buttons
of
context
that
are
related
to
being
enclosed
or
encapsulated
by
a
sub
structure
in
your
layout
I.
Don't
think
roundness
being
uniform
or
not
is
a
very
universal
thing.
You
know
like
you
could
have
different
roundness
and
and
not
necessarily
as
long
as
you
don't
use
round
buttons
next
to
an
input
box
and
just
worry
about
the
next
an
input
box,
then
you
don't
create
that
confusion
exactly
yeah,
that's
what
I
wanted
to
get
to
and
and
my
big
again
these
are
very
subjective.
C
C
C
Well,
yeah
I
mean
we
can
we
can
test
this
thing,
usability
test
and
see
what
people
think
and
all
stuff
I
also
consider
another
call
out
of
the
same
significance,
we're
looking
just
a
download
and
learn
note
at
this
point,
but
consider
that
UI,
if
it
had
more
options
and
less
options
of
this
particular
style
of
button
one
day,
we
might
need
a
call-out
for
a
different
purpose
altogether.
That
is,
of
the
same
emphasis.
C
I
mean
so
so
just
consider
it
in
mind
that
if,
if,
if
we
are
happy
with
it,
if
it's
used
repurposed,
you
know
and
and
get
not
unfavorable
feedback,
then
it
is.
You
know
it's
not
necessarily.
Something
personally
would
find
you
know
worth
changing
at
this
point.
Right
make
sense
yeah,
but
those
are
cool,
cool,
colored
socks
and
I
appreciate
the
feedback.
Let's,
let's
go
ahead
with
with
what
we
have
today,
but
what
definitely
was
tested
and
asked
people
for
feedback.
F
B
Cause
here,
like
a
yeah
you're,
eight
ahead
of
Eastern
Time
I
was
gonna.
Ask
if
you,
if
you
were
interested
in
trying
to
get
into
the
hackathon
thing
we're
gonna
be
doing.
It
looks
like
maybe
October
19th,
but
that
would
be
probably
late
at
night
for
you,
it
would
be
going
until
maybe
midnight
your
time.
It
looks
like,
but
there's
an
issue
322
open
about
that.
If
you're
interested,
please
please
feel
free.
A
A
Yeah
well
we'll
just
post
a
post,
a
a
chat
like
a
video
chat
linked
closer.
Today
we
have
what
was
the
issue
number
John,
3:22
yeah,
if
you
322,
is
where
that's
written
so
well,
September
or
sorry,
October
19,.