►
From YouTube: Node.js Website Redesign
Description
A
C
A
Agenda
items:
we
have
li
agenda
items
right
now.
Let's
dig
into
that
issue.
147
in
no
chance
would
say
we
designed
a
new
home
in
this
issue
Adams
and
between
two
people
make
sense
to
consolidate.
One
series
and
group
is
currently
only
note
development
villages
that
don't
supposed
to
be
thinking.
They
want
to
move
the
government
started,
meeting,
minutes,
administration,
admin
issues
and
etc
over
to
notify
Devon
have
a
single
source
of
truth,
see
the
value
in
59
min.
Only
we
feel
I've
ever
wanted
to
reach
conversation.
A
Yeah,
so
the
mill
you
know
you
hook
on
it,
there
I
tend
to
do
that,
just
especially
since
notified
them
will
eventually
get
merged
into
nodejs,
org
or,
like
there's
gonna,
be
renaming
happening
again.
There
I
think
it
makes
more
sense
for
us
I
presented.
They
make
more
sense
for
us,
yeah
keep
them
for
it,
I'm.
Just
because,
like
it's,
it's
cleaner,
yes,
my
perception,
but.
D
A
A
The
guide
guide,
kind
of
launch
of
the
gift,
a
Deb
and
we're
slowly
iterating
on
that
to
make
it
in
keeping
new
website
kind
of,
hopefully
aligning
with
the
mock-up.
So
we
have
already
and
the
kind
of
guidelines
we
have
already,
but
eventually
that
is
going
to
end
up
as
no
JSON
or
now
there
are
some
interesting
stuff
there
around
like
well,
there's
the
website
working
group.
You
know
how
do
we
figure
that
stuff
out?
A
E
D
Sorry,
no
I
mean
I'm
just
sort
of
off
the
cuff
here,
but
the
first
thing
that
comes
to
mind
being
a
dev
TLD,
is
that
it
would
be
a
cool
place
to
sort
of
consolidate,
front
I,
guess
public
facing
resources
for
how
to
develop
magis
versus
like,
for
you
know,
making
sure
that
everybody
goes
to
our
repositories
and
whatnot
might
be
a
cool
way
to
make
that
soup
rare.
You
know
exciting
and
clean
and
greatly
like
a
great
looking
for
the
public
upfront
overtime.
It's
just
an
idea.
F
Yeah
I
tend
to
agree
with
you,
I
think
if
we
are
going
to
keep
the
node.js
or
dev
domain
and
if
it
is
not
going
to
become
one,
you
know
the
go
to
website
for
the
node.js.
You
know
the
new
website
and
it
makes
a
lot
of
sense
to
keep
the
website
redesign
the
node.js
repositories
you
know
separate,
but
as
Adam
said
I
would
you
know
like
reinforce
it?
We
should
probably
you
know,
connect
the
two.
So
people
could
know
that
this
is
where
the
meetings
are
happening
and
all
that
means
stuff.
F
A
Yeah
so
I
think
the
plan
and
I
guess
this
isn't
solid,
but
I'm
pretty
sure
the
plan
is
to
continue
using
their
server
can
use
no
JSF
as
like
a
temporary
on
for
development
and
then,
like
once
that's
consolidated
and
like
we
launched
the
new
website
at
that
point,
no
gift
that
dev
will
be
like
cool.
What
do
we
do
with
it
now?
I
have
an
idea
that
I'd
be
interested
to
see
implemented.
We
can
talk
about
that
later.
A
That
item,
because
I
didn't
create
an
issue,
so
yeah
I
think
that
I
guess
is
there
a
general
point,
because
one
thing
I
do
think
we
should
say
is
like
if
we
don't
consolidate
them.
What
is
the
alternative
and
I?
Think
you
very
much
state
your
point
having
like
here
are
the
repos
we
use
in
the
the
notice.
A
What's
the
redesign
initiative
and
here
are
and
then
also
and
then
to
the
readme
and
then
also
link
back
to
the
website
redesign
initiative
from
the
readme
they're,
just
a
Devon
and
the
other
refunds
that
we're
working
with.
B
D
It
today
also
I'm
here
in
the
interest
of
sinking
more
and
coming
more
regularly
to
sync
with
internationalizing
things,
and
so
it
would
be
good
to
keep
in
touch
with
the
internationalization
team
over
time
so
that
we
know
you
know
like
what
the
distinctions
are
and
what
we
need
to
target
you
know
and
and
share
through
our
internationalization
platform,
which
is
crowded,
and
things
like
that.
So
I'm
definitely
interested
to
know
what
the
distinctions
are
and
how
to
begin
to
work
with
those.
A
G
A
A
Yeah,
so
they
just
the
relay
didn't
get
in
there
is
because
the
whole
doesn't
a
like
generates
the
list,
the
agenda
once
and
then,
and
then
doesn't
do
it
beyond
that
like
it
was
an
update,
if
there's
more
audits-
and
we
have
to
go,
add
things
and
we
do
that.
Okay,
cool,
so
yeah
I
went
ahead
and
added
that
into
it
yeah
it's
it's,
it's
a
pretty
pretty
simple
tool
that
creates
the
attendance.
A
B
I'm
wondering
there
is,
there
is
a
thing,
I
think
a
separate
initiative
where
people
want
to
run
local
I
forget
what
it's
called
but
I
think
Tracy
opened
an
issue
around
running
local
initiatives
and
a
bunch
of
meetups
raise
their
hand
about
willing
to
being
willing
to
host
them.
Does
anyone?
Can
anyone
recall
where
that
would
be
I
believe
it
might
be
in
calm,
calm,
I'm,
gonna,
go
look
for
that
issue.
The.
A
B
It's
that
just
seemed
like
if
that
is
a
line
that
seemed
like
the
best
possible
use
of
our
time,
is
that
we
merge
it
with
that,
because
some
meetups
are
already
willing
to
host,
but
their
goals
might
have
been
slightly
different.
Can
we
circle
back
around
to
this
later
in
the
meeting?
I
will
try
and
find
that
issue.
A
A
A
F
Think
we
can
have
we
sort
of
have
an
agreement
here
about
you
know
so
I'm
sort
of
setting
a
minimum.
You
know,
let's
say
three
PR
for
documentation
or
for
code.
Do
you
know
sure
that
your
interest
rate
and
then
later
on,
you
know
defer
into
the
voting
process
like
if
everyone,
if
no
one,
has
an
objection,
then
moving
on
with
adding
the
team
member.
A
F
A
I
I
generally
try
to
go
down
the
route
of
like
either
so
you
know
when
I
joined
the
website,
he
was
on
the
fire
and
was
like
working
at
that's.
How
I
got
involved
with
node
I
did
a
bunch
of
small
changes
that
were
like
not
super
maximal
but
I,
just
vibrator,
because
I
think
you
can
do
both
like
one
major
change:
that's
dramatically,
impactful
and
or
a
bunch
of
tiny
changes
that
are
like
reducing
debt
by
thousand
cuts,
so
I
agree.
A
Do
we
want
to
go
down
the
path
of
either
self
self
nomination
or
the
current
member
nomination
like
having
both
you
know
asking
the
to
be
added
or
self
nominate,
it's
like
self
nominating
and
asking
to
be
added
to
the
group
or
being
nominated
by
someone
who's,
currently
a
member
and
having
both
of
those
as
an
option
simultaneously.
And
then
you
can
still
do
that.
You
know
loading
basically
consensus
seeking
process
that
we
we
use
a
node
where
you're
you
know,
you're
gonna
accept
someone.
If
there's
no
objections,
then
you
can
get
that
through.
F
Think
the
process
of
self
nominating
is
sort
of
the
Woodman
it
actually
inspires.
Other
people
to
you
know
contribute
more
as
well
as
if
we
can
have
sort
of
a
general
guideline
around
yeah.
Maybe
you
have
to
contribute
a
little
bit
and
then
you
can
go
ahead
and
self
nominate
yourself
and
let
the
team
decide
on
it.
Then
it
sort
of
gives
them.
F
You
know
the
ability
to
show
off,
but
they
have
done,
but
they
have
contributed
instead
of
us,
or
you
know
the
members
already
trying
to
judge
on
basis
of
what
they
have
done
and
the
other
way
around
it
is.
If
someone
is
already
contributing
in
not
trying
not,
you
know
self
nominating
themselves,
then
we
can
just
go
ahead
and
ask
and
whatnot
right.
G
A
G
A
G
A
A
A
G
G
F
G
Pause
them
with
that
way,
we
would
solve
the
issue
that
you
can
sort
them.
However,
you
want
to,
we
can
add
them
in
the
middle
of
something
and
also
add
links.
We
can
also
go
ahead
and
introduce
while
a
couple
of
levels-
let's
say
I
mean
right
now,
with
the
logic
we
use
the
column
and
do
a
second
or
third
dimension
of
the
of
the
many
artists.
F
You
know
personally
experiences
that
the
CML
file
always
ends
up
being
a
big
trouble
because
of
you,
no
one
would
add
one
less
face
in
then,
or
everyone
is
finding
that
one
thing
so
maybe
we
have,
we
can
have
a
bit
more
of
us.
You
know
strict
structure,
all
right
of
JSON
file
or
maybe
a
JavaScript
object
if
that
goes
well,
but
definitely
moving
into
that.
This
direction
with
a
better
format,
would
be
a
go
for
me.
G
Object
object
notation,
so
we
all
know
as
flexible
as
jung-ho,
but
the
question
is
to
be
wanna.
Have
that
flexibility?
I
don't
know
yet
it's
just
I
was
more
with
Victorian
today,
but
they
can
come.
What
about
one
state?
We
could
hit
bit
young
for
a
bit
object.
Notation,
I,
don't
know,
maybe
that
we
need
to
change
it.
So
was
this
proposal
tea?
Well
kick
out
this
discussion.
F
A
The
thing
I
would
say
here
is
like
it
would
be
really
nice
if
we
didn't
have
to
like
I
guess.
One
of
the
things
that
I
try
to
do
is
reduce
the
maintenance
burden
at
all
costs
and
so
like
not
having
to
do
something
manually
he's
good.
In
my
previous
role,
we
had
to
maintain
the
basically
the
same
side
bar
very
manually
by
a
very
old
static
site
generator
and
like
that
was
a
real
big
pain.
A
B
I'm
glad
this
discussion
was
started,
so
thank
you
for
opening
the
issue.
Llorona
I
noticed
the
the
main
problem
would
be
if
you,
if
you're,
adding
a
new
article,
you
have
this
massive
problem
of
renaming
a
bunch
of
files
or
directories,
and
it
seems
like
one
big
issue
with
maintaining
the
Yama
file
is
the
possibility
of
making
mistakes.
I'm
wondering
if
that
is
like
maintaining
the
Yama
file,
can
can
a
be
less
tedious
or
less
prone
to
mistakes
by
our
review
process.
B
Also,
editing
yamo
files
might
be
a
very
low
barrier
for
entry
for
people
who
want
to
get
started
on
this
project
so
as
opposed
to
it,
it
seems
to
me
that
editing,
a
llamó
file
might
not
be
too
far
off
from
editing
a
documentation
typo,
which
typically
tends
to
be
how
people
get
started
in
projects
like
this,
so
maybe
maybe
having
that
well
code,
encode,
tedious
or
possibly
like
time.
Intensive
work
might
be
good
for
people
to
get
their
feet.
Wet
I.
F
Tend
to
think
that
we,
you
know,
files
often
lead
to
many
many
issues
because
of
the
you
know,
sort
of
flexible
formatting
they
have,
but
if
I
want
to
move
towards,
you
know
having
to
automate
it
there's.
Definitely
we
can
you
know.
For
example,
we
can
introduce
two
factors
when
early
on
a
priority
vector
that
you
could
have
you
know
we
could
just
use
graph
fuel
to
generate
this
documentation.
F
Navigation,
like
we
are
doing
right
now,
based
on
that
particular
priority.
The
way
that
we
have
in
later
on,
if
you
want
to
add
different
links
which
are
not
part
of
this,
you
know
particular
documentation
or
something
else
we
could
introduce.
You
know
sort
of
a
you
know,
file
that
has
no
sort
of
heart,
another,
let's
say
parameter
that
has
published
none,
but
it
has
a
priority
of
that
it.
It
can
be
in
the
menu.
You
know,
sort
of
an
external
link
it
it.
It
will.
Save
us
from
you
know,
having
two
men
really
maintain.
G
That
was
exactly
actually
point.
Why
I
suggest
that,
because,
as
you
also
mentioned
for
everything,
unless
we
need
to
introduce
something
or
touch
the
code
and
see
I
mean
if
we
have
once
two
logic
implemented
in
our
components,
we
don't
need
to
touch
the
code
at
all
actually,
but
it
doesn't
matter
whatever
you
want
to
date.
G
With
the
navigation
I
mean
you
can
introduce
easily
more
dimensions
and
you
can
add
any
link
to
know
about
pass
or
whatever,
and
that
was
actually
my
point
why
I
wanted
to
go
to
you
know
just
or
just
maintain
them
manually.
Of
course
it
brings
the
overhead,
as
I
mentioned
in
at
the
end
of
the
document,
that
someone
needs
to
write
them.
It
is
just
like
that,
I
don't
know,
I,
don't
think
said
that
I
mean
ultimately
do
it
automatically
will
be,
of
course,
really
lovely
yummy.
F
Can
you
reiterate
on
how
automating
it
through
gets
be
graphical
would
not
be
effective?
You
know
understand
which
they
show
their
I.
Think
I
you
come
again.
Can
you
reiterate
on
how
having
to
automate
it
through
gates,
V
and
graph
QL
by
you
know
the
post
matter?
Why
would
not?
Why
would
that
not
be
effective
or
how
come
it
would
be
less
of
a
thing
then,
as
compared
to
writing
that
you
file
manually
way.
Would
it
break
what.
A
So
I
think
what
liver
Nova's
getting
it
is
like
that
is
it's
nice
to
automate
it,
but
there's
like
certain
things
that,
if
you're
doing
it
in
that
manner,
you
can't
necessarily
do,
or
at
least
as
far
as
I
know
as
far
as
I
understand
about
graph
QL
and
gatsby,
like
inserting
a
arbitrary
link,
there
might
be
difficult.
I
could
be
wrong
certain,
but
you.
F
Can
actually
build,
you
can
actually
grow
or
that
post
matter
to
have
another,
because
I
have
a
project
where
multiple
lengths,
you
know
re
director
to
one
single
document,
so
what
we
have
as
a
bunch
of
different
slabs
that
are
only
related
to
that
document.
So,
in
a
similar
way,
what
we
have
is
a
display:none
property
for.
In
the
you
know,
a
post
metal.
We
would
just
want
to
add
an
external
link,
but
it
has
a
display:none.
F
It
is
not
a
document
and
in
graph
QL
query
we
can
easily,
you
know,
filter
it
out
where
in
a
post
matter
or
document
that
display:none
does
not
get
displayed,
but
it
slug
or
its
menu
item
could
be
inside
the
navigation.
So
that
is
how
we
do
it,
but
at
the
end
of
the
day,
everything
is
automated
and
has
priority.
So
we
can
easily
move.
You
know
the
navigation
up
and
down
so.
F
For
example,
there's
this
entire
documentation,
which
is
entire
local,
but
now
there
is
your
link
towards
your
social
media,
and
you
don't
want
to
publish
in
our
document
on
that.
So
there's
this
just
one.
You
know
post
meta
data
screen
done
parameter
and
in
graph
here
we
have
filtered
out
that
parameter
when
we
are
printing
the
documentation.
F
So
nothing
happens
for
that
document
in
just
for
adding,
because
at
the
end
of
the
day,
what
happens
is
the
external
links
are
always
like
10%
of
the
internal
links
so
because
of
only
those
impression
link
having
to
manually
maintain
the
entire
navigation
is
a
bit
much
bit
much.
So
what
we
do
is
we
maintain
those
10%
external
links
and
sort
of
documents,
sort
of
like
documentation
documents,
but
they
have
a
display:none
attribute,
so
they
don't
get
published
as
documents
only
their
parameter
for
slugs
or
in
this
case.
F
G
I
mean
at
this
point
for
every
font
message
at
your
institution,
so
you
have
markdown
files.
You
need
to
implement
illogic
for
it
and
also
for
every
single
thing.
You
need
to
introduce
new
tags,
which
leads
to
the
problem
that
you
need
to
talk
to
your
logic.
Again.
Imagine
you
want
to
introduce
the
other
new
dimension
of
the
site,
navigation.
You
need
to
introduce
a
tag
which
cause
I,
don't
know
just
turn
navigation
or
navigation
section
over
and
then
you
need
to
talk
to
your
logic,
change.
G
It
might
get
comfortable
with
that
and
if
you
want
to
introduce
iden
a
couple
months,
a
couple
months
later,
I
don't
know
food
I
mention
you
have
to
do
the
same
again,
which
that's
the
issue
you
wouldn't
have
in
which
young
files,
if
you
have
once
the
logic
implemented
because
the
structure
doesn't
change
but
with
different
meta
tags.
You
change
all
the
time.
Your
structure,
which
leads
to
the
problem.
You
need
to
change
all
the
time.
Your
logic.
That
was
actually
my
intentional
point
where
I
want
to
avoid.
A
G
Honestly,
I
will
just
keep
everything
as
it
is
before
we
invest
time
and
effort,
because
we
don't
know
where
we
gonna,
let
in
I
don't
know
half
year.
So
I'll
wait
a
bit
since
we
got
the
happy
information
from
Adams
died
that
on
with
implementation
of
another
pages,
I
will
just
wait
a
bit
and
see
how
things
will
change
and
then,
while,
depending
on
the
situation,
we
can
go
for
something
or
we
could
maybe
just
I,
don't
know
just
something
completely
different.
Nobody
knows
yeah.
F
I
agree
with
that,
but
those
divided
friends
are
still
being
made
and
maybe
we
could
have
a
you
know,
general
solution
for
the
entire
navigation
of
the
site,
and
then
we
would
have
more
insight
into
if
we
are
going
to
go
for
level
leaves
or
D,
but
not
so
keeping
it
right.
Now,
where
it
is,
makes
things
easier?
Not
you
don't
have
to
you
know
you
just
have
to
add
another
talk
of
Indian.
It
will
be
automatically
intruder
and
you
know
whatever
you
added
it
instead
of
having
too
many.
F
F
A
Subdomains
as
long
as
they
conform
to
our
code
of
conduct
or
a
code
of
conduct
that
we
would
enforce
for
that,
but
also
there's
an
interesting
interplay
here
with
glitch
where,
if
people
want
to
work
on,
you
know
the
tutorials,
they
could
see
it
live
on
the
Internet,
so
the
tutorials
that
are
being
embedded
in
the
site.
Now
they
could
see
a
live
on
the
Internet
at
some
subdomain
on
something,
no
Jayadev.
So
that's
you
know
one
thing,
and
then
they
could
also
deploy
other
glitch
apps
to
that.
A
F
A
F
If
we,
we
can
I
think
making
something
like
this.
Not
all
where
we
could,
you
know
give
the
subdomain
to
particular
developers
would
be
interesting
for
an
order
te
domain,
but
with
node.js
or
dev
I,
like
the
idea
of
having
you
know,
sort
of
a
pre-configured
pledge
block
or
something
like
that.
You
could
just
go
and
you
know
have
sort
of
a
node.js
development
platform.
But
if
it's
a
little
bit
more
option,
you
know
you
could
try
a
different
version
of
node.js
with
bit
more
than
but
just
glitch
offers
or
having
a
pre-configured
one.
Maybe.
A
Yeah
I
will
create
an
issue
to
kind
of
discuss
the
future
of
notice.
That
I'll
do
that
now.
You
know
once
we're
done
with
the
meeting
and
I
think
I
think
that's
a
very
good
idea,
as
well
as
like
nodejs
tied
that
slash
playground,
slash
whatever
there's.
You
know
a
lot
of
things
you
could
do
with
that.
It's
a
good
idea
and
I
like
that
yeah.
So
you
know
there's
definitely
a
lot
of
things
we
can
and
probably
should
do
with
that.
So
I
think
it's
good
to
get
that
discussion
going
now.
It.
D
Seems
like
syncing
that,
with
you
know,
really
great
public
facing
resources
for
people
to
get
started
with
you
know
whatever
they
want
to
with
note
would
be
an
awesome
thing
too.
So,
like
some
kind
of
landing
for
people
to
get
into
node.js
development,
and
then
you
know,
on
top
of
that
springing
from
there
into
you,
know
publishing
their
apps
and
things
might
be
hope,
you're,
sure,
okay,.
B
That
I
think
we
can
probably
in
the
meeting
a
few
minutes
really
unless
anyone
else
has
anything
they'd
like
to
talk
about
or
share
related
to
the
dock
survey
issue.
61
user
feedback,
yes
survey,
I
found
the
repo
I
mean
I,
found
the
issue
that
we
were
talking
about.
It's
in
user
feedback,
its
issue,
115
and
I
believe
that
was
what
Aguirre
was
talking
about
when
he
said
that
they
plan
creating
a
user
group
Meetup.
A
B
D
Think
where
we
need
to
do
another
sort
of
big
push
to
get
people
involved
and
kind
of
read,
regroup
and
regather
the
internationalization
initiative
and
get
people
on
a
regular
working
group
meeting
cycle
and
that
sort
of
thing
so
I
think
it's
it's
mostly
just
like
getting
getting
us
organized
and
sinking
sinking
up
with
this
group
and
making
sure
that
we're
moving
towards
you
know
providing
an
internationalized
Docs,
whether
it's
markdown
or
you
know
what
not
I
think
that's
what
we
need
to
figure
out
now.
I
think.
F
E
F
Good
thing
to
look
at
you
know
for
sort
of
inspiration
in
you
know,
making
champions
of
particularly
languages
and
assigning
particular
documents
to
a
particular
people.
That's
what
you
don't
make
sense,
but
definitely
create
an
issue
for
that
and
we
could
discuss
it
and
for
the
meetings
as
well.
Yeah.
D
D
Thinking
about
and
trying
to
create
a
documentation
that
has
no
upstream
or
downstream
and
I
think
we
were
on
we,
we
have
been
on
track
for
that.
You
know.
As
far
as
the
last
time
there
was
a
push
in
the
internationalisation,
repo,
so
I
think
like
alleviating
upstream
and
downstream
and
finding
champions
and
getting
the
word
out
and
doing
all
that
kind
of
stuff
is
will
be
great.
A
With
anything
else,
it's
like
the
seventh
time,
I've
asked
and
I
like
that.
We
keep
having
other
things
good,
okay,
cool
thanks.
Everyone
for
coming
today
see
you
again
in
two
weeks,
I'm
gonna
be
trying
to
make
these
meetings
more
often,
I
know
I've
been
kind
of
tardy
a
bit
recently.
So
looking
forward
to
seeing
seeing
you
all
again
et.