►
From YouTube: Node.js Website Redesign
Description
A
I
mean
someone
of
the
tangible
deliverables
was
to
make
a
little
design
system
for
anyone
or
any
designer
out
there.
That
would
want
to
maybe
take
on
designing
a
few
pages
later
on
a
lot
of
stuff,
so
maybe
microsites
with
the
look
and
feel
of
of
nodejs.
So
I,
don't
if
you
guys
had
a
chance
to
look
at
the
stuff
in
figma.
So
in
there
we
have
the
style
guide
per
se
with
the
color
typography
I
kept
the
colors
as
we
had
them
before.
A
A
A
So
I
put
those
two
calls
to
actions:
they're
no
Jess
LTS,
which
is
the
one
that
deleted,
is
the
one
that
people
are
EE
the
most
where
you
can
get
the
current
as
well
or
in
here
I
had
an
idea
to
put
some
sort
of
like
interactive
section.
I,
don't
know
if
that's
like
me
face
to
so
what
I
put
here
at
first
was
just
the
commands
to
download
it
like
right
away
right
as
long
as
and
as
well
as
the
documentation
would
teach
you
to
documentation
page
in
a
second
here.
A
I
had
also
it's,
for
us
is
big
communities,
it's
pretty
big,
so
the
next
section
is
about
like
a
then
someone,
I
have
and
stuff
like
that.
So
that's
it
and
then
here
I
kind
of
put
a
section
about
like
features
and
things
like
that.
This
might
change.
I
might
change
the
isn't.
If
you
choose
I,
just
put
it
there
for
reference
and
then
a
call
to
action
to
subscribe
to
the
to
the
newsletter.
A
And
then,
if
you
go
to
the
dogs,
I
created
a
there's,
two
things:
there's
the
template
for
a
basic
documentation,
page
right
that
anybody
could
follow
with
the
h1s
and
h2s,
and
you
know
all
that
stuff
as
well
as.
If
you
look
at
this,
it's
in
you
can
look
at
a
dark
theme
as
well.
I
put
breadcrumbs
also
the
date
in
which
was
edited
and
but
that's
pretty
much
the
template
page.
You
do
have
a
home
page
for
documentation
per
se,
which
in
here
would
be
kind
of
like
what
is
known
like
what?
A
What
can
you
do
with
know
like
it
stuff
like
that
more
about
documentation
per
se?
And
then
here
you
would
have
all
the
navigation
to
that.
These
would
be
like
you
would
click
on
this,
and
this
would
open
which
Maps
really
closely.
What
we
have
here,
I'm
just
taking
from
from
here
I'm
grouping
them
a
little
bit
better,
so
they
make
sense,
and
that
is
oh
and
then
in
here
I'm
creating
all.
A
So
all
these
elements
are
kind
of
like
components,
so
it'll
be
easy
for
you
guys
to
to
come
in
here
and
then
and
code.
These
things
like
you
could
go
into
code
mode
and
then
see
like
all
the
different
attributes
and
all
stuff
here.
So
everything
is
old
with
the
specification
that
are
in
here
everything.
So
everything
is
connected,
so
he
can
see
me
really
really
easily.
That's
it
yeah!
That's!
B
Very
cool
I'm
psyched
to
keep
watching
this
come
together
for
the
the
light-dark
mode.
I
think
all
we'll
need
is
just
if
it
can
be
kept
relatively
one-to-one.
The
mapping
like
it
would
be
nice
to
just
switch
a
global
variable
for
colors
for
light
in
dark
mode
and
I
call
it
a
day.
But
if
we
need
to
do
something
more
custom
we
can
we
can
manage
that
as
well
like
it
do
you
is
it
currently,
a
1:1
mapping,
no
yeah.
A
Yeah,
the
only
thing
that
changes
is
the
primary
color
changes
from
green
to
this
pink
and
then
it's
just
basic
color.
That's
the
only
thing
that
changes
yeah
and
it's
just
yeah,
just
a
gold
variable.
B
B
C
B
A
B
B
Yeah
I
I,
like
it
there
personally
we're
kind
of
we're
kind
of
saying
we're,
not
gonna,
have
a
live
code
demo
on
the
on
the
home
page.
At
this
point,
you
on
what
you
don't
want
to
consider
pros
and
cons
for
I'd
say
like
it's
kind
of
neat,
to
see
it
running.
But
at
this
point,
if
you
don't
have
a
general
understanding
of
what
what
note
is
you're
gonna
go
to
the
learn
page
and
have
to
get
more
detailed
content.
B
So
we
might
want
to
get
a
little
bit
of
user
feedback
from
from
new
engineers
to
see
if
not
having
the
live
demo
on
the
page
and
instead
having
CLI
install
options
is
in
fact
a
better,
a
better
experience
for
them
because
they'll
be
live.
They'll
be
live
code
Dumbo's
here
in
the
learn:
docs
correct,
yeah,
yeah,
yeah,.
A
The
idea
so
like
big
is
that
people
would
come
I
guess
as
soon
as
they
downloaded.
That
would
come
to
get
started
about,
what's
known
all
stuff
and
then
moving
to
tutorials
like
the
first
tutorial
and
then
Johnny
talked
about
maybe
putting
videos
in
there
and
also
so.
We
could
do
this
stuff,
like
that
in
this
session.
Your
and
then
after
that
more
advanced
things
like
advanced
guides,
which
you
were
following
that
in
here
so
I'm
just
kind
of
grouping
these
together,
yeah.
B
And
John
I'd
love
to
get
your
thoughts
on
so
Oscar.
You
kind
of
have
a
video
tutorials
section,
that's
independent
of
getting
started
or
advanced
guides.
John
do
have
thoughts
on
if
it's
it
better
to
have
like
the
video
tutorials
as
a
separate
area,
or
is
it
better
I'm
interspersed
in
the
the
text-based
getting
started?
Their
advanced
guides
like
I,
think.
D
It
would
probably
be
like
the
videos
could
live
just
embedded
with
the
written
content
like
either
a
link
out
to
a
YouTube
channel
or
it
could
be
embedded
in
the
page
or
something
like
that.
I
think
yeah
I
think
that,
like
for
personally
I
think
that
makes
the
most
sense.
So
if
you
land
on
a
page-
and
you
want
to
watch
the
video
it's
there,
otherwise,
you
know
you
land
on
the
page
and
there's
a
video
somewhere
you're,
not
probably
gonna,
go
track
it
down.
Yeah.
B
Because
there's
there's
gonna
be
a
weird
mapping.
If
we
we're
gonna
have
to
be
careful
about
the
video
content,
we
we
make
and
make
sure
it
maps
directly
to
the
getting
started
flow.
The
existing
documents
there,
because
if
it,
if
it
starts
diverging
too
much,
then
we'll
struggle
with
where
to
put
it
or
it
will
match
the
content.
D
A
And
I've
seen
some
really
good
talks
about
node.
Maybe
we
can
include
for
channel
and
in
this
section
which
talks
about
what
no
it
is
really
I.
Obviously,
this
is
just
like
template
content
right,
but
in
here
we
could
put
those
type
of
videos
or
if
we
make
an
actual
media
about
it,
we
can
just
put
it
in
here
and
then
just
keep
keep
the
the
content
or
the
typed
content
minimal
as
well.
B
If
we're
going
to
start,
including
third-party
content,
we
might
want
to
draw
the
policy
for
what
we
are
willing
to
include
versus
not
include
in
another
part
of
the
project
like
we
had
included
third-party
tools
that
were
sort
of
like
endorsed,
like
you
can
recommend
this,
but
like
as
as
tools
to
help
develop
a
note,
but
when
one
of
them
was
removed,
it
seems
like
there
is
some
now
open
discussion
about
what
rules
are
we
following
when
we
decide
which
third-party
tools
genders
or
not
so
the
same
thing
for
content
would
be
nice
to
have
so
this
might
be
a
good
reason
to
draw
that
out.
B
B
A
A
D
Dropped
some
links
into
the
agenda
issue
for
this
from
at
least
older
ones
that
we
had
I'm
not
sure,
if
maybe
they're
wrong
or
whatever,
but
they
point
to
the
MJ
design
system.
If
you
can
maybe
go
look
at
that
issue
and
check
to
see
if
those
links
are
sending
to
the
right
place,
but
I
drop
those
in
a
minute
ago.
Okay,.
B
B
A
B
Cool
disconnected
they're
in
a
video
auto
played
yeah.
If
you,
if
you
drop
the
the
updated
link,
it's
gonna
stay
consistent,
oh
I
need
to
switch
over
the
automatic
issue,
generator
take
a
generator
anyway,
if
we're
consolidating
one
or
both
so
while
I'm
in
there
I
can
drop
it
in
some
of
this.
The
worker.
A
A
A
Okay,
I'm
gonna
get
off
then
cuz.
It's
gonna
get
really
technical,
I
guess
after
this.
A
B
D
A
For
now,
and
will
be
awesome
if
you
could
like
go
through
the
prototype
and
the
way
you
go
to
the
prototype
is
like
this
should
be
a
present
or
some
sort
of
call
to
action
here
and
then
go
through
all
organized
a
little
is
a
little
bit
better,
so
I
didn't
make
sense,
but
I'm
just
particularly
interested
in
seeing.
If
this
may
sensing
the
hierarchy
of
the
sections
make
sense,
because
we
can
change
the
look
and
feel
as
much
as
we
can
but
I'm
just
curious
about
like
okay
yeah
this.
A
This
makes
sense
to
have
it
there
or
yeah
I.
Don't
know
if
the
features
will
go
well
here
like
stuff
like
that.
I'm,
not
sure
that
this
is
valuable
for
the
audience.
So
that's
the
kind
of
feedback
I'm.
D
A
For
not
so
much
about
how
it
looks
so
like
right
now,
oh
I
lost
that,
maybe
in
the
next
in
the
next
meeting
yeah
and
then
I'll
organize
these
a
little
bit
better,
so
that
it
makes
a
little
bit
more
sense.
And
then
you
guys
can
give
me
feedback
about.
Okay
makes
sense
to
have
to
get
started
and
then
the
story
goes
and
then
I've
got
guys
and
the
way
I'm,
organizing,
that
cool.
D
A
A
I
wanna
get
a
feel
for
for
the
styling
per
se
as
well,
but
but
that's
not
like
what
I'm,
what
I
master
but
feel
free
to
to
give
feedback
on
on
collars
typography
the
type
scale
that
we're
using
the
the
spacing
scale
that
we're
using
as
well
like
all
that
stuff.
You
guys
can
keep
me
feedback,
but
that's
not
necessarily
where
I'm
after
right
at
this
moment,
cool
awesome.
B
Cool
it
might
be
I'm
gonna
leave
this
in
a
comment
in
the
fingerboard
too.
For
the
the
feature
section,
it
might
be
time
to
solicit
some
homepage
content
again
from
the
folks
on
the
technical
side
of
the
project.
That'd
be
curious
to
see
what
what
they
think
should
be
highlighted
on
the
home
page
for
a
first
time.
They
would
know
that
user
yeah,
los
4
with
us
with.
A
Those
lists
should
be
yeah
and
if
we
even
need
those
like
or
if
that's
like,
we
want
to
call
those
out
should
it
be
before
the
community
things
I'm
just
putting
like,
based
on
the
Google
Analytics
I'm,
just
putting
that
hierarchy
on
the
on
the
first
thing
that
people
see
right,
like
the
first
thing
that
they
do
is
download.
Second,
is
kind
of
like
like
learning
right
like
call
to
action
to
learn,
and
the
second
is
about
all
about
community
right
features
and
all
that
stuff
I'm
just
reading
them
below
the
fold.
D
B
To
meet
you
man,
ok
same
cool,
see
you
soon
awesome!
Let's,
let's
dive
into
the
regular
agenda
here:
oh
I'm,
gonna
punt
on.
B
C
B
Issue
number
147
made
a
while
back:
it's
the
new
home
no
JSF
ticket.
There
was
talk
back
in
February
about
merging
the
two
repos
because
having
an
admin
repo,
which
basically
just
holds
meeting
minutes
and
auto-generated
meeting
tickets
separate
from
the
code,
repo
I
could
potentially
be
confusing.
We
got
came
back
at
me
a
collaborator
summit
that
it
was
in
fact
a
little
confusing.
C
B
Oh
I
have
a
PR
open
over
in
no
Jaidev
which
we
can
merge
in
if
we,
if
we
choose
to
move
forward
with
this,
just
moving
meeting
minutes
and
pertinent
stuff
in
the
read
me
over
so
we'll
leave
that
open
for
I
think
the
requisite
48
hours
for
additional
comments
as
well.
But
you
can
keep
the
discussion
going
here.
I
know
many
of
you
had.
You
had
concerns
about
merging
the
two,
but
have
you
instead
of
all
dairy
is
still
in
a
similar
spot.
B
Well,
if
the
focus
of
the
cleverest
some,
it
actually
came
out
and
said
well,
it
is
actually
confusing
for
us
and
it's
getting
in
the
way
of
us
doing,
work
or
actually
contributing
an
administrative
level.
Then
that
probably
means
that
that
should
be
fixed,
so
I'm
just
looking
through
the
pull
request
and
not
dev
I
kickin.
What
number
is
it
sorry
yeah?
It's
PR
number
270,
okay
via
o,
merge
content
from
website
redesign,
okay,
fair.
A
B
D
B
As
a
to
clarify,
where
did
the
meet
minutes
go
now?
Do
they
go
into
directory
meeting,
slash
and
then
just
like
before,
but
in
the
same
repo
yep?
So
all
I
did
in
that.
Pr
was
basically
copy
paste.
The
new
meetings
directory
over
and
any
relevant
information
and
contributing
that
mainly
being
I
emerged
in
which
wasn't
a
lot
there's
a
good
bit
of
duplicate
content.
B
It
was
just
basically
work
round
in
Lua
form,
and
now
it
adds
a
fair
amount
of
length
to
read
me,
especially
for
someone
who's
skimming
quickly
up
and
down
I'm
wondering
if
there
would
be
any
objections
for
removing
the
old
parts
that,
because
I
think
right
now
we're
in
the
very
last
part
it's
inside
development,
yeah
I
was
wondering
the
same
thing.
I
have
no
objections.
There
I
copied
it
over
for
completeness
sake,
but
we're
all
okay
with
mixing
it
him
right.
I'm
done,
he
talked
about
that.
Did
you
use
it?
D
It
I'm
not,
you
know
it
wasn't
super
useful
to
me.
We
could
probably
pull
that
into
a
you
know
a
folder
or
something
just
so.
The
information
is
preserved
somewhere
but
doesn't
have
to
be
on
the
readme
I've
been
thinking
a
lot
about.
You
know,
working
on
the
readme
or
whatever
in
general
and
I
I.
Don't
I,
don't
think
that
particularly
like
it
confused
me,
I
was
like,
should
I
make
a
pull
request
to
add
myself
to
the
repo
I,
wasn't
sure
what
was
going
on
so
yeah.
B
C
B
D
B
I'll
mix
that
from
the
PR
leave
it
open
for
the
requisite
48
hours
and
then
we'll
merge
it
in
there's.
There's
additional
work.
We've
done
for
the
meeting
issue
generation
and
I
want
to
need
to
do
the
work
to
two
port
issues
that
should
stay
alive
from
website
redesign
over
to
dev,
since
we're
not
doing
it
rebo,
my
name
actually
I
can
examine
old
Rico
I'll.
B
Do
that
work
when
I
when
I
merge
to
be
our
super
also
related
to
last
time,
while
I
was
away,
I
didn't
I
did
catch
a
message
from
owner
about
starting
access
to
the
zoom
account
and
I'm
wondering
if
we
need
to
revisit
the
policies
for
like
how
many
people
have
access
to
it.
So
we
have
a
reasonable
amount
of
backups
when,
especially
multiple
people
are
awake.
Yep
there
was
a
lot
of
vacation
and
readjusting
post
post
conference,
so
I
yeah.
B
B
B
B
So
if
you
pop
over
to
know
JSF
and
take
a
look
at
the
project
boards
in
there,
I
made
five
different
project
boards,
there's
a
whole
slew
of
them,
one
of
which
is
just
about
done.
What
will
will
augment
with
issues
once
we
once
we
get
mocks
from
from
Oscar
or
to
learn
page,
but
for
kind
of
the
five
major
pages
that
were
building
out
here
I've?
Maybe
we
made
this
project
boards
along
with
stub
issues
or.
B
B
B
That's
interesting
I
guess
they
just
didn't
get
pulled
on
the
boards.
Okay,
well,
I'll!
Do
that
cool!
Well,
there's
project
boards
that
will
soon
have
issues
in
them
and
then
there's
stub
issues
for
a
lot
of
major
content
over
in
issue.
So
it's
a
lot
more,
a
lot
more
showing
up
here.
You
go,
take
a
look!
So
there's
no
issues
for
a
you
know:
release
page
documentation,
new
download
grid
for
the
release
pages
and
just
kind
of
nitty-gritty
technical,
a
we
need.
This
comment
on
the
darn
site,
like
other.
B
The
other
significance
are
to
integrate
the
static
JSON
files
that
we
have
for
documentation
into
the
site
and
actually
just
show
some
basic
guide
documentation
from
what
we
currently
have
it's
pretty
detailed
tickets,
but
there's
a
lot
of
they're
kind
of
borderline,
good
first
issues,
because
there's
there
really
needy
because
it's
a
bit
of
core
infrastructure,
but
for
somebody
for
somebody
looking
for
something
to
dig
their
teeth
into
there's
some
very
good
time.
Content
here
obviously
need
to
surface
it
in
these
project
boards.
B
State
of
things
supposed
to
post
collapse
it
it's
it's
a
lot
of
content
to
go
through
and
we
could
either
like
give
a
high-level
review
of
each
ticket
right
now.
Just
for
the
you
know,
video
evidence,
but
that
might
not
be
the
best
use
of
time.
Looking
at
the
dev
agenda
list,.
B
Yeah,
looking
at
the
looking
at
the
dot
dev
thing,
a
few
of
these
were
were
tagged
with
the
meeting
issue
that
would
basically
just
be
technically
does
on
how
we
might
do
it,
but
just
rereading
the
ticket,
so
I
guess
for
you
to
a.
How
would
you
like
to
use
the
the
rest
of
time
can
keep
talking
technical
content
or
we
could
keep
talking
organizational
needs.
D
We
could
do
technical
stuff,
one
of
the
things
I
pulled
down.
I
fork,
the
repo
like
just
the
other
day.
I
was
looking
for
something
to
do,
and
I
was
trying
to
jump
into
the
release
pages
or
something
and
I
realized.
There's
so
there's!
No,
you
know
I
started
the
project.
I
realized
there
is
no
release
page.
Yet
no.
A
D
B
B
B
We
need
releases
that
police's
infinite
scroll
thing
at
the
bottom
to
load
so
I,
linked
to
the
the
currently
close
to
JSON
file,
which
we're
just
gonna
hit
up,
as
if
it's
a
fake
JSON
API
for
this
I
link
to
that
you
can
use
the
wireframe
for
general,
rendering
of
it
for
now.
So
all
this
all
that's
basic
data
integration
and
just
like
you
get
the
content
on
the
page,
we
can
do
before
a
final
mock
because
it'll
be
a
yeah.
D
B
D
D
I
see
now
the
release
process,
documentation,
yeah,
that's
also
another
yeah.
Whatever
doesn't
how
we
break
it
up,
doesn't
really
matter.
I
guess
that
much
I
was
just
I,
was
I'm
learning
so
much
more
about
the
the
repo
and
the
the
state
of
the
project
by
finally
getting
in
and
writing
some
code,
I
realize
it.
Oh
yeah,
there's
probably
a
lot
of
code
I
can
write.
I
can
help
out
writing
just
not
just
documentation
stuff.
There's.
B
D
Was
basically
my
my
question
was
I
was
like
oh
like
should
I
just
would
that
be
beneficial
to
like
just
create
the
page
and
then
where's
it
gonna
fit
in
the
hierarchy,
because
I
couldn't
see
where
I
was
trying
to
just
drop
the
Gatsby
codebase
in
general
and
I'm,
familiar
with
gat
C,
but
I
was
like
I,
wasn't
exactly
sure
where
all
the
pages
were
pulling
from,
etc,
but
that
might
help
people
get
started.
If
there's
like
a
structure
that
we
have,
even
if
it's
just
skeleton
or
whatever,
but
one
question
I
had
to.
D
When
do
we
plan
to
like
release
the
site,
not
release
size
and
final,
but
I
mean
like
Gatsby
is
a
static
built
thing?
If
that,
if
that
release,
information
is
available
from
JSON
that
could
be
built
at
compile
time
instead
of
having
to
be
dynamically
loaded,
assuming
assuming
that
JSON
information
gets
updated
from
the
like
a
pull
request
or
somewhere,
you
know
in
the
node
repo
we
could
maybe
just
set
up
a
trigger
to
build
the
site
again,
etc.
Is
that
is
it
too
early
to
worry
about
this
stuff
or
that's.
A
B
Most
of
the
content
gets
automatically
published
when
window
publishes
I
and
it's
it's
an
independent
build
process
and
all
these
JSON
files
get
dumped
out
onto
the
existing
node
org
server.
So
we
can.
We
can
assume
that
that
will
update
as
node
gets
released
and
I
kind
of
want
to
decouple
the
website
redeploying
from
the
data
redeploying
right,
because
you
don't
want
to
have
to
redeploy
the
website
with
every
redeploy
you
know,
or
at
least
especially
not
now,
because
the
releases
team
doesn't
know
that
that
would
be
part
of
that
process.
B
B
We
also
don't
necessarily
want
to
as
we're
building
out
the
site.
You
want
to
be
aware
of
a
bundle
size,
because
if
we,
if
we
bundle
every
JSON
giant
JSON
blob
with
all
the
historical
versions
in
tune
right
into
the
final
bundle,
it's
gonna
get
pretty
big,
pretty
quick
and
just
grow
over
time.
So
a
single,
oh
ting,
huge
chunks
of
data,
is
probably
to
our
benefit.
I.
B
D
For
me,
yeah
I'm,
real,
quick,
I'll
talk
about
I,
had
an
issue
probably
started
in
the
website
of
the
design.
Just
about
like
what
would
we
based
off
what
we
had
talked
about
about,
helping
to
onboard
more
developers
to
the
project?
I
started
an
issue
just
to
you
know,
track
or
whatever
keep
it
and
ask
to
see.
D
If
anybody
had
any
advice
or
like,
is
there
a
getting
started
document
you
really
like
somewhere,
we
could
look
at
and
I
came
back
to
it
eventually
and
realize,
like
a
lot
of
this
information,
I'm
talking
about
exists
somewhere
in
this
repo
I'm
just
now
like
absorbing
it
all
and
realizing
where
it
is
so
it's
like
yeah
but
there's
a
there's.
An
issue
I
started
about
that
just
to
as
I'm
I'm
dogfooding
it
myself.
D
B
Totally
the
the
people
already
in
this
project
have
the
the
curse
of
prior
knowledge.
So
definitely
keep
track
of
that
and
if
there's
anything
you
wish
you
had
earlier
on,
let
us
know,
because
a
lot
of
a
lot
of
context
is
buried
in
issues
which
is
always
a
risk
with
larger,
larger
projects
yeah.
So
anything
you
wish
was
surfaced
earlier
on:
let's
definite
that
out
of
the
reading
cool.
D
Yeah
yeah,
luckily
there's
that
was
one
of
the
I
think
objections
of
like
merging
the
two
repos.
Was
there
being
like
a
lot
of
issues
but
I
think
with
tagging
you
know
we
can
just
provide
a
link
in
the
readme
to
like
hey
here's,
the
issues
that
you
might
care
about.
If
you
don't
care
about
governance,
so
go
look
at
these,
but
yeah
cool.
B
Barring
any
other
large
agenda
items,
I
might
give
you
10
minute,
but
10
minutes
back
and
I'd
probably
appreciate
that
too
I
have
a
10
o'clock.
Let's.
D
B
D
D
B
I'm
gonna
definitely
flesh
out
some
more
the
kind
of
architectural
issues
that
I
open
up
over
claps.
It
currently
get
them
pulled
into
the
project
boards
so
that
they're
a
little
more
organized
I
love
riding
boards,
yeah
and.