►
From YouTube: Node.js Website Redesign
Description
B
A
B
C
However,
having
discussed
with
him
for,
like
the
last,
you
know
a
couple
weeks,
he's
kind
of
on
board
as
long
as
he
can
start
on
July
10th
and
he's
very
willing
to
kind
of
come
over
as
long
as
it's
a
predictable
schedule.
So
one
of
the
things
that
I'd
like
to
do
is
before
July
10th.
Just
people
give
him
like
a
you
know.
If
you
can
be
here
for
days
every
other
week
or
whatever
whatever
it
might
be.
This
is
largely
going
to
be
a
decision
for
you
all.
C
Then
he
he
would
feel
very
comfortable
that
there's
the
main
reason
he
was
kind
of
on
the
fence
before
was
he
thought
that
like,
given
that
this
was
a
team
you've
never
worked
with
or
whatever
he
wouldn't
be
able
to
like?
Do
a
great
job,
which
is
why
he
thinks
it's
like
really
important
to
be
we'll
have
like
one-on-ones
and
stuff
like
that.
So
yeah.
B
Totally
I,
like
your
idea
of
on
the
off
weeks
from
this
meeting,
I'm
coming
up
yeah
that
way,
we
have
a
touch
point,
a
touch
point
midweek,
one
so
every
other
week
and
then
like
a
heads
down
for
days,
while
he's
on
site,
great
yeah
and
and
you're
sure
he
doesn't
mind
flying
out
that
often
you
said
he
wanted
appointments
here,
a
nice!
That's
right,
so
yeah.
C
So,
like
we've
worked
with
him
a
lot
before,
that's
the
main
reason
I
wanted
him
on
here,
just
because
it
you
know
technically,
for
the
paperwork
I'll
be
his
manager
for
this
thing
and
so
I
kind
of
just
wanted,
given
that
it's
already
this
kind
of
weird
setup,
something
where,
like
some
amount
of
familiarity,
so
yeah
he's
come
here
before
even
on
like
projects
with
us,
you,
like
San
Francisco
it's
summer,
so
his
kids
are
at
camp
and
stuff.
So
if
there's
a
time
to
do
it,
now
is
the
time
to
do
it.
Homes
well,.
B
C
I
sent
him
I,
sent
him
a
bunch
of
links
house
with
some
kind
of
like
the
the
color
stuff
we
had
talked
about
and
that
sort
of
thing
I
imagine
he'll,
be
kind
of
consuming
all
that
a
lot
greater
detail
like
closer
to
July
10th
but
yeah.
If
there's
anything
you'd
like
to
me
to
give
him
specifically
before
he
starts
just
forward
it
to
me
and
I'll
forward
to
him,
I'll
also
just
do
like
an
email
intro.
So
we're
not
like
yeah.
C
Go-Between
right
yeah,
but
the
goal
is
for
him
to
be
able
to
work
much
more
directly
with
you
guys,
so
it
should
not
feel
like
I'm
like
filtering
the
information
or
something
the
the
other
kind
of
question
I
had,
which
I
just
don't
know
anything
about
is.
Is
there
like
a
stripe
sets
up
like
the
legal
around
this?
Is
there
anything
on
your
guys's
and
basically
we
want
the
work
he
does
to
belong
to
you
guys
I,
don't
know,
there's
some
sort
of
something
we
need
to
sign
or
something
again,
I
don't
know.
C
A
That'd
be
on
my
so
as
far
as
I'm
aware,
no
but
like
that's
just
because
I've
never
had
to
deal
with
that
process.
So
let
me
dig
in
there.
The
foundation
is
having
some
changes
they
recently
so
I'm
gonna
have
to
dig
into
that
and
see
what
I
can
find
around
that.
But
I
will
actually
send
out
a
message
now
to
someone
to.
A
A
B
B
B
Sweet,
let's,
let's
get
a
video
call
set
up
for
then
cuz
I'm,
assuming
you
won't
be
out
here.
He
might
be.
If
you
get
one.
C
B
B
Synthesis
of
what
we
had
worked
on
there
in
the
collaborator
summit
issue
number
60
the
awesome
list
of
all
different
topic
ideas
for
getting
started
content.
We
like
we
talked
about
before.
We
want
to
break
this
out
into
separate
issues
for
each
one
and
set
up
a
process
for
people
to
contribute
back.
I
took
a
first
stab
yesterday
at
getting
that
process
set
out
issue
number
64
or
PR
number
64.
Sorry,
and
it
basically
outlines
a
pretty,
hopefully
pretty
straightforward,
RFC
process
for
contributing
documentation,
documents
and
a
place
to
do
so
inside
the
repo.
B
While
we
wait
for
the
final
infrastructure
and
documentation
ingestion
system
to
be
set
up,
so
we
can
actually
start
iterating
on
content
here
list
and
markdown
format.
In
the
meantime,
yeah
I
just
wanted
to
raise
visibility
of
that
and
hopefully
get
a
little
guys
hoping
they
would
be
here
so
that
we
could
get
leadership
consensus
at
least
so
you
can
pull
it
in
and
start
making
those
issues,
but
yeah
would
love
feedback
on
that.
When
you
get
a
chance
to
read
through
yeah.
A
B
A
A
I
think
we
had
attempted
one
at
one
point:
no
js',
CPS
I.
Think
yes,
I!
Think
we're
also
about
to
archive
that
repo
cos
like
that's
where
all
the
major
things
like,
yes,
modules,
HTTP
to
async
hooks
an
API
and
stuff
we're
like
originally
discussed,
but
it
the
flow
we
ended
up.
Having
was
actually
very
different
from
how
they
like
what
was
proposed,
and
it's
just
to
say
like
that
was
you
know
one
instance
where
I
think
we
did
have
that
flow,
but
not
to
say
that
it
wouldn't
be
useful
elsewhere.
Yes,.
B
Yeah
well
my
thoughts
were
this.
Sorry,
it's
it's
in
place
until
we
get
the
final
solution
working
and
it's
just
a
good
way
to
yeah
to
give
people
a
place
to
go,
contribute
content.
This
will
be
source
of
truth
until
we
we
move
stuff
into
the
main
node
repo
and
get
that
get
all
those
wires
hooked
up.
B
C
B
A
B
C
Cool
I
just
I'm
listening
it
was
wanting
to
do
some
sort
of
clockwise
things.
I
was
hoping
I,
don't
know.
This
is
the
right
place
to
ask
or
whatever,
but
one
of
the
things
we
were
hoping
for
is
if
we
could
start
doing
kind
of
like
a
test
run
of
a
couple
embeds
and
the
API
dogs
like
they're,
already
some
some
of
them.
That
would
you
know
you
could
just
swap
in
with
him
in
bed
and
prior
to
an
actual
redesign.
C
Just
have
some
of
them
be
runnable,
mainly
because
we
want
to
do
a
couple
of
so
the
DD
and
you're,
pretty
pretty
explicit
about
the
couple
of
things
we
want
to
figure
out
before.
Like
you
know,
we
flipped
a
switch
or
something
we'd
like
to
develop
some
of
the
features
that
you
guys
had
already
known.
You
want
to
request
like
hey,
we
don't
want
no
tip,
you
tend
to
show
up
in
the
drop-down
that
sort
of
thing
so
we'd
like
to
be
able
to
like
kind
of
get
that
rolled
out.
C
We
also
just
want
to
get
some
sense
of
like
kind
of
what
the
traffic's
gonna
be
for
us,
namely
because
we
like
have
been
thrown
around,
maybe
just
having
a
dedicated
server
for
the
note
page,
because
it
might
be
the
case
that
that
you
know
has
enough
traffic
where
we
want
to
do
that
kind
of
thing.
So,
I
don't
know
if
the
right
people
to
talk
to
are
here
or
if
we
need
to
talk
to
someone
in
the
maid
node
repo
about
that,
like
I
just
gets
thrown
that
out
there
yeah.
B
B
A
C
C
That
sounds
great
and
then
I
guess
the
one
of
the
other
components
of
this
that
we
wanted
to
kind
of
get
started
on
now,
but
I
know
might
be
a
little
still
up
in
the
air.
Is
that
our
thinking
is
kind
of
regardless.
Since
we
don't
really
know
the
way
it's
gonna
be
implemented
in
the
future,
we
were
just
gonna
kind
of
dive.
In
with
a
like
we're
gonna
assume
it's
gonna
continue
being
implemented.
The
way
it
is
and
like,
for
example,
build
out
support
for
like
making
the
run
kid
stuff.
C
Just
work
with
the
the
markdown
parser
who
it
starts
to
am
I
can
always
get
the
name
confused
so
back
time
to
make
okay,
yes,
we're
just
building
out
that
plugin
or
something
I
don't
know
it.
I
was
just
curious
if
there
was
already
strong
opinions
of
like
oh
man,
we're
definitely
not
gonna
use
that
no.
B
The
nice,
the
nice
thing
about
the
approach
we've
been
taking,
it's
we've
been
doing
it
one
state
at
a
time,
which
means
we
have
zero
technical
opinions
right
now
cool.
So,
if
you
I
think
they're,
the
only
technical
opinions
we
have
are,
we
want
to
use
run,
get
the
significant
part
of
the
site.
So
let's
wait
technical
opinions
yeah,
so
we
any
any
groundwork.
You
lay
right
now
that
you
deem
the
best
path
for
getting
run
kid
in.
There
will
set
the
foundation
for
OPP
later.
B
The
other
technical
opinion
we
have
is
we
don't
want
to
have
to
rewrite
all
the
existing
documentation
right,
which
means
it
will
still
live
in
markdown.
You
know
and
we'll
still
live
alongside
the
main
nodejs
code.
So
if
you
work
with
the
current
API
Doc's
as
is-
and
you
get
it
hooked
up
with
run
kit,
I
think
that
it's
a
very
safe
path
forward.
Okay,
great
Bres,
yeah,
sweet.
A
A
Yes,
so
I
had
I
had
another
issue
that
I
wanted
to
bring
up
around
user
feedback.
I
created
an
issue,
61
I'll
put
it
in
the
zoom
chat,
go
around
possibly
putting
out
a
you
know
a
survey
just
around
the
docs
to
begin
to
allow
us
to
iterate
on,
or
you
know,
get
your
feedback
on.
What
is
and
isn't
helpful.
A
This
will
be
the
second
like
this,
assuming
it
happens,
which
you
know
I
think
is
still.
You
know
TBD.
If
the
group
wants
to
do
it,
this
would
be
the
second
initiative
or
working
group.
That's
done
this
and
basically
the
guidelines
are
kind
of
you
know,
radio,
buttons
or
multiple-choice
or,
like
you
know,
a
scale
from
one
to
ten
type
thing
like
an
FPS
or
you.
You
want
to
limit
a
text
input
as
much
as
possible
just
because
it
makes
analyzing
today.
C
B
A
B
Yeah,
it
would
be
nice
to
build
that
question
there,
questions
for
that
in
opinions
and
what
we
want
to
gather
Francisco
can
and
what's
his
name.
I
would
like
to
start
stop
calling
him
Joey,
Joey,
Ellis,
Joey,
okay,
that's
helpful,
hey
how's
it
going
yeah,
so
good
would
Joey
I'm
assuming
Joey
would
would
probably
love
to
have
input
on.
You
know
if
we
ask
the
whole
node
community
what
you
like
what
you're
not
like.
Well,
yeah
yeah
in
documentation.
B
D
B
Worries
yeah
we're
we're
actually
just
at
the
tail
end
of
this
discussion.
Journey
Mike
just
cut
out,
unfortunately,
but
we're
yeah
journeys,
Mike
just
cut
out,
but
we're
talking
about
issue
number
61
its
proposal
for
doing
another
round
of
user
feedback
on
nodejs
box,
so
I
person
think
it's
an
awesome
idea
like
what
that's
the
community
what
they
want
to
see.
That's
the
whole
point
of
a
user
focused
design
and
iterative
feedback.
So
but
I
was
also
just
saying
that
we're
talking
earlier
Francisco
Joey
is
the
same
right.
Yep.
B
The
designer
that
run
kit
is
very
kind
of
giving
us
for
three
months
is
starting
on
the
10th
I.
So
that's
it!
Next
to
this
upcoming
yeah
I
know
right
and
we'd
love
the
we'd
love
him
to
have
to
have
feedback
on
the
whatever
questions
are
asked
for
this
as
well.
So
we'll
keep
talking
about
that
with
our
meeting
on
yeah
and
then
the
only
other.
So
we
we
hashed
out
some
details
on.
B
Design
start
date
and
some
some
legal
questions
and
then
the
only
other
check
it
brought
up
other
than
this.
This
one
I
believe,
was
my
pull
request
from
yesterday
number
64
I
proposed
a
process
for
contributing
documentation
to
the
repo
I,
like
just
a
little
outline
and
little
template
to
a
to
follow
for
and
where
to
put
it
in
the
repo
while
we're
waiting
on
the
documentation
ingestion
pipeline
to
actually
get
finalized.
So
we
can
actually
start
working
on
content
here
with
a
little
bit
of
order.
D
I
haven't
seen
that
yet,
but
I
wondered
if
we
could
rope
and
Addyson
on
that,
because
her
fur
might
have
insight
on
how
they
do
their
documentation
with
Drupal
and
they
were
intending
initially
to
help
us
write
the
guide
for
contributing
documentation.
It
was
there's
been
some
we're
trying
to
wait
on
both
Francisca,
who
wants
it
to
do
a
video
on
how
to
do
a
documentation,
PR
and
them
who
wanted
to
the
write
the
technical
side
of
it.
Yeah.
B
B
Video
that
Francisco
was
talking
about
would
be
for
like
API
documentation,
which
we
know
where
that
lives
and
how
it
works
and
we're
not
going
to
change
it
as
part
of
this
process,
but
for
for
like
for
guides
and
more
detailed
Doc's,
we
don't
know
really
where
it's
gonna
live
yet
or
how
we're
gonna
be
pulling
it
into
the
new
website.
I
feel
like
we're
getting
started
content
so
I
don't
know
if
we
need
a
block
on
the
video
for
for
getting
this
process
out
there
at
least
okay
cool
yeah.
B
B
Know
still
can't
hear
ya,
I
awesome,
yeah,
so
yeah
once
this
gets
pulled
in
I
think
we
can.
We
can
then
split
out
all
those
giant
lists
of
items
into
separate
issues
and
just
point
people
to
this
process.
It
basically
just
gives
gives
a
place
in
the
repo
for
proposed
guide
pages
to
live
and
a
template
for
drafting
them.
B
B
B
What's
our
take
on
new
documentation
towards
removing
and
adding
new
Docs,
so
I
think
the
the
goal
right
now
is
vanilla.
Your
issue
is
issue
number
60
right,
so
we
didn't
sir
size
at
the
collaborators
summit
to
kind
of
brainstorm,
new
types
of
documentation
and
new
types
of
content.
So
that's
issue
number
60
under
website
redesign.
We
have.
We
have
really
really
bad
getting
started.
Docs
j/s
web,
the
api,
sir.
B
B
There's
not
a
lot
of
content
on
there.
So
in
the
new
site,
we're
hoping
to
have
like
a
lot
of
other
a
lot
of
other
platforms,
a
getting
started
section
or
a
guide
section,
and
so
we're.
We
are
rewriting
documentation
for
that,
at
least
from
the
ground
up,
so
we're
the
the
opinions
and
thoughts
on
removing
and
adding
new
Doc's
were
all
for
it.
Let's
do
what's
best
yeah
I
think
that's
kind
of
the
opinions
we're
still
looking
for
that.
B
We're
still
looking
for
that
that
right
and
perfect
solution,
so,
let's,
let's
keep
iterating
towards
there,
that's
for
more
questions
in
the
chat
yeah,
so
I
literally
just
opened
up
this
PR
yesterday,
it's
a
we
don't
know
right
now,
because
we
don't
have
the
infrastructure
for
the
site
built
yet
very
intentionally
like
we're,
hoping
to
focus
on
design
for
a
while.
We
don't
know
where
this
new
documentation
will
live
exactly
or
what
format
it'll
come
in.
B
We
presume
it's
gonna,
be
marked
down,
seems
reasonable
and
we'd
love
for
it
to
live
alongside
the
main
nodejs
codebase.
I
because
we
heard
a
lot
of
concerns
from
some
core
contributors
that
if
it
doesn't
live
right
alongside
the
codebase
people,
won't
keep
it
updated.
People
won't
contribute
to
it,
because
if
you
change
your
feature,
you
now
need
to
make
a
PR
in
another
repo
to
go.
Make
it
happen.
So,
let's
keep
just
like
with
the
API
Doc's.
B
B
So,
in
the
meantime,
until
we
get
documentation,
ingestion
and
insight
infrastructure
working
and
know
where
it's
gonna
live,
let's,
let's
use
this
repo
as
the
the
current
staging
ground
for
new
new
guides
and
new
documentation
documents
and
and
follow
this
process
to
get
them
submitted
so
yeah
they
would.
They
would
PR
it
against
this
repo,
and
once
we
have
the
infrastructure
figured
out,
we
will
do
a
mass
migration
of
all
this
documentation
to
where
it's
the
final
living
place
is
gonna,
be
so
this
way
we're
not.
B
Get
no
worries
cool.
Well,
if
that's
it
I
think
we'll
end
the
stream
and
call
it
a
meeting.
Thank
you
all
for
joining.
Thank
everybody
who
called
in
on
YouTube
to
listen
again,
see
their
bio.
Oh
I
can't
actually
stop
this
stream
because
I
because
tyranny
started
it.
You
know
you
drop
so
we'll
just
we'll
just
all
drop
off
and
host
the
meeting.
Actually
I'm.
Sorry.