►
From YouTube: Node.js Website Redesign
Description
A
We
are
live
cool
hi.
Everybody
welcome
to
another
episode
of
website
redesign,
sorry
for
starting
a
little
bit
late
if
you're
joining
us
on
youtube,
so
we
will
dive
right
into
it,
since
we
have
a
couple
people
that
need
to
pop
off
at
9:30,
so
we're
gonna
start
chatting
about
issue
number
107.
This
is
the
tech
stack
consideration
issue
over
here.
We've
been
talking
about
gatsby
for
quite
a
long
time.
I'm
gonna
drop
a
link
to
this
in
the
chat
as
well.
A
Yeah
we've
been
talking
about
Gatsby
for
quite
a
long
time
and
I
figured
it's
about
time.
We
get
started
and
get
a
foundation
going
here.
So
we've
been
spinning
the
wheels
on
this
but
I
kind
of
have
an
idea
of
where
we
can
take
it
in
the
next
next
few
weeks.
So
I,
just
literally
minutes
before
this.
This
meeting
through
a
personal
experiment
over
on
my
own
Fork
of
website
redesign
here
it
lives
and
where
it
goes,
but
I
just
dropped
a
link
in
the
chat.
A
This
is
a
miller,
github,
slash
website,
redesign
the
website,
prototype
branch,
it's
just
a
simple
Gatsby
thing
and
it
will
spit
out
just
literally
all
the
getting
started,
content
on
to
a
website
they're
on
to
a
gassy
project,
it's
kind
of
a
proof
of
concept
of
data
integration,
so
we
have
a
I
think
I
want
to
get.
You
know
a
first
phase
of
this
out,
hopefully
by
February
Myles.
A
What
was
the
date
February
8th
said,
all
the
1212
awesome,
and
since
we
have
a
lot
of
getting
started
content
here
like
we
can,
we
can
get
something
up
on
a
on
a
development,
a
prototype
website,
I'd
literally
just
that
learn
page
of
getting
started,
content
and
actually
make
this.
You
know,
use
it
as
a
platform
to
start
soliciting
feedback,
so
yeah
I'm
one
of
what
people
think
about
just
moving
ahead.
Moving
ahead
with
this
tackling
it
don't
have
any
objection
tonight,
awesome,
so
we're
also
yeah
so
we're
miles.
A
B
A
B
With
what
I
would
love
to
do,
if
you
could,
if
you
would
be
up
for
it,
would
be
to
take
like
the
source
code?
That's
in
that,
let's
open
an
issue
on
it
meant
to
make
like
an
odious,
dev
site
repo
within
the
org
and
get
everyone
who
wants
to
participate,
invited
to
it
and
add
it
into
the
orc.
I
can
go
through
and
wire
up
all
the
infrastructure
for
deployment
on
that,
and
we
can
just
point
adam
at
it
and
he
can
send
some
PRS
for
design
are.
B
Alternatively,
if
you
want
to
do
more
of
a
structured
thing,
you
know
I
can
get
him
invited
to
this
meeting,
but
I
just
have
a
feeling
based
on
like
the
timeline
that
we're
talking
about.
It
may
be
faster
at
the
very
least
for
him
to
do
it
in
issues
and
asynchronously,
rather
than
waiting
for
meetings.
Beautiful.
A
I'm
definitely
happy
with
that,
and
if
you
want
to
shoot
in
my
way,
101
I
got
some
foundation
and
stuff
that
I
can
kind
of
onboard
him
with
for
I.
You
know
color
palette,
thoughts
and
stuff
like
that
yeah
and
that
the
wireframe
from
a
long
time
ago
so
and
just
kind
of
talk
about
thoughts
for
the
the
page
itself.
A
As
for
this
actual
content
like
there's
a
whole
bunch
of
stuff,
that
would
we're
gonna
need
to
add
just
functionality
wise
even
before
we
get
a
look
and
feel
thing
down
so
like
we
need
a
side
menu
that
when
you
click
on
it
will
render
pages
individually.
That's
generated
from
the
content
that
would
be
nice.
I'm
gonna.
Take
some
time
later
today
to
you
know
kind
of
break
that,
apart
into
bite-sized
dev
issues
that
people
can
tackle,
they
think
as
they
as
they
see
fit
a
little
bit
of
project
lining
here.
A
But
like
I
think
by
the
end
of
this
we
could
we
could
pretty
easily
have
a
one-pager
that
just
displays
its
content
in
a
pretty
way,
which
would
be
awesome
and
it
gives
us
a
like.
A
live
playground
to
publicly
start
playing
was
looking
feel
and
get
a
get.
A
good
look
and
feel
proposal
out
there
for
actual
site
structure.
C
A
And
there's
some
just
copy
editing
still
work
that
that
needs
to
be
done.
It's
written
first
person
through
a
lot
of
this,
because
so
this
this
was
all
content
donated
by
Flavio,
I,
awesome,
awesome,
developer
and
documenter
over
in
Italy,
but
it
was.
It
was
taken
from
a
person
blog
post
of
his
it's
giant
getting
started
with
nodejs
content
guide.
So
it's
it's
written
the
first
person
it
actually
it.
A
A
A
It's
so
it
all
lives
in
that
documentation,
folder
in
the
main
repo.
We
have
a
RFC
process
or
pulling
in
new
Doc's
okay.
So
so
it's
not
in
the
website
prototype
branch.
No,
it's
not
in
the
branch
self.
The
the
goal
for
this
site
is
just
to
pull
content
from
a
slew
of
different
data
sources
and
stitch
it
together.
Okay,
no
no
content
should
actually
live
in
the
website,
repo
itself
and
that's
all
grep
during
the
build
step
yeah.
A
Basically
so
right
now,
and
we
can
talk
about
better
ways
to
do
this
and
we're
actually
gonna
have
to
talk
with
the
I-29
group
pretty
soon
about
how
best
to
do
this,
but
we're
right
now.
We're
literally
depend
I'm
literally
depending
on
the
website,
redesign
repo
at
a
certain
commit
and
just
grabbing
it
from
node
modules.
That's
part
of
the
Gatsby
build,
so
there's
probably
smarter
ways
to
do
that.
So
that's
that's
other
work
that
that
gets
to
be
done.
B
A
Yeah,
we
need
to
sync
with
internationalization
to
see
well
one
to
get
this
content
in
the
translation
pipeline,
which
is
hopefully
gonna,
be
fairly
non-trivial,
but
then
also
figure
out
what
format
they're
exporting
it
in
and
make
sure
that
we
can
ingest
that
in
a
happy
way
down
the
line.
I
think
this
like
this
will
work
fine
for
our
purposes
for
the
February.
You.
B
Know
the
concern
I
would
have
with
it
would
be
if
the
if
the
content
is
all
living
on
different
places
and
the
site
itself
has
like
a
hard
link
to
the
commit
for
that.
It
will
be
extremely
hard
for
people
to
know
where
to
go,
to
contribute
back
and
how,
once
it's
contributed
back
automating
the
process
of
redeploying
it.
So
I
can
take
a
look
at
that
in
and
come
up
with
some
suggestions
about
how
to
maybe
streamline
that
yeah.
A
A
The
pipeline
depend
directly
on
wherever
the
content
is
published,
so
that
you
know
this
getting
started
content
if
you're,
adding
and
you
commit
to
node
core-
and
it
changes
how
you
actually
start
using
stuff
I,
you
can,
in
the
same
fell
swoop,
update
the
documentation
which
also
lives
alongside
the
coded
documents
and
no
decor
with
like
perfect
testing,
we
can
go
to
the
mman
live
in
its
respective
repos.
The.
B
Infrastructure
that
I
was
looking
to
spit
up
was
gonna
use
cloud
build,
and
so
essentially
what
it
was
going
to
do
is
every
time
there
was
a
PR.
It
would
actually
build
the
site,
put
it
into
a
bucket
and
give
you
a
link.
So
you
could
view
what
the
site
looked
like
with
your
changes
and
then
auto,
deploy
for
anything
that
lands
on
master.
That
was
kind
of
like
the
goal
for
the
infrastructure
and
I'll
just
think
about
how
we
can
link
in
content
changes
and
how
to
drive
people
towards
it.
A
So
I
I
know
that
the
internationalization
folks
have
the
tool
they're
using
we'll
watch
individual
repos
for
content
updates,
and
then
it
goes
to
the
translation,
pipeline
and
I.
Think
their
plan
is
to
publish
out
to
a
node
module
with
content
translated
content.
So
if
we
hook
up
something
like
greenkeeper
to
the
website,
the
website
proper,
like
we
can
get
an
automatic
PR
when
new
content
comes
to
the
translation
pipeline
and
possibly
have
that
kick
off
new
builds
for
this
site.
There
might
be
one
way
to
go
about
it,
but.
B
Yeah
I
don't
know
that
that's
necessarily
any
better
than
just
like
automate
PR.
That
adds
it
to
the
repo
but
I'll
save
my
tech
notes
for
later,
a
question
for
for
Jen
and
Potch
I'm,
assuming
that
we
wanted
to
maybe
take
some
of
the
examples
that
are
in
there
and
make
them
a
little
more
interactive.
D
Think,
but
at
the
highest
level,
is
taking
some
of
these.
Like
full-fledged
examples,
like
you
scroll
down,
you
know
what
a
screen
full
and
you
see
an
example-
nodejs
application,
your
standard,
HTTP
and
you're
off
kind
of
thing
that
could
actually
be
an
embedded
running
application
and
they
can
click
and
get
get
their
own
like
little
container
version
of
it
and
make
a
change
and
check
it
out
right
in
the
browser.
So
they
want
to
change
the
HTML
that
sends
or
whatever
it
would
take.
D
You
know,
like
one
click
like
it
would
be,
I
think
that's
like
the
sort
of
be
at
the
highest
level.
We
can
just
any
of
these
fully
fledged
things
that
I
do
some
serving
I
drop,
the
link
of
literally
an
embed.
That's
just
a
live
version
of
the
like
basic
example
in
chat,
so
you
can
picture
sort
of
in
that
same
footprint,
an
interactive
split
view
between
what
the
actual
server
is
rendering
to
the
client
and
and
code
itself
and
I.
D
Think
there
are
last
check
points
throughout
this
document
where
these
little
fully
fledged
you
know
servers
and
can
all
just
be
live
and
people
can
play
with
them.
So
if
they
want
to
see
how
that
works
and
what
breaks
they
can
make
changes
and
it
will
be
there
their
own
Fork
of
it
so
will
break
everyone
else.
It's
not
one
yeah,
it's
not
one
scope.
D
The
larger
question
would
be
for
some
of
the
so
this
doesn't
know.
This
is
not
really
Doc's,
which
means
that
we
don't
have
to
worry
about.
Like
sort
of
just
you
know,
seeing
the
we
don't
have
to
worry
about
just
seeing
the
sort
of
an
interactive
console,
but
anything
where
we
have
these
fully
fledged
examples.
C
Yes,
and
we
will
will
be
willing
to
build
those
out
and
add
them,
and
also
we
we
welcome
any
feedback
for
any.
You
know
things
that
we
may
hit
we're
like
well
I
wish
invented.
This
we've
been
pretty
quick
to
act
on
them
as
we
worked
with
events
with
Google,
for
example,
so
yeah
we're
very
flexible
with
that
kind
of
stuff.
A
Awesome
excited
to
see
that
happen
yeah,
so
the
pot
you
and
I
on
the
side
can
probably
sink
about
yeah.
That
looks
like
if
you
haven't
taken
my
look
already
but
like
the
the
Gatsby
it'll,
probably
just
be
a
ghastly
remark
plug-in
that'll
go
through
and
rewrite
stuff
on
the
fly
as
it
goes
out
right.
So.
E
Yeah
yeah
yeah,
honestly
honestly,
like
looking
at
some
of
the
content
it
doing
it
in
the
using
glitch
instead
of
just
static
code
blocks,
it
could
actually
reduce
some
of
the
jitter
inside
of
the
content
in
terms
of
going
contacts.
Contacts
switching
and
going
back,
I
can
fork
between
code
blocks,
so
that's
beneficial
I
think
did
you
possibly
buy
from
you
know,
might
include
rewriting
some
of
the
content
just
slow
it
down.
Yeah.
D
A
That's
very
exciting
cool.
Well,
we'll
keep
talking
tactic
I
in
the
github
issues,
miles
I'm,
looking
forward
to
meeting
Adam
and
see
what
he
has
to
contribute
over
on
the
on
the
on
the
repo
and
will
open
up
that
ticket
will
take
that
opening
up
the
ticket,
an
admin
to
make
the
new
repo
for
it
as
an
action
item.
You
may
need
action
item
after
this
meeting
suite
miles
Jen,
since
we
only
have
you
for
five
more
minutes.
Are
there
any
other
top
of
mind
issues
you
want
to
talk
about
before
moving
on
I?
Don't.
B
I
think
you
know
right
now:
I
want
to
just
dig
into
the
architecture,
and
you
know
bike
shed.
I
bet
that's
separately,
I
guess,
like
the
biggest
the
biggest
thing
to
go
over
right
now,
just
like
reiterate
all
the
things
and
make
sure
that
we
have
consensus
and
notice
problems
with
it
seems
like
the
plan.
Right
now
is
to
make
a
new
repo
in
the
nodejs
work
and
then
to
transfer
the
like
base
website
content
that
you
had
in
your
branch
there
over
to
that
repo.
B
Then
we
would
point
people
who
are
going
to
participate
directly
at
the
repo
itself
for
doing
style
changes,
preferably
maybe
opening
issues
with
suggestions
before
doing
a
bunch
of
work
and
then
we'll
figure
out
a
flow
for
content
in
the
next
week
or
two
and
then
Potter
again,
if
you're
doing
it
like
we'll,
have
like
a
document
to
process
of
where
and
how
to
send
the
hours.
For
that.
Does
that
all
sound
like
in
line
with
what
we
were
saying.
B
And
I
think
that
that
will
like
truthfully,
you
know,
be
a
really
good
litmus
tests
or
like
if
you
have
friction
as
you're
going
along
Podge.
Please
document
it
and
let
us
know,
because
you
know
you've
I,
don't
wanna,
say
you've
been
around
the
block,
but
like
you've
done
this
for
a
minute,
and
you
know
some
best
practices.
So,
if
you're
dealing
with
friction
and
collaborating
when
we're
all
working
directly
together,
new
people
when
we
do
this
launch
will
definitely
have
that
exact
same
problem
and
not
necessarily
have
the
same
ability
to
navigate
it.
B
A
A
B
A
Yeah
cool:
let's
move
on
it's
a
more
procedural
issues
here
in
in
the
repo.
So
next
one
at
least
tagged
for
more
discussion
is
and
99
Doc's
hackathons
merely
want
to
talk
about
progress
here,
and
do
we
want
to
remove
the
flag
on
this
until
maybe
after
the
landing
pages
out
next
time,
yeah.
G
I'm
I'm
not
sure,
I
think
that
one
was
initially
pinned
as
a
issue
to
me,
can
you
hear
me?
Yeah
I
think
that
one
was
initially
pen
doesn't
issued
will
be
discussed
while
we
figured
out
if
that
could
be
used
to
leverage
the
content
generation
products.
Now
that
we
have
a
large
influx
of
Ducks
content
coming
in
periodically,
we
can
probably
take
that
one
out
and
the
updates
there
I
think
the
last
time
you
had
talked
about
it.
A
G
A
F
E
G
Last
I
want
to
add
one
more
point
that,
after
the
foremost
put
together,
I
think
we
we
pinged
a
user
feedback
with
like
a
link
to
the
forum
and
said
that
it
had
been
iterated
over
and
asked
them
for
their
input
on
it.
That's
I'll
drop
this
over
there.
Anyone
in
user
feedback
who
wants
to
present
user
feedback.
If
you
can
bring
that
to
the
meeting,
that'd
be
great
that
we
could
probably
move
forward
on
this,
because
I
think
this
was
the
next
step.
A
A
G
A
H
A
We'll
get
that
get
that
moving
cool
and
then
the
one
other
issue
not
on
the
agenda.
For
today
we
talked
a
little
bit
in
the
last
calm,
calm
meeting
about
how
we
want
foundation,
content
to
factor
into
new
website
stuff
and
that's
of
Rachel
on
the
call
over
here.
I
think
Sarah
mentioned.
She
was
interested
in
chatting
more
about
it,
but
looks
like
she
wasn't
able
to
join
today.
A
H
A
Yeah,
so
laughter
I,
remember
immediately
left
off
with
a
we're
interested
in
it,
especially
with
merger
stuff
happening.
We
don't
know
exactly
where
that
content
is.
Is
gonna
fall
like
how
much
we
want
of
it?
What
type
of
content
we
wanted
that
we
were
gonna
hash
out
some
ideas
for
like
right.
What
on
the
current
site,
we
want
on
the
new
site
and
then
the
other
requirement
was
we
need.
A
We
need
it
to
be
editable,
not
in
github,
so
we
had
been
chatting
with
contentful
a
little
bit
about
getting
a
support
through
them
for
a
headless
CMS,
so
you
can
just
go
in
and
edit
content
through
WYSIWYG
and
it'll
just
show
up
on
the
site,
as
you
save
changes
to
that
and
yeah,
and
actually
that
that
gets
me
prototype
I've
been
playing
with,
does
have
a
content,
full
integration
out
of
the
box.
So
we
can.
We
can
make
that
data
integration
happen
which
is
nifty
so
I
don't
know.
A
H
I
mean
I
think
we
should
definitely
bring
this
are
we
we
haven't
had
too
much
additional
conversation
around
it,
but
you
know
we
definitely
want
to.
You
know
just
be
able
to
get
content
over
and
just
you
know
be
collaborative
in
that
aspect.
So
from
a
technical
standpoint,
if
there
are
recommendations,
I
think
we're
open
to
that.
So
I
think
brainstorming
would
be
good
out
there.
Yeah.
A
Awesome
so
we
we
could
go
through
the
exercise
of
like
walking
through
the
foundation
site
and
seeing
what
content
is
in
or
out
and
go
through
the
ia.
You
know
design
and,
oh
my
god,
really
my
browser
autocompletes
when
I
start
writing
the
foundation
site
down
to
foundation.
Rjs
org,
which
puts
the
other
on
on
a
phishing
website
that
somebody
set
up
on
nod
jeaious
I.
A
However
I
I
don't
know
if
that's
necessarily
the
best
use
of
everybody's
time
on
the
call
right
now.
So
if
we,
if
we
want
I'd,
be
happy
to,
you
know,
cut
the
meeting
a
bit
early
call
people
who
don't
want
to
stay
on
and
chat
about
foundation,
site,
structure
optional
and
like
we
can
just
walk
through
the
site
and
start
coming
up
with
an
ia
proposal
in
the
next
twenty
minutes.
The
content
to
keep
Orkut,
if,
unless
other
folks
have
topics
to
bring
up.
That
might
be
a
good
use
of
time.
G
A
A
And
the
releases
page
so
that'll
be
kind
of
phase
two
and
then
phase
three
would
be.
You
know
beefing
up
the
rest
of
the
site,
probably
with
foundation
content
more
interactive,
API
Docs,
so
it
wouldn't
be
until
later
this
year
that
this
would
actually
happened,
but
I
think
it's
good
to
start
planning
I'm
thinking
about
how
it
fits
into
larger
side,
side
structure.
Now.
A
This
awesome
well
I'm
gonna,
go
ahead
and
end
the
livestream
anyway,
on
a
live
stream.
Who
wants
to
take
part
in
this
exercise.
The
link
to
join
is
in
the
github
issue,
so
feel
free
to
jump
in
and
keep
chatting
but
I'll
on
the
live
stream
now
and
we'll
we'll
just
talk
shop
about
a
foundation
side,
okay,
cool
bye,
everybody
on
YouTube,
yes,.