►
From YouTube: Node.js Foundation Website Redesign Initiative Meeting
Description
B
Yeah,
it
says
it
for
me
now:
okay,
well,
welcome
everyone!
Welcome.
People
are
watching
the
very
first
inaugural
noches
foundation
website
redesign
initiative
meeting,
that's
a
very
long
name
on
the
second
of
1st
of
February
I
suppose
before
we
get
started,
Ivana
iMovie,
we
don't
have
too
many
like
participants.
We
can
do
a
quick
roll
call.
B
B
A
C
E
F
B
B
B
Fine,
okay,
now
that
everyone's
introduced,
we
have
a
very
rough
agenda.
Unlike
like
other
meeting
groups,
we
don't
have
fun
linked
to
issues
right
now,
because
we,
this
is
literally
our
first
meeting,
so
I
guess.
Does
anyone
have
anything
they
want
to
discuss
like
they
think
it's
really
important,
and
then
we
should
discuss
first
because
I
just
like
this
is
just
a
loose
agenda
that
I've
pulled
up.
I
can
link
it
in
chat.
You
know
where
it's
like
literally
the
meeting
issue.
Does
anyone
have
anything
they
want
to
prioritize
over?
A
C
B
A
B
A
B
B
Alright,
so
I'm
assuming
someone
session
affords
all
right.
Then,
let's
get
started
with
the
first
agenda
item
the
general
objectives
strategy
going
forward.
I,
don't
quite
remember
who,
like
put
these
points
up,
I
collected
them
from
the
other
shoe
in
in
our
repository
I.
Think
I,
don't
remember
who
made
them
if
anyone
like
wants
to
start
like
the
discussion,
I
guess
feel
free
to
I.
A
Believe
is
partly
me
I'm
just
trying
to
make
sure
we,
yes,
so
I,
just
that
was
kind
of
the
things
I
put
in
that
issue
were
the
the
kind
of
structured
I,
so
we
would
probably
want
take,
and
that
was
just
me
trying
to
help
get
us
started
somehow
and
I.
You
know
I
not
attached
that
I,
don't
think
any
of
us
necessarily
should
be
I.
Just
wanna
make
sure
we
had
some
kind
of
base
to
go
off
of
it,
pick
up
art
and
iterate
on.
B
F
C
C
Yeah
I,
so
the
the
general
just
the
proposal
looks
like
first
I
mean
it's
it's
kind
of
like
any
product
design,
but
and
good
to
have
this
kind
of
find
France,
probably
I
discussions
about
site
structure
first,
which
presumably
would
be
something
that
we
we
kick
off
in
this
meeting
I.
Then
we
could
move
on
to
design
and
talk
about
how
we
want
to
actually
move
forward
with
design.
I
know
there
was
some
discussion
about
actually
hiring
a
designer.
If
we
have
funds
for
that
or
if
it's
gonna
be
a
glute
Lea
volunteer
as
well.
C
You
know
who's
gonna.
What
the
process
would
be
like
go
ahead
and
then
only
then
we
actually
get
to
implementation
and
actually
I
could
call
out
that
in
the
common
trend
for
this
meeting,
there
were
people
it
shouldn't
jump
to
the
implementation
immediately
and
I.
Think
it's
very
important
that
we
don't
talk
tech.
We
don't
talk
implementation
for
the
first
plenty
of
meetings
and
strictly
talk
about
content
and
structure
and
ia
and
experience,
and
you
get
that
hashed
out
in
a
robust
way.
First
yeah.
B
I
B
C
A
B
A
B
A
B
Perfect
yeah:
okay:
let's
go
down
the
whole
agenda
here,
so
the
next
point
would
be
overall
site
structure
which
is
kind
of
patty
face
because
it's
very
general.
It's
a
very
generalized
thing
actually
want
to
redirect
to
to
Gianni's
comment
in
the
the
Rochester
dog
issue,
which
is
a
little
little
better
little
more
verbose,
which
actually
like
lists
as
a
sub
point
here,
assess
current
site
structure,
see
what's
needed
and
what's
not,
which
I
think
is
a
very,
very
practical
thing.
We
can
do.
A
C
I
was
I
was
just
gonna.
Ask
him
that
in
that
vein,
talking
about
current
site,
I
would
I.
You
know
I
I
jumped
into
this
this
community,
just
in
in
the
last
six
months
or
so,
and
so
I
I
know
that
I
at
least
don't
have
a
lot
of
context
about
have
a
site
evolved,
how
we
got
to
where
we
are,
how
the
current
content
I
got
to
where
it
is
and
I'd
love
to
get
from
someone
with
context
a
little
bit
of
history
of
the
evolution
of
the
site.
I
think.
F
F
F
For
the
framework
we're
currently
using
and
I
can
say,
I
already
implemented
a
very
quick
draft.
Do
you
like
it?
He
was
like,
oh
my
god,
so
much
more.
That
I'm
already
started
with
so,
let's
just
use
that
so
that's
basically
how
it
all
started
and
yeah.
So
there
was
never
really
a
a
well-defined
content
structure
for
the
websites.
Just
new
chapters,
a
new
menu
ice
is
popping
up
and
also
with
the
change
of
the
foundation
of
all
the
governance
rules.
Texts
were
just
added
slightly
modified,
so
yeah
we're
missing
the
strategy.
Part
a.
F
D
D
C
E
A
So
I'd
like
to
add
some
context,
just
as
a
user
I
mean
I
was
involved
early
on,
but
I
like
to
add
some
products
is
a
consistent
user
of
the
site
for
information.
If
there's
a
lot
of
barriers-
and
this
is
like
you
know-
it's
just
the
way-
this
is
it's-
we've
consistently
added
to
it.
You
know
what
there's
a
need
for
for
a
new
content.
A
We
add
and
I
been
my
experience
using
it
not
necessary
implementing,
but,
like
you
know,
we
have
about
Docs
to
get
involved
security
and
dues,
even
the
blog
part
of
it,
and
so
you
know
each
of
these
are
they
could
be
structured.
A
bit
like
one
of
the
things
I
used
to
do
is
I
used
to
try
to
find
that
the
pager.
A
You
could
download
the
logo
because
I
used
to
download
it
a
lot
like
more
that
I
should
and
I
ended
up
using
github,
so
that
now,
because
I
actually
can
never
remember
where
the
logo
is
and
like
what
page
it's
on,
whether
it's
some
resources
or
somewhere
else,
it's
a
it
actually
is
on
research.
So
yeah
like
just
finding
really
making
sure
that
we
pull
back
on
what
we
have
and
refine
it
in
a.
H
B
C
Something
that
something
that
might
be
beneficial
for
this
group
to
put
in
place
not
now,
but
in
the
in
the
future.
We
can
open
an
issue
for
it,
just
just
a
chronicle
it,
but
having
a
having
a
holistic
process
for
adding
new
content
to
the
site
as
a
rather
than
having
people
open
a
pull
request,
see
somebody
thinks
it
looks
good
and
presses
a
button.
People
like
actually
have
a
review
of
it.
We'll
sit
down.
F
C
B
So,
just
to
make
sure
that
we
get
through
the
each
and,
let's
I,
don't
know
what
would
be
a
good
place
to
like
start
I.
Think
a
good
place
to
start
is
to
kind
of
try
and
figure
out
a
a
collection
of
what
we
currently
have
on
the
website
and
then,
from
that
point
on
we
can.
We
can.
We
can
say:
okay,
here's
what's
missing,
here's,
what
should
be
added!
Here's
how
we
should
we
organize.
B
E
There's
one
thing
that
I've
noticed
in
the
new
yearÃs
documentation:
it
seems
to
be
especially
wide
in
the
way
that
most
open,
they
still
have
a
few
items
top-level
and
then
you
can
go
deeper
into
them,
but
no
documentation
it
I,
just
many
individual.
It
has
to
have
to
be
sewn
at
the
same
time.
So
I
think
this
is
a
special
service
is
not
normally
found
in
many
other
two
commendations
and
we
have
to
design
a
solution
around
this.
C
A
Will
I
will
say
that
the
API
documentation
that
will
be
a
special
challenge,
because
it's
actually
not
they're
not
driven
by
the
website,
it's
driven
by
the
core
people
or
the
TSC
Jeremy
I,
can
probably
get
more
context
by
that.
But
it's
that's
not
really
scope
or
domain
of
the
website,
so
we'll
probably
have
to
have
discussions
about
that
and
figure
out
where,
where
that
lands
it
out
how
we
can
work
with
that
yeah.
A
H
A
E
C
C
C
I
and
then
make
recommendations
for
the
nodejs
website,
based
on
what
appeared
in
the
industry
standards
and
the
best
side,
the
best
that
I
could
see
from
other
quote
competing
websites,
including
items
for
the
nav
and
then
diving
into
each
of
those
top-level
nav
items
and
talking
about
the
content
for
each
page
and
the
types
of
content.
You
see
in
the
best
presentation
strategies
or
for
each
so
it's
a
rather
than
rather
than
start
out
with
it
kind
of
yeah.
E
B
B
Okay,
let
me
just
kind
of
time
up
this
because
I
think
a
bit
ago
we
were
kind
of
at
the
neck
point
already,
which
is
addressing
content
held
in
separate
repositories
which,
with
the
whole
discussion
about
the
box
there
that's
like
and
then
in
the
main
node
with
per
story.
Yeah.
That's
that's
a
question.
I!
Don't
know
about
that,
but
it's
a
good
wrote
it
up.
F
Okay,
it's
not
just
about
the
API
Doc's,
but
at
the
moment
we
have
stuff
like
the
governance
documentation,
he
assumed
members
all
code
of
conduct.
They
are
all
linked
to
the
main
notice,
repo
or
the
TSE
rape
role
and
I.
Think
that
should
be
a
part
of
the
website.
There's
a
wizard.
The
website
I
want
to
see
the
code
of
conduct,
for
example,
but
directly
and
not
just
go
to
some
random
github
repository
to
a
completely
different
layout
and
I'm
just
presented
a
markdown
file.
A
I
F
B
A
C
C
That's
it's
currently
kind
of
implemented
on
the
current
site.
There's
some
there's
some
like
there's
some
examples
on
there
that
you
can
use
to
get
started
a
little
quickly,
but
it's
definitely
not
the
kind
of
really
ergonomic
guided
tour
that
you
see
on
a
lot
of
modern
developer
websites.
Nowadays,
I
know,
there's
probably
a
lot
of
places
out
there
on
the
internet,
where
people
have
made
no
js'
guided
tours
or
nodejs
tutorials
that
we
might
be
able
to
pull
content
from
like
we.
We
might
not
have
to
write
anything
to
get
that
on
the
website.
C
F
A
I
Want
to
over
complicate
things,
but
what
what
would
happen
if
we
broke
the
docs
out
into
its
own
sort
of
sites,
for
example
like
Doc's,
dot,
no
js'
dog,
and
then
you
could
build
a
site
that
was
getting
started,
for
example,
part
of
the
content,
and
then
you
could
extend
it
with
markdown
files
or
whatever
from
different
repositories.
I.
C
Think,
as
long
as
we
have
a
way
of
making
sure
that
all
these
all
these
sub
sites
are
styled
the
same
like
when
you
click
in
between
them.
You
shouldn't
feel
like
you're,
going
in
between
different
different
repositories.
As
long
as
it
feels
like
a
cohesive
experience
and
I'd
say
that
would
be
a
good
organization
strategy.
I'm.
I
Not
I
don't
really
agree
with
that,
because
I've
seen
a
few
sites
recently
that
have
a
PR
documentation
in
a
different
site
that
looks
completely
different,
but
the
documentation
site
works
as
a
documentation
site
and
their
main
site
works
for
a
different
purpose,
for
example
site,
and
if
you
go
to
their
site,
it
works
as
a
way
to
download
their
products
and
give
information
about
it,
but
their
Doc's
work
as
a
documentation
site
and
this
it
doesn't
look
the
same.
Yeah.
C
What's
the
best
experience
for
people
but
I
yeah,
as
long
as
as
long
as
splitting
up
the
website
doesn't
impact
design,
something
I
always
say
at
work
is
I.
Never
want
technical
implementation
to
be
part
of
the
thought
process
of
a
designer,
so
design
should
be
able
to
do
anything
that
they
want
to
do
and
as
long
as
it
is
technically
feasible,
we
should
be
there
to
support
it.
So,
let's,
let's
let
those
with
the
design
skill
figure
out
what
the
best
experiences
and
then
we
get
to.
We
have
to
make
sure
we
support
it.
F
This
kind
of
links
to
my
third
question:
syncing
with
an
ocean
foundation
website.
That's
exactly
what
you
were
talking
about.
I
briefly
talked
with
Greg
Wallace,
how
we
get
those
two
sides
and
sync
because
they're
using
a
wordpress
setup
now-
and
there
are
at
least
some
plugins
which
allow
you
to
pull
a
theme
from
github.
So
basically,
we
could
share
code
like
header
and
footer,
or
the
general
website
frame.
F
B
A
A
A
Just
this,
you
know
TSC
members
and
I,
don't
even
know
how
often
that's
updated
at
all
so
and
like
the
meetings
meeting
minutes
think
actually
is
a
dead
link.
So
you
know
I
think
we
should
probably
have
a
discussion
with
him
about
the
scope
of
different
parts
and,
like
you
actually
stop
Tracy
Hines
is
still
listed
to
staff
about
the
foundation
on
the
site.
A
C
C
A
C
For
unifying
kind
of
theming
and
branding
I
I,
don't
think
it's
unreasonable
at
all
to
emerge
from
the
design
process
with
a
full
system
or
how
to
how
to
brand
no
js'
related
sites
like
the
official,
no
jest
branding
and
design
system
and
I'd
love
to
see
that
crafted
in
some
charitable
way,
so
that
it
can
actually
be
this.
The
styling
can
be
shared
between
the
two
sites.
Yeah.
B
B
That's
a
good
point:
let's
relate
it
to
this
I
guess:
let's
skip
one
point
that
we're
gonna
like
do
later,
because
I
think
we're
well
within
timeframe:
yeah
considering
you
started
10
minutes
late,
let's
go
over
to
decision
structure,
because
what
I
was
thinking
is
if
we
do
make
such
like
big
decisions,
essentially
like
if
out
of
the
design
process,
there
comes
a
a
full
branding
system,
then
that's
project
white
right.
We
need
to
implement
that
across
more
than
just
the
website,
because
otherwise
that
was
what's
mode
won't
be
the
point.
B
A
H
E
C
A
A
So
it's
generally
consists
of
seeking
as
long
as
there's
jeremiad
much
people
explain
it
better
than
I
can,
but
as
long
as
there's
consensus,
general
consensus
and
no
explicit
objections
or
hard
objections,
you
know
that
things
can
pass
through
when
there
is
a
hard
objection
that
the
objection
needs
to
be
addressed
either
with
the
person
objecting
or
it
needs
to
be
resolved.
Actual
implementation,
whatever
is
being
commented,
needs
to
be
addressed
or
whatever
is
being
proposed.
B
D
B
D
B
A
C
C
C
That
would
be
cool
paths
like
that,
so
there's
no
version
switcher
on
the
on
the
documentation.
That's
that
includes
both
the
any
getting
started.
Documentation
are
there
and
the
API
documentation.
It
would
be
great
to
have
a
better
overview
of
the
release
structure
and
how
it
works.
There's
there's
some
description
there,
but
it's
it's.
It's
very
thing
a
little
hard
to
find
it's.
C
I
think,
since
this
you
spawn
from
the
community
committee
I,
a
robust
community
page
is
also
missing
at
the
moment.
I.
That
would
be
awesome
to
add
and
what
else
did
I
have
I
had
I,
don't
know
if
we
want
to
how
we
want
to
manage
this,
but
actually
it's
so
nerdy,
I,
guess
technically
news.
A
lot
of
a
lot
of
sites
will
have
a
blog.
It
looks
like
under
nodejs.
We
call
it
news,
but
just
how
we
present
that
you
know
how
we
present.
It
is
basically.
B
C
I
make
note
of
in
the
in
the
medium
of
posts
in
that
chat.
I
think
there
needs
to
be
a
strong
distinction
between
community
articles
and
kind
of
fluff
content,
something
that
you
would
want
to
go
share
on
social
media,
something
that
you
would
you
know,
get
subscribe
to
and
get
in
your
inbox
reading
your
free
time.
Let
me
see
distinction
between
that
content
and
I
am
the
content
that
would
go
on
a
website.
Blog
I
believe
that
the
content
that
goes
on
a
especially
a
you
know
a
coding
language.
C
E
E
B
C
C
I
I
B
A
That's
not
a
comment
on
any
specific
thoughts,
I
think
there
we
should
definitely
get
get
those
written
down,
note
them,
but
we
we
definitely
need
to
make
sure
we're
heading
toward.
You
know,
planning
out
what
we're
gonna
be
doing
from
from
the
from
each
part
of
this.
So
you
know
information
architecture,
design
that
implementation
I
want
to
make
a
pass
going
for
it,
and
actually
we
have
something
that
we
can
walk
away
from
this
meeting
with
in
terms
of
this
is
actually
next
does
any
one
kind
of.
I
I
probably
say
that
we
need
some
form
of
documentation
on
what
we
need
in
terms
of
upper-level
content
of
the
website,
like
what
features
should
be
present.
What
should
be
the
main
goals?
What
features
in
the
current
site
achieve
those
main
doors
and
can
be
improved
in
the
future,
but
yeah
I
think
we're
talking
about
two
content
e
right
now.
So.
B
B
B
F
B
Know
so,
I
guess
as
a
sort
of
an
explanation
as
to
I
guess
why
that
didn't
work
before
is
because
I've
never
really
came
from
the
community
itself.
Like
one
time
just
came
from
one
person
like
an
outstanding
who
I
believe
like
coordinated
with
Michael.
If
I
recall
quickly,
I
was
leo
Michael
Michaels
initiative
and
then
I
came
come
from
the
foundation
side,
which
just
I
don't
know,
I
didn't
I.
Wasn't
there
it
sounded
like
it
was
sort
of
a
same
deal.
A
I
B
H
A
H
So
you
could
make
the
request
and
basically
I
can
help
you
get
bids,
but
I
think
the
key
would
be
to
do
a
statement
of
work
and
maybe
some
suggested
vendors,
and
then
we
can
help
you
go
through
that
process
and
select,
because
because
you
got
a,
we
will
end
up
having
to
make
a
agreement
between
the
foundation
and
the
vendor
and
will
have
to
go
through
that
vetting
process.
But,
like
you
like,
the
best
way
to
start
would
be.
H
You
know:
mm-hmm
just
have
an
idea
of
how
much
work,
if
you
know
it'll
be
in
just
a
ballpark,
because
I
gotta
get
a
raise.
That
money
is
honestly
how
it
works
yeah,
but
it's
ideally
and
not,
and
this
I'm
glad
this
is
moving
forward.
So
just
so,
you
know
idea
the
best
thing
to
do
when
you
have
a
community
request
or
is
to
try
and
get
it
in
before
the
end
of
the
year.
So
we
can
budget
for
it
for
the
next
year
and
just.
B
H
B
H
Yeah,
but
if
there's
some
kind
of
like
the
reason
the
foundation
is,
there
is
to
find
the
resources
to
make
sure
that
the
project
is
successful.
So
I
can
do
my
best
to
try
and
give
you
what
you
need,
but
it
is
just
a
matter
of
coming
up
with
that
that
statement
of
work,
so
we
can
get
them
and
you
all
probably
know
better
than
I
who
are
qualified
people
to
help
us
with
this.
I
H
F
E
Crazy
idea,
I,
don't
know
if
it's
even
Miami
or
not,
but
why
not
I
mean
the
community
is
huge
for
not
years
and
there's
many
designers
also.
So
why
not
to
publish
a
competition
contest
or
something
like
that
where
people
from
the
community
can
offer
their
proposal
and
then
there's
some
is
for
prize
or
something
like
that.
D
B
That's
I
think
the
last
kind
of
was
selecting
the.
What
was
it
the
Wheaton
logo
we
design.
Wasn't
that
also
yeah
that
go
well
I,
don't
remember,
I,
don't
I
think
it
would
be
an
entirely
different
thing,
because
it's
on
such
a
massive
scale,
yeah
easier
that
we
centrally
like
make
sure
that
we
get
the
thing
we
want
in
the
website
across
to
the
designer
we
choose
and
I.
E
C
C
Want
to
be
able
to
work
with
that
designer
again
and
if
it
comes
from
a
competition,
we
don't
have
a
guarantee
that
that
we
would
with
a
vetting
process
with
a
vendor
or
with
recruiting
somebody
explicitly
from
the
community,
because
there's
gonna
be
a
lot
of
back
and
forth
here.
Probably
we're
gonna
have
one
iteration
of
content
and
structure
ideas.
Designer
will
come
back
and
say
it
kind
of
works,
but
you
might
want
to
try
this
we'll
come
back
with
other
content
with
that
recommendation.
So
we
want
that.
D
A
D
F
Didn't
really
work
out
with
the
logo.
Back
in
the
days
we
had
quite
mixed
results
and
I
think
most
where
coming
from
developers,
not
even
some
designers
or
somebody,
but
a
little
bit
more
experienced
about
brand
and
design
and
color
and
stuff
like
that
and
for
the
website.
I
think
it's
the
sheer
scale,
because
you
don't
just
need
a
single
screenshot
for
for
the
whole
page,
but
for
the
for
the
download
for
regular
content
pages,
it
can
become
quite
complex.
E
F
I
Just
building
upon
what
Adam
said,
you'll
be
good
as
well.
If
you
work
with
someone
that
you've
chosen
to
work
alongside
them,
while
you're
planning
out
a
site
get
their
input
on
things,
whereas
if
you
just
hand
off
this
huge
document
that
we've
decided
on
and
we've
talked
about,
and
then
just
say
you
know,
go
go,
do
it
and
we'll
choose
who's,
we're
gonna,
choose!
You
know
it's
not
the
best
situation.
If,
for
something
of
this
scale,.
B
C
B
B
F
B
C
Gonna
I'm
gonna
load
the
question
and
then
not
not
want
a
resolution
or
an
answer
on
it,
but
we
we
have
the
we
have
the
Aqua
Jet.
We
we
have
the
opportunity
to
think
about
even
deeper
about
branded
logo,
especially
if
we're
hiring
an
agency
or
hiring
an
expert.
Do
we
want
to
allow-
and
this
is
to
the
test
in
the
waters.
Again,
we
don't
I,
don't
think
we
can
even
get
consensus
on
this
in
a
single
meeting.
C
H
C
E
C
E
H
Way
we
budget
just
is
that
I
know
what
committed
funds
we
have
from
our
membership
sponsors
right
now
and
I'm
always
trying
to
add,
and
this
year
as
I
add
those
those
funds
go
they're
pretty
much.
The
only
place
I
would
add
change.
The
budget
is
adding
to
community
programs.
So
if
a
big
you
know
cloud
provider
sells
books,
maybe
joined
up
or
something
like
that,
maybe
that
would
provide
more
funds
that
would
go
to
community
programs.
That's
how
it
works.
B
C
H
C
Have
depending
on
how
much
conversation
happens
offline,
it
would
be
good
to
have
some
some
details
to
maybe
dig
into
and
and
then
we'll
be
able
to
evaluate
what
state
we're
in
for
wire
framing.
If
we
want
to
do
that,
if
you
want
to
get
a
friend
to
do
that,
you
know
and
then
then
we
can
talk
about
the
design
hand
off,
but
but
we
won't
know
until
we
get
a
feel
for
the
screws
velocity.
So
yeah
I
agree
with
what
Jim
I
also.