►
From YouTube: Node.js Website Redesign Initiative Meeting
Description
B
Hello,
everybody
and
welcome
to
another
episode
of
nodejs
website
redesign
working
group.
Let's
do
quick
introductions,
the
people
called
in
here
or
anybody
who's
streaming
or
watching
this
at
a
future
date.
I'm
Adam,
koa
co-leader
of
the
working
group
with
Vanille,
who,
unfortunately
can't
make
it
to
this
meeting
at
a
conflict
web
developer
over
at
LinkedIn
journey.
A
C
B
Great
yeah,
so
I
I
kind
of
envision.
This
meetings
as
more
of
a
recap,
meeting
of
what's
been
discussed
over
the
past
couple
weeks.
Actually
a
post
collab
summit
since
we
haven't
had
a
proper
streaming
meeting
since
since
then,
but
there
are
three
things
on
the
agenda
for
today:
we'll
just
go
down
the
list
and
see
what
the
conversation
takes
us.
The
first
thing
on
the
list
is
again
that
same
old,
extended,
color
palette
ticket,
which
is
popping
up
and
every
meeting
because
I'm
gonna
use
this
to
remove
the
CC
agenda
label.
B
I'm
gonna
do
right.
Now
there
we
go,
but
I
did
actually
intentionally
leave
this
on
to
the
redesign
work
agenda,
because
I
just
want
to
use
it
as
kind
of
a
jumping-off
points.
You
don't
have
a
dedicated
ticket
for
it.
Just
to
talk
about
the
state
of
the
design
volunteer
that
we're
getting
from
or
I
guess,
donation
time,
donation
that
we're
getting
from
stripe.
B
We
have
been
chatting
over
email
about
when
they
get
this
started
and
it
looks
like
they're
they're
finalizing
a
couple
things
on
their
end
and
then
sometime,
hopefully
I'll.
Hopefully,
by
end
of
this
week,
if
not
early
next
week,
we're
gonna
be
getting
like
a
first
sit-down
chat
and
say
hey
to
the
designer
and
meet
me:
do
they
are
just
over
Skype
and
so
over
the
next
few
months,
we'll
actually
have
a
dedicated
design
resource
to
help
us
get
our
wireframes
to
a
higher
fidelity
place
and
flesh
out
this
design
system.
B
A
A
general
question
on
that,
once
we
do
have
the
dedicated
design
resource,
what
will
other
kind
of
money?
What's
your
kind
of
thoughts
around
what
other
contributors
will
be
able
to
do
in
the
initiative
and
I
I?
Don't
have
an
expectation
around
that
I'm
just
curious.
What
what
if
anything,
other
people
can
do,
like
you
know,
designed
by
committee,
doesn't
usually
end
up
working
very
well.
B
B
So
what
I?
What
I'm
kind
of
envisioning
is
because
design
by
committee
doesn't
doesn't
work?
Well,
we're
gonna
go
let
the
designer
do
what
designers
do
best,
which
is
push
pixels
around
and
make
this
thing
look
gorgeous
and
get
a
couple
proposals
together
and
we'll
have
the
discussions
on
github
for
once,
there
are
high
fidelity
mock
out
there.
In
the
meantime,
it's
actually
a
great
segue
thing.
B
Keep
turning
to
the
ticket
that
Manuel,
actually
just
posted
eight
hours
ago,
finally
got
the
information
from
our
collab
session
in
person,
collaboration
session
synthesized
and
up
in
a
github
issue.
It's
issue
number
60
in
the
website,
redesign
org.
So
while
we're
working
on
high
fidelity
mocks
and
getting
look-and-feel
working
well,
which
is
like
a
one
or
two
person
job
just
by
nature
of
design,
there's
nothing
blocking
us
from
working
on
content
and
that's
actually
I
think
what
the
community's
most
well
poised
to
to
contribute
back
at
the
moment.
B
B
A
Kind
of
one
I
didn't
realize
it
was
self-serving.
Till
I
started
talking
about
it
oneself
and
of
thing
out
of
that.
The
question
I
had
is
you
know
and
very
much
this
while
I
was
in
Germany
I
had
the
opportunity
go,
spend
some
time
with
some
of
the
content
for
people
there
devil
team
and
they
I
had
talked
to
them
like
hey,
we're
interested
in
possibly
using
adept
full
because
I
know
miles
had
mentioned
it,
and
you
know
and
notice.
A
A
A
B
A
B
A
That's
good
yeah
so,
and
you
know
with
that,
just
in
my
personal
experience
with
contempo
or
a
headless
CMS
in
general,
they're,
not
simple
to
get
used
to
like
they're
a
very
different
concept
than
a
normal
CMS,
because
you
have
to
build
all
your
content
models
yourself.
I've
been
doing
that
building
content
models
for
two
years
now
or
like
a
year
and
a
half
so
I'm
happy
to
come
in
and
help
actually
build
out
the
content
models
and
dude.
So
that
work,
because
it's
not
easy
for
people
who
aren't
familiar
so.
B
Yeah
that
would
be.
That
would
be
great.
We
should
also
probably
have
a
larger
conversation
with
foundation.
Folks
or
like
you,
I
do
a
at
least
an
audit
of
the
foundation
site
and
see
if
and
how
we
can
look
that
in
because
I
there
was
a
lot
of
interest
in
consolidating
the
two.
Yes,
especially
CMS,
so
yeah.
D
B
B
About
site,
it's
sweet
that
sounds
good,
so
a
Gary
we're
just
doing
a
quick
recap.
This
would
probably
be
a
pretty
quick
meeting.
We
said
at
the
beginning,
because
we're
just
kind
of
recapping
work-
that's
been
done
over
the
past
two
weeks
since
collab
summit
I
and
then
just
keeping
on
keeping
on
with
the
with
the
work
that
needs
to
get
done.
So
we
talked
about
the
designer
coming
on
board
I'm
from
stripe
fairly
soon
we're
closing
loop
on
that
with
with
run
kit.
B
Folks
and
they'll
start
joining
this
meeting,
probably
early
July,
once
they
actually
got
on
boarded
and
we
get
that
started
and
then,
while
design
work
is
happening,
the
rest
of
the
community
can
can
keep
contributing
back
by
drafting
content.
We
have
issue
number
60
I,
believe
it
was
that
many
I'll,
just
posted,
which
is
all
the
digitized
version
of
our
exercise
from
the
collab
summit,
and
so
every
every
list
item
here
is
gonna,
probably
need
a
fully
fleshed
out
documentation
page
for
how
it
all
works.
For
this,
the
new
getting
started
content
where
we're
drafting.
D
B
Yeah,
so
this
would
be
like
a
proper,
getting
started
flow
for
understanding
core
concepts,
and
how
do
you
start
writing
in
those
application?
What
how
do
I
make
a
simple
server,
what
our
modules?
So
it's
it's
a
higher
level,
more
user-friendly
approach
to
to
getting
on
board
and
getting
people
started
up
with
node
and
moving
on
to
more
advanced
topics
like
symbols,
purity
concerns-
or
you
know,
multi-threaded
concerns
or
I,
so
higher
level
than
the
the
raw
API
documentation.
B
D
Actual
content
that
relates
wildly
to
the
projects
not
just
for
a
price
because
most
of
the
contents
we
have
on
YouTube
are
strictly
on
writing.
No
J's
API
is
and
no
much
content
on
a
course
of
the
no
J's
actually
used
for
so
I.
Don't
know
having
like
a
content.
Creator
not
like
working
group,
was
a
team
so
we're
responsible
for
creating
multiple
contents
for
the
training
use
cases
there's
associated
with
no
teachers.
So.
A
I
think
that's
a
good
idea.
That
said
one
of
the
things
that
I've
learned
over
working
with
no
jsni
ojas
over
the
past
three
years
is
creating
too
much
structure.
Early,
prevents
natural
structure
from
growing,
and
so
would
I
would
I
would
suggest
is
having
that
work
done,
and
this
is
funny
because
this
is
very
much
mirroring
how
I
originally
joined.
I
oj
s
having
that
work
done
in
the
scope
that
it's
currently
being
proposed.
A
So
that's
the
website
redesign
and
then
that
can
theoretically
you
know
if
the
need
is
there,
be
split
out
into
a
different
initiative.
If
enough
work
is
done,
but
you
do
creating
too
much
structure
around
something
that
already
has
structure.
It
creates
a
lot
of
churn
and
actually
decreases
contributions
that
then
increase
in
contributions,
not.
D
A
Website
right
now
and
leaving
it
there
and
letting
it
kind
of
grow,
naturally
something
else.
That's
generally
a
good
approach
and
like
that's
exactly
how
the
evangelism
working
group
had
got
gotten
started
originally,
because
there
was
too
much
content
being
created
too
much
interest
in
creating
content
in
the
website
repo,
which
is,
it
was
mostly
me
having
too
much
interested
yes.
So.
B
My
my
my
thought
and
kind
of
expectation
for
how
it's
gonna
evolve
like
that,
is
it's
doing
exactly
what
you
were
saying.
Will
the
website
redesign
initiative
is
an
initiative.
It's
a
temporary
thing
like
once.
The
redesign
is
over
it'll,
go
into
maintenance
mode
and
probably
go
back
to
the
main
nodejs
website.
Repo
most
likely
like
that
will
become.
B
It
will
just
become
the
new
website
and
maintenance
will
get
kicked
back
over
there
and
I
expect
documentation
and
content
creation
to
kind
of
evolve
into
its
own
group,
but
I
I
think
right
now,
the
web,
the
redesign
and
the
content
creation
are
so
intertwined
that
it
would
be
hard
to
separate
to
a
its
own
standalone
group
right
now
so
waiting
for
that
good
point
to
spin
it
off
into
its
own
group.
After
it's
been,
you
know,
it's
kind
of
found
itself
as
part
of
this.
A
B
On
on
that
note
something
that
we
need
right
now,
every
single,
an
issue
number
60
in
website
redesign,
every
single
issue
in
this
list
or
every
single
item
in
this
list-
is
its
own
documentation,
page
or
proposed
documentation,
page
and,
like
I,
say
below
it's.
It's
a
no
way
exhaustive
and
there's
probably
stuff
on
there
that
shouldn't
be
on
there,
but
each
one
of
these
will
need
their
own
issue
so
that
we
can
actually
have
a
dedicated
conversation
around
it.
B
I
and
after
right
after
this
meeting,
I'm
gonna
get
a
folder
committed
just
so
that
we
have
a
place
to
start
peeing
markdown
files
with
like
rough
drafts
of
each
of
each
page.
So
people
can
start
contributing
content
right
now
and
lpr
it
right
into
the
website.
Redesign
repo.
For
now,
we've
been
talking
with
core
or
not
core,
sorry
CSC
and
the
technical
folks
about
this
living
directly
in
the
node.js
repo
proper,
which
I
think
is
the
right
place.
It's
the
right
place
for
it
to
live.
It
simplifies
a
lot
of
stuff.
In
our
end,.
A
B
B
It
simplifies
so
much,
but
for
now,
when
we're
iterating
really
quickly,
so
we
don't
absolutely
flood
the
main
repo
with
PRS
for
non
code
content,
I'd,
love
us
to
iterate
in
the
web,
design,
website,
redesign
repo
and
then
do
a
big
old
dump
once
we
feel
like
it's
ready
into
the
main,
the
main
repo
and
again
only
after
we
have
ingestion
figured
out,
which
is
a
whole
other,
which
will
be
a
little
while
from
now
yeah,
so
we'll
we'll
get
that
little
bit
of
structure
set
up.
So
we
have
a.