►
From YouTube: Node.js Website Redesign
Description
A
Awesome
and
we
are
live
on
YouTube
hi.
Everybody
welcome
to
another
episode
of
website
redesign
working
group
yeah.
Let's
just
do
a
quick
round
of
introductions
for
the
YouTube
channel
since
it's
a
small
group
today,
I'm
Adam,
a
community
committee,
chairperson
and
co-lead
of
the
website,
redesign
working
group
at
LinkedIn
in
San,
Francisco
miele,
but
you
next,
I'm.
B
C
A
Awesome
I
want
to
see
an
issue
that
should
be
on
here,
but
isn't
cool
anyway.
Our
agenda
for
today
is
over
on
website
redesign
issue,
number
113
and
yeah
for
people
on
the
call
pop
open
the
docs
and
add
yourself
into
the
present
header,
pretty
please
we'll
just
start
from
top
and
go
down
and
I
probably
get
through
the
agenda
pretty
quick
and
leave
it
open
for
discussion
after
the
fact.
First
issue
on
the
agenda
is
creating
branch
of
the
docs
using
run
kit
I
had
a
chat
with
Francisco.
A
They
are
completely
unblocked
now,
which
is
awesome.
They
were
waiting
on
a
PR
to
land
in
I.
Believe
I
forget
exactly
what
open
source
project,
but
it
landed
and
they
can
now
get
a
built
in
with
the
first
couple.
Demos
enabled
I
think
Francisco
is
leading
this
and
he
should
be
good
to
go
so
I'm
actually
going
to
go
ahead
and
remove
the
agenda
tag
from
this,
because
it'll
be
a
completely
different
task
to
get
this
into
the
new
site.
A
But
since
he's
unblock
the
one
didn't
stop
tracking
it
here.
Cool
next
topic
issue
number
105:
this
is
Flavio's
awesome.
Pr
Hertford
nodejs
handbook
content
yeah.
This
has
been
open
for
a
while.
How
do
people
feel
about
pulling
this
in
since
its
had
a
cycle
of
reviews
and
Fabia
was
updated
it
with
with
the
Pyxis.
B
A
We
got
a
looks
like
floo,
floo,
floo
cardi
and
some
pretty
expensive
reviews.
Their
tyranny
took
a
look
at
it.
No
approvals
like
explicit
approvals,
but
I
mean
it's.
It's
huge
and
I
feel
like
it
a
lot.
You
know
we're
gonna
find
plenty
of
copy
errors
down
the
line.
I'd
rather
landed
and
master
and
iterate
on
it
than
yeah.
D
A
B
A
To
get
this
on
the
calendar
for
we,
we
agreed
to
run
through
in
the
TSC
meeting
for
website
redesign
update
on
January
23rd
of
next
year.
Oh
so!
Well,
it's
just
this
shouldn't
be
on
the
agenda
and
we'll
just
need
a
follow-up
closer
to
then
issue
number
99,
Doc's
hackathons
video.
Has
there
been
any
we've
been
on
this,
but
you
know.
B
Discussion,
our
last
discussion,
I'm,
not
sure
if
we
actually
came
up
with
a
action
item
for
this,
if
we
did
I
there
I,
don't
recall
I'm
sorry,
there
hasn't
been
movement
on
that,
but
I
think
now
it
could
be
good
to
come
up
with
one
tonight
and
though
we
can
move
this
on,
because
it's
really
useful.
B
They're
you're
still
regular,
so
if,
like
so
there's
one
happening
this
weekend,
it's
a
regular
third
Saturday
of
the
month,
intro
to
open
source
meetups
that
we've
been
running
for
a
couple
months
now
and
on
the
second
Saturday
of
each
month.
We
also
have
the
regular
notes:
go
meet
up
so
twice
a
month.
There
is
a
note
school
in
Vancouver
regularly,
and
we,
if
we
want
to
piggyback
on
that,
that
would
be
that
could
be
cool.
It
would
be
less
useful
to
jump
on
the
first
one,
because
the
first
one
people
typically
do
work
shoppers.
B
But
if
we
were
to
turn
it
into
an
actual
hackathon
where
you
know
like,
we
said
trumpet
time
and
people
dive
down
to
Docs
and
do
stuff
that
one
would
be
a
good
one
to
do
that.
But
unless
it's
a
full
out
we're
turning
this
into
an
entirely
different
event,
then
the
best
one
to
use
is
the
intro
to
open
source
one,
because
in
that
one
we
can
get
people
on
board
with
processes
and
teach
them
or
share
how
we
do
our
our
PRS
into
into
our.
How
do
you
say?
I
read
both
and
not.
B
A
B
If
you
read
through
that
and
you
could
follow
along
or
you
have
any
contributions
or
if
it's
a
step
by
step
thing,
you
can
try
and
execute
it
yourself,
and
if
you
want
to
PR
something
back
into
this
thing
that
our
that's
our
already
landed,
that
would
be
really
cool.
How
does
that
sound
to
people
here?
It
sounds
perfect.
A
B
A
Believe
they
can
make
a
PR
directly
into
that
particular
file.
There's
a
section
head
there
when
you
need
to
follow
this
process,
you
need
to
follow
this
process.
If
you
intend
to
make
a
substantial
addition
or
change
to
the
proposed
nodejs
getting
started
guides
in
the
repo.
What
constitutes
substantial
change
of
all
is
based
on
community
norms.
Some
changes
do
not
require
an
RFC
so
yeah.
If
it's
like
copy
changes
or
small
content
changes,
I
think
they
can
just
modify
the
file
directly.
I
don't
want
to
make
people
jump
through
hoops
cool
yeah
awesome.
A
Take
it
go.
Here's
the
ticket
cool,
it's
so
I'm,
yeah
gonna
say
we
move
on
from
99.
We
get
66
user
feedback.
Nodejs
doc
survey
issue
number
61.
This
is
an
issue
that
tyranny
popped
open,
just
getting
more
general
user
fee.
There's
a
lot
of
conversation
on
you
getting
more
feedback
on
how
people
like
the
current
documentation,
what
documentation
people
like
around
the
internet.
What
features
they'd
like
to
see
I
outside
of
the
little
circle
that's
been
talking
about
it
here.
There's
a
proposed.
A
Survey
over
here,
I
just
link
to
it
in
the
chat.
It's
also
linked
in
the
issue.
I
would
love
to
see
this
go
out
and
just
get
all
of
calm,
calm
to
blast
it
out
on
Twitter
and
maybe
the
no
js'
folk
node.
You
have
Twitter
account
as
well
talk
to
foundation
about
that.
I
do
think
that
the
forum
needs
a
little
help.
A
There's
a
lot
of
freeform
answers
in
there,
which
will
be
a
pain
for
us
to
go
through
yeah
would
love
to
take
another
pass
at
getting
this
documentation
feedback
from
ID
because
there's
an
awesome
first
draft,
but
it
can
be
improved
before
actually
sending
it
out
thoughts.
Volunteers,
take
a
stab
at
updating
the
survey.
B
B
A
Thank
you
so
much
yeah,
let's
just
get
activity
back
on
that
the
the
issue
just
kind
of
went
to
the
backburner.
So,
let's,
let's
get
activity
on
that
going
again.
I'd
love
to
get
the
survey
sent
out.
It
leaves
just
for
general
feedback
by
let's
just
set
an
arbitrary
date,
because
deadlines
are
helpful
days
of
today.
Let's
try
and
get
this
able
to
be
sent
out
by
end
of
month
would
be
nifty.
B
Out
I
personally,
oh
I'm,
sorry
yeah,
it
definitely
is
getting
pretty
bad.
I
pasted
the
link
to
the
issue
and,
if
you
know
we
typically
don't
have
a
process
where
people
assign
themselves
to
issues
usually
do
we
Adam
it's
only
very
rarely.
When
there's
a
very
specific,
we
need
very
specific
eyeballs
on
it
that
we
have
people
assign
themselves
yeah.
A
They're
not
it's
also
a
pain,
because
we
can't
actually
assign
people
like
literally
assigned
people
to
issues
unless
they're
in
the
org,
which
is
interest.
Another
reason
why
we
don't
do
that.
Unfortunately,
it
would
be
really
nice.
If
github
would
let
us
assign
issues
to
folks
who
aren't
actually
in
the
organ
yeah.
B
A
A
Let's
get
to
an
issue,
that's
not
on
the
agenda,
but
should
have
the
label
for
next
time.
This
is
issue
number
107,
the
one
we've
all
been
waiting
for
next
at
consideration,
so
we
wrote
up
a
little
proposal
for
text
back
consideration,
branching
off
of
what
we
talked
about
in
the
collaborator
Summit
a
bit.
The
big
the
big
recommendation
is
Gatsby
Gatsby,
Gatsby
Gatsby,
because
that's
what
everybody
else
is
using.
It's
also
a
very
solid
foundation.
I
have
some
exciting
news
about
this.
A
Actually,
so
we've
got
I
strike,
saying
like
hey,
wanna
dev,
that's
already
full
time
here.
Take
one!
So
that's
really
cool
I
really
want
them
to
just
set
the
foundation,
because
it's
nice,
if
one
person
gets
that
going
so
we're
in
the
next
week,
they're
gonna
have
a
Gatsby
project
up
and
running.
Just
like
a
hollow
one
that
you
know
it's
is
up
and
then
a
github
repo
for
us
to
play
with
I.
B
A
That
makes
the
most
sense,
but
we're
not
taking
anything
for
granted.
He's
gonna
in
the
next
week
he's
gonna,
he's
gonna.
Take
the
week
to
like
evaluate
gatsby
is
a
long
term
solution
which
will
probably
end
up
being
fine
and
and
get
like
the
at
least
a
proposal.
Scaffolding
for
what
the
what
the
site
could
look
like,
just
the
general
skeleton
structure
of
it
and
get
that
up,
and
I
get
hub
repo
where
we
can
all
start
finally
iterating
on
code,
which
I'm
psyched,
for
I
don't
know
about
all
y'all
so
and
especially
now,.
A
Pr
has
landed
like
we
can
started.
Looking
at
what
data
ingestion
looks
like
and
build
process
looks
like,
so
that's
really
cool
yeah
I
really
want
him
to
PR
it
as
a
proposal
and
like
a
here's.
What
the
site
could
look
like
like
it's,
certainly
not
a
mandate,
but
we'll
actually
have
something
to
talk
about
and
look
at
I
think
by
next
meeting,
since
this
is
kind
of
what
he's
what
he
was
tasked
with
this
sprint
to
get
this
the
scaffolding
underway.
A
A
A
Yeah,
we
don't
quite
know
where
the
repo
is
gonna
live.
Yet,
like
that's
that's
another
big
question
like
I.
Would
love
for
I
have
a
fork
of
the
nodejs
website,
redesign
repo,
just
on
my
personal
github?
It
would
be
nifty
if
we
could,
if
we
could
work
in
a
branch
on
that
fork
and
like
once,
the
website
is
ready
to
go.
A
We
just
PR
the
whole
damn
thing
into
the
nodejs
github
repo,
like
we
work
in
a
gutted
branch
of
website,
redesign
of
its
are
the
nodejs
website
repo
and
when
ready,
we
just
PR
the
whole
change
in
pipe
it
in
the
master.
Call
it
a
day.
One
way
we
could
go
about
it.
Another
way
is
make
a
whole
new
repo.
It
would
mean
working
with
build
folk
to
get
it
hooked
into
CI,
properly
and
I
make
sure
it
deploys
properly
down
the
line,
and
so
that
would
be
another
option
is
work
elsewhere.
B
A
I
think
the
build
working
group
will
have
opinions
on
where
it
should
live
and
how
it
should
work
and
also
the
existing
website
website.
Folks,
who
I
think
are,
are
slim
pickins
nowadays,
but
will
I
I'd
be
happy
reaching
out
to
them,
though,
where
where
they
think
we
should
best
be
working
here?
There'd
the
the
current
website
come
on.
A
A
Was
thinking
about
just
working
from
a
like
I
think
working
from
a
branch
off
of
this
thing
would
be
probably
the
easiest
and
hey
we
might
even
just
be
able
to
set
up
another
like
another
deployment
branch
that
just
is
is
running
in
parallel,
so
we
have
old
website
branch,
new
website
branch
yeah,
you
can
see
I
pipelines
and
yeah
I
don't
know
I
can
we
can
reach
out
to
them
and
see
what
what
they
recommend?
The
other.
B
It'd
be
interesting
to
just
pull
the
org
as
the
whole
and
see
if
anyone
would
be
interested
right
now
and
I
read
me:
we
have
the
stages
of
where
we
are
and
we
have
people
signed
up
all
the
way.
Shell
site
development,
like
last
persons
that
who's
PR
got
in
is
young
here
and
right
after
that
we
have
user
testing
deployment
and
maintenance
and
I
feel
the
the
people
who
are
in
deployment
and
maintenance.
A
Also
granted
all
even
with
all
this
talk,
it's
also
real
easy
just
to
set
another
get
remote
and
twitch
the
whole
history
to
wherever
we
needed
to
go
so,
for
the
sake
of
just
getting
getting
rolling.
Will
we
might
want
to
just
start
work
like
I
I
feel
like
these
conversations
will
be
ongoing
for
a
while
and
probably
what
we
decide
now
will
not
be
the
final
solution,
so
it
would
be
best
or
that
I
think
that's
just
to
start
work
in
a
in
a
branch.
I'll
point
them
point
them.
A
The
point
is
to
that
that
location
just
did
just
to
start
either
writing
and
then
we
can
keep
the
the
CI
and
deployment
conversations
ongoing
for
long
term
work,
but
yeah
I'm,
hoping
by
next
meeting,
or
maybe
even
sooner.
If
we
watch
the
github
repo
that
there'll
be
a
like
a
scaffold
gas
food
project
set
up
for
us
to
start
hacking
away
and,
unfortunately,
that
initial
scaffolding
takes
like
woman.
A
You
can't
really
parallel
lives
that
work,
but
once
we
have
the
repo
set
up,
we
can
start
like
actually
giving
it
giving
out
tasks
for
some
of
the
more
interactive
parts
of
the
website
and
some
of
the
larger
desks
which
I'm
psyched
about
totally
yeah.
So
I
have
a
whole
lot
of
tickets
to
make
and
again
a
project
board
so
that
we
can
actually
track
and
parallel
live.
Some
of
this
work.
A
D
A
I
think
the
the
hope
that
came
out
of
the
collaborators
summit
up
in
Vancouver
a
while
back,
was
that
the
site
stay
as
static
as
possible,
so
I.
Ideally,
we
have
no
backing
database.
We
have
no,
you
know
crazy
calls
to
any
back-end.
There
will
be
work
to
stitch
together
the
site
we
want
documentation
to
live
alongside
the
assorted
repos.
A
A
It
would
be
really
nice
if
there
was
just
a
metadata
repository
which
is
kind
of
especially
for
website
redesign,
considered
source
of
truth
for
all
these
different
locations.
They
a
whole
bunch
of
info
floating
around.
So
regardless
of
how
we
actually
start
stitching
together
a
website
or
how
we
actually
like
what
a
build
system,
we
use
it
with
front-end
framework.
We
use
if
any
I
care
about
those
answers.
But
regardless
of
all
that,
we
need
to
know
where
to
get
data
to
actually
show
on
the
site.
A
So
I'm
rather
excited
about
this
project,
and
this
is
I
think
something
that
website
redesign
can
certainly
help
drive.
Since
will
be
the
main
consumers
of
it,
I,
in
addition
to
some
of
the
other
tooling,
that
journey
has
been
been
hacking
away
on
and
it's
free
time,
I
yeah,
so
that's
that's
kind
of
the
current
vision
for
the
site
is
keep
it
as
static
as
possible.
Thank
you.
Scott
yeah
make.
A
A
But
yeah
I
don't
know
what
the
state
of
this
data
repository
ticket
is
I.
Think
tyranny
is
probably
gonna.
Take
the
lead
on
it
since
the
tool
that
he's
working
on
the
node,
good
release,
lines
and
good
first
issue.
Cli
tools
will
also
be
consuming
it,
but
I
know
he
would
probably
love
help
with
us
and
especially
architecting
a
solution.
A
A
A
You
that's
all
I
got
that
is
all
of
our
agenda
items,
including
the
the
added
one.
Do
people
have
more
more
thoughts
or
opinions
or
hopes
or
dreams,
or
things
are,
should
be
chatting
about.
A
I'm
so
excited
for
us
to
actually
have
code
to
work
on
it's
gonna,
be
great.
We've
been
an
administrative
land
for
a
very
long
time,
so
it's
gonna
be
fun
to
see
it
actually
start
getting
built
yeah.
So
for
next
time
Noah
is
the
the
developers
name,
who's
who's,
helping
out
with
the
the
Gatsby
stuff,
so
I'm
gonna
have
him
start
coming
to
these
meetings.