►
From YouTube: Node.js Website Redesign
Description
A
A
One
month:
okay,
first
things:
first,
because
I
promise
the
summit
folks
that
I
would
say
this.
Every
meeting
y'all
need
to
just
hit
your
travel
fund
requests
if
you're
using
it
or
and/or
register
for
the
conference.
Sorry
summit,
this
interchangeable,
the
collaborator
summit
is
happening
in
less
than
three
weeks
and
we
will
all
be
meeting
in
Berlin.
So
please
register.
If
you
need
the
link
it
is.
A
Would
anyone
have
the
link
handy
else?
I
know
where
to
go,
get
it
I'm,
looking
right
that
I'm
having
and
II
know
I'm
dropping
you
here,
152
in
summit
in
this
summit
repo,
if
anyone's
on
YouTube
and
is
a
collaborator.
Please
look
inside
the
summit,
repo
of
nodejs
and
issue.
152
has
the
link
it
spins
at
the
top.
That's
my
first
update.
Anyone
else
want
to
go
first.
Next.
A
Yeah,
that's
super
important,
there's
a
thing
in
open
source
where
folks
think
that
well,
because
most
people
aren't
paid
for
open
source,
they
do
it
on
their
off
time.
So,
like
people
take
the
from
the
regular
jobs
and
then
I
could
be
like
oh
I'm,
very
activist
or
some,
but
not
take
an
actual
vacation.
Please
take
vacations!
That's
your
public
service
announcement
from
website
redesign.
We.
B
Have
an
update
from
Oscar
who
couldn't
make
the
meeting
today,
but
as
a
few
things
started
on
the
design
front,
he
dropped
a
comment
in
the
issue
ticket
which
is
166
over
in
website
redesign.
He
dropped
a
link
to
a
figma
board
where
he's
gonna
be
continuing
to
iterate
on
lower
level
design
systems.
He
stuff,
as
he
keeps
working
on
mocks
for
all
this.
He
has
a
few
questions,
one
of
which
is
a
very
fun
and
exciting.
B
B
B
There
we
go
and
I
had
a
few
questions.
I
answered
some
down
below.
He
was
asking
dark
mode.
Question
mark
and
I
at
least
said:
yeah
makes
sense,
it's
gonna
be
a
lot
of
reading
on
this
site.
Everyone's
doing
dark
mode
helps
with
the
eyes.
Let's
do
it.
While
we
can-
and
he
has
this
survey
thrown
up-
he
doesn't
want
it.
The
responses
coming
in
on
his
Google
account
so
I'm
gonna
port
it
over
and
we'll
get
this
thing
sent
out
on
social.
That's
like
hey!
B
B
Let's
say
many
as
I
think
as
nice,
as
as
recap
would
go
or
would
be
going
over
meeting
notes.
I
think
I'd
rather
go
through
the
agenda
and
see
what
yeah
you
can
see
where
conversation
takes
us
may
roll
back
into
you
just
recap
by
the
end,
but
added
a
couple:
extra
tickets,
just
just
for
up
leveling
on
first
thing
on
the
agenda
here
is
179
in
je
s,
dev
I
just
wanted
to
check
on
status
here
and
owner
I'm.
Very
glad
you're
on
the
call
I'd
love
to
see
this
thing
land.
B
C
B
Right
then,
right
now,
just
code
changes
is
the
problem.
The
integration
works.
Finally,
just
got
yeah
yeah.
Okay.
I
may
have
a
little
bit
of
time
this
weekend
to
pull
this
down
and
and
start
just
making
the
syntax
changes
so
I
I
might
I
might
be
able
to
pick
that
up
and
and
help
you
out
get
this
across
the
line
that.
B
Oh,
no,
it's
totally
fine
upgrading
stuff
to
winter
integrations
is
it's
a
pain,
so
yeah
I'll
see
you
I'll.
Do
my
to-do
list
for
this
weekend
and
more
I'll
see
if
I
can't
get
an
updated
and
it's
been
a
long
time
since
I've
had
a
code
contribution,
so
I
think
I
owe
I
owe
the
repo
a
little
bit
of
TLC
so
I'll.
Take
that
up
cool.
B
There
was
an
open
question
in
250.
I
want
to
make
sure
we
got
answered,
or
at
least
documented
no
Jeff-
that
dev
slash,
250,
just
kind
of
a
question
on
GCB
run:
I
I'm,
actually
a
little
shake
like
what
permissions
somebody
needs
to
actually
run
that
command
and
at
least
documenting
this
would
be
helpful.
It
looks
like
it
they'll
still
work,
because
we've
had
contributors
run
it
on
subsequent
pull
requests,
since
I
was
open.
C
Think
the
thing
that
caused
a
bit
confusion
is
that
that
Kevin
tried
to
send
that
command
as
he
landed
in
the
redesign
for
service
contributor.
My
guess
he
wasn't
indeed
in
the
foundation
group
I
mean
in
the
node.js
group
in
get
up.
So
that's
why
there's
why
he
didn't
didn't,
have
the
permission,
I
guess:
I'm
a
bit
ship
work.
Ashley
should.
B
Work
yeah
I'm,
looking
to
see
if
there
was
any
rum
in
the
last
nine
days,
yeah
miles
did
it
seven
days
ago
on
another
project
here,
so
it
does
still
work
I
think
we
just
need
some
clarification
around
who's
able
to
run
it,
and
it
sounds
like
anybody
in
the
group.
It's
able
to
now
confirm
with
miles
will
add
some
LOD
some
docks
around
it.
Would
you
know
who
is
and
isn't
able
to
run
that
command
and
I
believe
miles
still
is
planning
on
making
this
automatic
thrown
in
to
get
hook?
B
Awesome
those
are
kind
of
the
two
tickets
that
I
was
looking
through.
The
backlog
wasn't
sure
what
status
was
on
anybody
else's
open
questions
before
we
dig
into
slightly
meeting
your
stuff
I
feel
free
to
chime
in
now,
I
yeah.
Are
there
any
other
open
issues
that
just
kind
of
need,
a
quick
sink
to
unblock.
B
That
isn't
no
nifty,
so
we
have
just
two
other
smaller
things.
Well,
two
other
media
things
in
the
agenda,
one
of
which
I
kind
of
want
to
save
for
the
breakout
session
78.
Considering
that
localized
Docs,
we
had
a
dedicated
one
for
that,
but
I'd
love
to
brainstorm
a
bit
around
issue
number
158,
since
we
still
have
a
half
hour
in
this
meeting,
and
maybe
the
three
of
us
can
call
it
an
approach.
Moving
forward,
get
someone
get
someone
started
on
it.
B
B
B
So
we
have
these
are
the
pages
we're
talking
about
here.
We
need
I,
think
a
little
more
context
and
unless
I
know,
I
need
more
context
around
where
and
how
these
are
actually
built.
I
mean
these
are
generated
from
mark
down
in
nodejs
core
right,
like
in
the
node
core
repo,
so
I'm
tracking
it
down
there
right,
no
js'
node,
that's
the
name.
So
there
is
this
doc,
folder
doc,
slash
API
in
node,
core
or
nodejs
node,
and
these
pages,
whenever
there's
a
whenever
there's
a
build
of
node
that
goes
out.
B
These
pages
are
generated
just
from
those
markdown
files
in
10,000,000
ways.
So
there's
you
know
a
JSON
dump
representation
of
every
of
every
source
file,
there's
single
pages
for
every
source
file
and
then
the
menu
is
obviously
generated,
and
then
there's
that
view
on
single
page
option,
which
is
just
a
giant
concatenated
version
of
all
the
of
all
the
docs
so
I.
B
Ideally,
our
API
documentation
page
is
something
a
bit
more
interactive
and
a
bit
a
bit
nicer
to
work
with
I
think
that's
a
long
way
off,
because
that
will
require
a
significant
documentation
effort
in
node
core,
but
we
should
be
able
to
do
something
with
these
API
files.
Now
there's
a
lot
of
there's
a
lot
of
weirdness
once
you
start
thinking
about
bringing
up
historical
API
documentation,
you
know
how
do
we?
How
do
we
generate
all
that?
Where
are
these
things
hosted?
Is
this?
B
Do
we
need
to
kick
off
a
build
of
the
entire
website
because
we're
in
s.p.a
in
order
to
get
an
API
documentation
update
or
are
we
pulling
from
some
other
external
data
source?
Sir
I
still
statically
build
HTML
files
at
the
end
of
the
day?
We're
just
doing
you
know
we're
redeeming
it
essentially.
So
it's
a
feels
like
a
seamless
integration
with
the
website,
or
are
we
Publishing
to
a
JSON
package
which
we'd
statically
host
somewhere
and
pull
in
render
dynamically
on
our
website?
So
you
know
it's
not
no,
no
dev!
B
B
B
A
B
B
B
Node
core
or
like
an
artifact
from
node
core.
My
hunch
would
be
that
this
is
getting
built
and
deployed
to
the
same
URL,
but
in
a
different
in
a
different
folder.
So,
like
my
guess,
would
be
all
the
API
Doc's
would
be
part
of
the
the
CI
build
dumped
on
to
the
node.js
org
server
in
a
static
location,
and
it's
just
it's
just
part
of
CI
as
it
gets
built
out,
but
don't
take
my
word
on
that,
so
it
might,
it
might
be.
B
A
B
B
There's
a
this:
is
a
nice
like
first
time,
contributor
task
to
because
there's
just
like
static
JSON
sitting
up
on
a
server,
it's
pretty
like
getting
getting
an
API
page
that
picks
up
that
API
renders
a
thing
on
to
the
page,
doesn't
have
to
look
pretty,
but
just
like
dumps.
Api
Doc's
on
the
page,
as
is,
is
an
awesome,
getting
started
task
or
sorry,
first
time,
first
time,
contributor
task
I
should
be
nice
to
so
we
can
capture
that
and
have
it
on
here.
I
have
people
pick
it
up
as
needed.