►
From YouTube: Node.js Website Redesign Initiative Meeting
Description
A
And
for
life,
okay,
so
six
everyone
for
coming
to
today's
website
redesign
group
meeting
initiative
meeting
so
I
think
we
can
hop
right
into
it.
So
well
we
have
a
few
items
on
the
agenda.
Let
me
get.
Let
me
backtrack,
let's
go
through
who's
here,
so
hi,
I'm,
37,
developer
advocate
at
node
source
and
chairperson
of
the
community
Cuba
D,
and
also
contributing
to
the
website
redesign
initiative.
A
D
A
A
A
Don't
think
we
should
necessarily
continue
to
let
getting
started
at
the
community
page
block
us,
because
it
has
been
kind
of
a
blocker
for
us
that
we've
been
working
on
over
the
past
three
or
four
meetings
and
at
this
point,
I
I
think
we've
kind
of
figured
out
it's
opinionated
enough,
and
there
are
enough
state
stakeholders
that
it
will
be
kind
of
living
and
evolve.
Naturally,
and
so
we
can
kind
of
get
a
base
down
and
then
let
it
kind
of
develop
from
there.
B
I
like
to
say
that,
even
though
we
shouldn't
let
it
block
I,
think
I
think
we
should
move
on
to
more
details
of
mock-ups.
Well,
we
might
want
the
site
to
be,
but
I'd
still
love
to
get
that
extra
either.
That
extra
meeting
on
the
books
to
plan
out
that
foundation
I
have
active
work
being
pushed
towards
getting
that
first
iteration
out
I
and
also
want
the
float.
The
idea
of
doing
some
session
at
the
collaborator
summit
or
like
an.
B
A
A
C
B
B
D
D
Having
read
some
of
the
issue
and
stuff,
our
team
kind
of
took
the
time
to
put
together
kind
of
like
a
little
prototype
website,
for
how
you
could
use
one
can
step
in
one
of
the
things
is
that
in
there
it's
kind
of
a
first
shot
at
a
getting
started.
I
can
just
paste
the
link
into
the
chat,
and
it
kind
of
has
like
a
bunch
of
different
prototypes
and
stuff.
Oh
that's.
B
A
A
D
So
we
kind
of
broke
it
up
into
two
main
things.
One
of
them
is
kind
of
like
how
to
integrate
kind
of
just
runnable
code
throughout
kind
of
the
entire
documentation
experience
and
that's
the
first
link
and
if
you
scroll
down
to
the
third
paragraph,
there's
a
specific
take
on
like
a
getting
started
approach
and
that's
the
second
awesome.
D
A
A
D
That's
kind
of
the
idea:
if
so
you
kind
of
read
the
little
blurb
well,
we've
actually
done
is
take
the
the
exact
markdown
piles
that
generate
the
current
documentation
and
just
tried
to
see
how
far
we
could
get
using
just
that
without
like
rethinking
it
or
anything
and
kind
of
what
we
found
is
that
it
kind
of
already
is
very
example.
Driven
and
all
we've
tried
to
do
is
kind
of
take
this
like
literate
programming
approach,
we're
like
you're
reading
about
it
and
you're
getting
to
play
around
with
it
on
the
right
yeah.
This.
B
D
D
D
A
D
It's
funny
like
when
we
first
started
working
on
wrong
kid.
We
actually
started
with
kind
of
a
version
of
this
site,
which
is
just
because
at
the
time
we
really
needed,
like
sites
that
could
like
have
hundreds
of
different
embeds
in
them
just
for
like
performance,
testing
and
stuff.
So
we've
actually
been
thinking
about
this
exact
problem
for
a
long
time.
D
A
Really
cool
what
question
I
have
is
run
kit,
like
only
for
applications
like.
Could
we
because
I
know
we
have
a
few
people
who
are
invested
in
doing
like
docker
tutorials
on
the
site?
Would
we
be
able
to
do
a
docker
image
as
well?
And
this
is
just
me
reaching
like
this?
Isn't
a
requirement
I'm
just
curious,
yeah.
D
So,
if
you
wanted,
we
could
give
you
a
link
that
actually
gave
you
everything,
bundled
into
one
container,
that,
like
you,
could
just
pull
off
a
duct,
docker
hub
or
whatever
so
I.
Guess
yes,
and
then
there'd
be
some
discussion
as
to
like
how
exactly
you'd
want
that,
but
it
should
be
totally
feasible.
Okay,.
A
B
Yeah,
so
the
one
other
use
case
that
I
haven't
I,
haven't
yet
seen
out
of
run
kit
and
I'd
love
to
love
to
know
how
it
could
be
supported
for
the
getting
started
page.
We're
probably
gonna
want
to
talk
about.
You
know
installing
your
own
dependencies
and
modifying
your
packet
rates
on
and
importing
other
files
stuff
that
is
seen
from
Monken
so
far
has
been
just
the
the
single
window,
with
the
snippet
to
run.
Is
there
support
that
I?
Don't
know
about
about?
You
know
larger
project
structures,
multiple
files,
sir
yeah.
D
So
basically,
so
long
answer
is
yes
and
the
short
answer
is
I.
Guess
the
short
answer
is
yes
a
long
answer.
It's
like
we
have
to
get
a
little
creative,
but
everything
we
do
a
trunk.
It
is
basically
trying
to
hide
all
the
problems
we
like
no
hours
that
it
takes
install
Babel
or
whatever
go
behind
the
scenes.
D
D
D
One
one
thing
we
actually
were
curious
and
we
just
wanted
to
float
it
early
because,
depending
on
kind
of
like
what
the
timeline
is
for
the
website
is
when
we
wanted
to
kind
of
start
working
on
exposing
it.
It's
like
to
some
extent.
Runk
is
meant
to
be
kind
of
like
a
wayback
machine
for
both
dependencies
and
for
like
node
right
we've
been
like
downloading
and
installing
every
single
version
of
everything
for
a
long
time,
and
a
lot
of
that
we
just
don't
expose
just
because
it's
kind
of
like
a
UI
problem.
D
D
But
in
a
world
where
you
know
we
had
all
the
Knightley's,
basically
a
couple
hours
after
they
come
out,
people
could
just
go
to
like
nightly
nodejs
org,
slash
dogs
and
they
get
the
nightly
of
the
dogs
running
the
nightly
node.
And
then
you
know
I
think
it's
just
way
more
likely
that
people
are
going
to
experiment
with
like
new.
You
know
syntax
features
and
stuff
by
just
hitting
a
website
and
then
might
be
encouraged
to.
A
C
A
Probably
wouldn't
be
code
for
the
new
hot
features,
so
we'd
probably
have
to
make
some
kind
of
custom
page
for
that
and
yeah
yeah
I.
Definitely
I
really
like
that
idea.
There's
just
like
some
details
that
we
need
to
make
sure
we're.
We've
got
covered
and
like
make
sure
the
story
of
it
make
flows
correctly.
It
makes
sense,
but
yeah
I
definitely
think
that's
a
really
good
idea
and
I
I
do
think
that
you
know.
Did
this
looking
at
the
the
buffer
page,
you
know
I
noticed
it
like.
A
D
A
B
A
That's
that's
yeah,
so,
like
that's,
we'd,
probably
have
to
build
that
dynamically
into
the
templates,
but
yeah
that
should
be
fine.
Hopefully
that
would
be
fine
yeah,
but
so
on.
Your
point
of
Knightley's
I
think
that's
a
really
good
idea
and
it's
definitely
something
really
cool
to
explore,
basically
giving
people
a
playground
for
the
new
features
and
like
that
we
have
quite
a
few
people
who
are
going
it
the
ones
that
we're
going
out
building
those
features-
and
you
know
whoever's
taken
those
it
enables
them
to
go
point.
C
A
B
Yeah
I'm,
half
writing,
notes
and
half
right
now,
fun,
yeah
I
said
before
we
we
went,
live
I
made
updates
locally
to
reflect
a
lot
of
the
feedback
in
the
downloads
flow
which
I'm
sure
they'll
be
second
round
the
feedback,
probably
but
also
to
a
yeah
to
reflect
the
downloads
flow
and
to
reflect
the
the
prior
versions.
This
comments
on
both
so
I
expect
to
have
that
up
later
today
and
pushed
it
was
not
able
to
last
bit
of
polish
on
it
before
the
meeting
yeah
still
TBD.
A
B
A
And
for
what
it's
worth
on,
they
get
excited.
I.
Think
I
said
this
in
the
beginning:
I
don't
know
if
I
said
it
in
the
beating,
though
I'm
currently
gonna
be
work
well.
Tomorrow,
gonna
be
working
on
an
article
about
getting
started,
to
publish
on
the
node
source,
blog
I'm,
happy
to
repurpose
some
of
that
content
and
then
also
kind
of
note
the
places
where
yes,
this
can
be.
A
You
know,
go
into
greater
detail
that
can't
necessarily
be
put
into
a
blog
post
and
so
I'm
happy
to
kind
of
that
together
and
I
actually
have
I
already
wrote
a
post
about
this
like
a
year
ago
or
like
seven
months
ago,
but
I'm
kind
of
it.
Things
have
changed
Lots,
so
it
kind
of
indicates
that
this
is
gonna
still
be
a
living
document.
Even
you
know,
once
this
is
shipped
things
change
very
rapidly,
it
don't
feel
like
they
are,
but
they
are
so
well.
A
B
Also
want
to
just
stay
here
toward
for
the
record,
in
addition
to
the
community
page
and
getting
started
page
having
content
missing
the
home
page
is
still
kind
of
a
big
black
box
of
what
are
we
gonna
put
it
in
there
empty
black
box.
If
you
will
so,
you
will
need
to
do
a
similar
iteration
on
content
for
that,
because
the
layout
I
think
will
be
dictated
a
lot
by
we're
getting
started.
C
A
A
A
B
So
I
believe
the
wireframe
does
include
the
security
announcement
banner
or
at
least
the
version
I
have
right
now
and
the
the
foundation
event
up
so,
but
what
I'm
more
thinking
of
is
is
actual
like
marketing
content.
You
know
what
you
get
when
you
use
note:
here's
here's!
What
note
is
in
in
you
know,
far
less
than
the
whole
getting
started
page,
but
something
you
can
skim
and
understand
immediately
nature.
You
know
that
type
of
content,
the
bulk
of
the
page,
will
be
dictated
by
that
the
layout
of
it
will
be
dictated
by
that
content.
B
A
We
need
to
make
sure
like
we're,
addressing
user
module
developers,
CLI
developers,
web
application
developers,
DevOps
people
like
there's
a
lot
of
different
things
that
no
does
and
it's
never
really
just
node,
and
so
maybe
we
want
to
have
sections
on
like
node
is
good
for
X
or
node
for
X.
Actually,
so,
like
note
for
web
apps,
node
for
modular
code,
modular
JavaScript
node
for
developer
tooling
node
for
monitoring
things
like
that,
I
might
be
our
best
approach,
not
sure
with.
A
A
Maybe
I
don't
know
if
there's
necessarily
a
list
of
those
use
cases
and
I
just
kind
of
like
the
ones
that
we've
talked
about
in
the
user
feedback
modules
or
like
developer,
tooling
and
modules
being
the
one
that
I
think
we,
the
node
project,
hasn't
really
been
super
engaged
with
which
at
all
it
doesn't
quite
connect
in
my
brain
but
yeah,
that's
the
one
we've
like
talked
about
in
the
project
itself.
I,
don't
know
if
there's
additional
ones,
although
I
can
create
an
issue
asking
for
that
easily
I
can
I
could
do
that
now,
cool.
B
A
E
A
So
we've
been
kind
of
going
through
this
process
of
a
full
full
stretch
of
going
through
information
architecture,
then
into
design
and
then
into
implementation
and
we're
trying
to
make
sure
we
just
kind
of
cover
each
of
those
bases
wholly.
So
we
don't
we're
not
missing
anything
and
we
don't
kind
of
overlook
things
which
has
been
done
in
the
past
and
so
we're
trying
to
make
sure
we
do
everything
and
I
think
we're
moving
into
the
design
phase
right
now
we're
like
we're.
We
should
probably
see
that
yeah
exactly.
A
We
should
probably
figure
out
what
our
plan
is
for
that.
So
this
is
kind
of
this
is
coming
in
at
a
good
time,
but
we
do
have
a
wire
frame
that
we
out
of,
has
put
pretty
extensive
work
into
that
I
I
think
we
generally
agreed
on
the
this
structure
for
that,
and
it
does
look
like
what
your
friend
designed
actually
followed
that
just
looking
at
having
the
two
tabs
open,
yeah,
there's
only
like
a
little
bit
of
difference.
So
I
don't
know
if
that
was
just
happy
coincidence
or
if
that
was
intentional,
but.
A
There's
those
two
things
there
beyond
that
I
think
we're
trying
to
make
sure
we're
going
into
code
a
little
bit
down
the
line
just
because
we
would
have
the
design
well
polished
first,
and
then
you
know
we
have
put
in
that
wireframe
that
Adams
bills.
We
have
quite
a
few
pages
that
are
beyond
just
the
home
page
that
we
probably
need.
We
need
to
have
make
sure
we
have
a
sides
up
with
those
two
I.
E
A
The
wireframe
is
linked
in
one
of
the
issues
and
I
just
also
pasted
the
link
in
the
chat.
However,
before
you
before
that
fully
gets
designed,
we
we
we
are
still
like
in
our
kind
of
project
management
of
this
we're
still
in
the
information
design,
area
formation,
architecture,
kind
of
phase
of
this,
and
we
are
moving
into
the
design.
It
seems
like
so
I
think
that
is
probably
what
we
need
to
talk
about
next
I.
B
A
B
Is
how
do
we
transition
from
this
ia
a
section
of
the
the
of
our
workflow
into
a
more
visual
design,
oriented
flow,
Chas
I?
You
can
kind
of
do
a
sync
and
talking
github
issues,
but
a
lot
of
a
lot
of
actual
pixel
pushing
for
visual
design
happens,
happens
offline
and
without
that
necessary
feedback
flow.
So
attorney
you
you've
had
you've
experienced
some
design
initiatives
in
the
past
I
hear
with
node
and
I'm
wondering
if
you
can
talk
to
how
it
went
and
what
the
what
flows
well
or
so.
A
Got
pushed
out
to
success
to
completion
we're
just
from
kind
of
okay.
Let's
talk
about
what
we
needed
this
to
building
it
in
code
without
that
intermediary.
Let's
design
this
step-
and
there
were
efforts
to
do
that-
let's
design
this
step,
but
none
had
had
the
kind
of
sorry
for
context.
There
was
an
IO
GS,
one
I,
believe
the
documents
or
the
files
for
that
still
live
in
the
evangelism
working
group.
A
Yeah,
so
the
document
still
live.
There
was
one
person
who
was
working
on
it
and
it
never
never
moved
beyond
the
design
and
they
had
a
fully
laid
out
design.
It
was
beautiful,
but
it
they
didn't
really
have
buy-in
to
get
implemented,
which
we
do
and
then
the
other
one
was
with
a
individual
who
started
working
at
a
company
and
didn't
have
time
to
continue
to
build
the
water
to
work
on
the
website.
A
Having
pretty
continuous
communication,
probably
outside
of
github
like
in
something
like
those
slackers
or
Twitter
DM,
or
something
like
that,
just
to
be
able
to
kind
of
reduce
the
barrier
of
posting
to
github,
we
can
have
notifications
to
having
to
go
and
check
if
you
don't
use
it
up.
Notifications,
it's
like
reducing
that
barrier
and
having
a
more
instantaneous
means
of
communication
and
kind
of
building
in
since
this
in
that
small
group
and
then
bubbling
that
up
as
iterations
I
think
that's
gonna
be
our
best
option:
cool.
B
B
Awesome
I
yeah,
just
let
your
friend
know
that
it's
a
it's
a
more
than
open
invitation
and
we
we
love
what
he's
done
already
with
the
Moxon
and
would
be
excited
to
use
it
as
a
as
a
launching
pad
as
we
as
we
kind
of
dive
deeper
into
the
the
pixel
pushing
part
of
this.
This
initiative-
I
yeah,
just
just
please
let
him
know
I-
will
journey.
Oh
I,
like
the
idea
of
getting
a
dedicated
slack
channel
in
node
slackers
for
this.
A
A
B
E
A
B
Awesome
so
I
I
also
had
one
other
thing,
just
a
little
crossover
with
another
one
of
the
working
groups.
So
the
badges
initiative
is
fast
approaching.
B
This
fades
as
well
like
we
need
some
design
prototypes
and
the
first
thing
that
we're
gonna
run
into
is
just
the
need
for
an
extended
color
palette
and
I'm
wondering
if
I
have
a
little
bit
of
experience,
designing
color
palettes,
helping
out
the
designers
here
at
LinkedIn
with
them
and
I'm
wondering
if
anybody
has
any
columns
with
me
getting
something
together
and
submitting
a
proposal
for
like
a
nodejs,
extended,
color
palette,
it'll
take
the
current
colors.
We
have
and
just
add
a
whole
a
whole
bunch.
A
B
B
My
plan
is
to
take
those
there's
a
number
of
open
source
color
palettes
already
out
of
there
I'll
link
to
them
in
a
in
a
badges
initiative
issue.
I'm,
probably
gonna,
take
one
of
those
and
just
tweak
it.
So
we
think
we
don't
worry
about
all
the
accessibility,
standards
and
guidance
as
much
I.
Let
somebody
else
do
the
work.
B
A
So
I
guess
one
final
thing
there
we
should
probably
agree.
We
don't
have
a
quorum
here.
We
don't
have
enough
well
yeah.
We
don't
even
have
members
to
just
really
say
that
we
will.
How
many
represent
we
have
too
many.
So
we
don't
have
enough
members
here
to
say
that
we're
moving
into
the
design
phase
like
vote
on
it,
I
I,
guess
of
the
people
here
who
are
our
members?
Are
we
in
agreeance
that
we
should
move
to
the
design
phase
of
this.
B
I'd
like
to
be
there
by
next
meeting,
I
feel
like
we.
We
have
a
couple:
I
want
to
get
the
the
updated
wireframe
out.
Finally,
okay
and
just
get
that
last
round
of
feedback.
I,
don't
I
think
there
won't
be
any
major
fires,
but
yeah
I'd,
be
hesitant
to
say,
let's
move
into
the
design
phase.
Now,
with
the
fear
that
somebody
will
go
off
into
a
corner
and
redesign
the
whole
site
themselves,
I'm
gonna
have
to
go.
You
need
to
copy
the
structure
set
up
for
this
eye.
B
C
There
was
one
thing
that
you
already
added
something
to
it:
I
was
going
to
mention
that
we
have
that
topic
opened
for
four
topics
to
discuss
for
the
collab
summit
and
yeah
I
was
just
gonna
mention
to
anyone
who's
going
to
attend
the
meeting
that
they
should
drop
things
into
that
for
a
discussion.
So
just
saying
that
and
that's
it
for
that,
there
is
I'm
not
but
like
I
saw
a
notification
from
Olivia
on
the
comm
comm
channels.
I
feel
like
I'm,
not
sure
if
that's
private
business,
but
we
should
probably
talk
about
that.
C
A
D
Sorry
question
I
can
post
this
stuff.
I
did
in
that
issue.
I
guess
I'm,
just
wondering
I
mean
we're
all
excited
here
and
help
in
whatever
way
we
can
I'm
not
sure.
Like
again
it's
my
first
one
of
these
cuttings,
so
we
can
keep
kind
of
doing
stuff
like
we've
been
doing,
and
just
you
know,
suggesting
stuff
or
I,
don't
know
if
you
guys
just
want
something
more
formal,
but
just
throwing
it
out
there
that
you
know
we
definitely
have
in
our
minds
like
slated
time
for
this.
D
If
you
guys
want
us
to
spend
time
on
this,
so.
A
What's
your
kind
of
view
on
a
time
frame
for
that,
because
I
think
like
like
we're
kind
of
discussing
earlier
we're
going
through
a
kind
of
set
of
phases,
information,
architecture,
design
and
implementation,
and
the
implementation
bit
is
definitely
where
we're
gonna
be
using
whatever
the
tool
is
that
we
end
up
deciding
on
and
so
that
I
don't
know.
If
we
need
to
wait
with
you
on
that
or
if
we
need
to
if
we
can
start
doing
stuff
now
and
I'm,
probably
leaning
toward
wait
a
little
bit
but
I'm
not
sure.
B
So
definitely
post
that
link
on
the
github
issue.
I
think
that's
immensely
valuable
for
anybody
who
is
not,
in
this
meeting
to
say
I
like
that.
It's
an
amazing
demo,
the
one
I'd
love
to
to
see
some
type
of
implementation
example
around
just
a
basic
multi
file
version
of
that
like
I
to
to
rank
your
projects,
one
imports,
the
other
runs
it
just
because
I
know
that
will
be
a
use
case
on
the
getting
started
page,
but
otherwise.
I'm
gonna
also
extend
an
invite
to
you
for
the
I'll.
B
Add
you
to
the
to
the
doodle
invitation
list
for
the
getting
started,
breakout
working
session
that
we're
gonna
host,
probably
sometime
next
week.
Okay,
where
we'll
get
a
lot
more
into
the
nitty-gritty
of
actual
content
for
the
getting
started
page
and
hopefully
that
can
help
guide
where
you
think
your
group
should
head
I
in
helping
to
just
slowly
converge
on
a
solution.
B
I'd
I'd
be
hesitant
to
say
that
we're
gonna
we're
gonna,
make
a
choice
until
we
have
all
the
getting
the
started.
Content
worked
out,
but
we
definitely
want
to
engage,
keep
engaging
you
and
and
make
sure
that
you
know
make
sure
that
you're,
aware
of
all
the
all
the
content
that
we're
hoping
to
share
yeah
and
make
sure
that
we're
aware
of
what
one
kid
could
offer
to
fulfill
the
needs
that
were.