►
From YouTube: Node.js Website Redesign
Description
A
Why
now
to
meet
a
hello
youtube
world?
It's
good
to
see
you
again
so,
as
I
was
just
saying
on
the
the
private
stream,
for
sake
of
folks
might
be
tuning
and
I
need
to
start
out
with
a
bit
of
a
income.
Just
what's
next
walk
to
the
envision
board
a
little
bit
and
try
and
figure
out.
You
know
where
we
can
start
poking
at
next,
because
we're
starting
to
it
and
beat
the
the
learn
page
to
death
and
it's
time
for
the
next
I
think
the
next
next
is
so.
A
Our
meeting
agenda
is
issue
number
159
and
website.
Redesign
I
just
dropped
a
link
in
the
chat
there,
but
really
I
want
to
start
out
I'm
Oscar,
you
dropped
a
link
in
the
cherry,
an
issue
in
the
in
website
redesign.
It's
not
a
157
and
just
for
the
first
issue
on
the
list
here.
It
links
to
a
Google
Doc,
where
you
wanted
to
capture
nice
to
have
once
that
needs
good
current
website
status
and
vision
for
the
future.
I
won't
want
to
implore
everybody
to
keep
adding
to
that
list.
A
It
looks
like
we
only
have
a
few
bullet
points
in
there,
so
this
will
help
you
out
Oscar,
as
he
keeps
going
down
on
the
rather
but
kind
of
number
freewheeling
regard
here.
We
did
have
or
do
have
an
envision
board
kind
of
that
was
setting
vision
for
structure
and
content.
Let's
drop
the
link
in
the
channel
I
would
read
the
long
enough
for
folks
on
the
dream,
but
that
would
probably
not
be
beneficial.
A
A
This
was
a
long
time
ago,
kind
of
source
of
truth
for
longer
term
vision,
and
it
has
most
of
the
large
verticals
in
the
site,
blocked
out.
That's
really
split
up
into
five
sections
home
page
those
invade
which
should
look
for
figure.
The
docs
page,
which
is
reskin
of
the
current
API
Docs
made
hand-wave
here,
because
there's
a
lot
of
functionality
we
can
pack
in,
but
we're
limited
by
the
way
the
docs,
our
current
structure,
we're
gonna
have
to
create
there
really
sorry
man
do
you
want
to
share
your
screen?
A
B
A
So
we
have
the
home
page,
which
is
self-explanatory
again,
a
bunch
of
hand,
wavy
content
for
the
home
page
I
think
we
get
to
iterate
on
this,
but
should
be
something
of
this
structure.
With
this
general
content
on
here
consider
layout
entirely
optional,
like
I
think
we
just
identified
major
content
sections.
We
need
an
upset.
Well,
the
download
button
will
learn
more
button.
We
need
some
way
to
brag,
it
might
be
the
one-two-three
punch
here.
It
might
be
something
you
know
differently,
structure
depending
on
content.
A
A
Yeah
and
you,
the
learn
page,
should
look
fairly
familiar,
so
we've
been
working
on
the
past
past
month
and
a
half
or
so.
This
one
is
in
a
pretty
odd
place.
Right
now
and
I
think
we
have
a
good
plan
very
next
steps
for
the
docs
page.
So
this
is
again
big
hand
wave
because
there's
a
lot
we
can
pack
in
here,
like
I,
said
for
extra
features
like
it
would
be
awesome
to
pull
out
the
it's
like
API
reference
at.
C
A
A
So
this
is
where
you
go
to
download
whatever
version
you
want,
if
you're
downloading
manually
so
there's
a
whole
intervention
here,
we
can
do
a
much
better
job
of
documenting
our
release.
Process
like
this
chart
is
hard
to
understand,
but
I.
We
tracked
that
variables
of
people
who
who
communicate
that
well
and
it's
just
epically
long
list.
If
you
really
really
want
it
of
every
release
with
the
the
SHA
song
and
the
date
released,
yada
yada
yada
there's
also
this
like
grid,
which
desperately
needs
to
be
redesigned
as
well.
It's
like
hey!
A
You
want
to
install
for
a
specific
system.
Here,
you
go.
Here's
the
button
to
click
by
default.
It
should
it
should
present
you
with
for
your
system
that
we
can
infer
and
with
download
options
very
LTS,
current
and
nightly.
There
was
also
a
lot
of
communication
around
how
we
should
talk
about
package
managers
so
like
people
who
install
through
nvm
or
install
through
some
other,
you
know
system
specific
package
system.
A
Should
we
document
that
a
lot
of
them
are
not
maintained
by
node
proper,
so
outstanding
questions
there,
and
then
you
notice,
the
community
page
is
non-existent
because
we
don't
know
what
contents
gonna
go
in
there
I'm,
hoping
that
the
outreach
working
group
will
help
we'll
help
flush
out
that
conk,
that's
just
up
and
coming
so
yeah.
That's
just
a
quick
review
of
the
state
of
state
of
the
future
Oh
Thank
You
owner.
D
A
If
my
internet
works,
it'll
load,
pretty
pictures
yeah,
so
it
actually
like
communicates
what
each
type
is.
This
makes
like
branded
drawing
for
the
release
type
and
talked
about
you
know
path
to
wherever
they're
going
the
time
for
releases
and
where
they
are
in
the
process.
Right
now,
so
really
nice
there's
some
creative
stuff.
We
can
do
here.
If
we
want
to
dive
deep
yeah,
I,
guess
I'll
open
the
floor,
see
anybody
have
thoughts,
opinions
where
we
should
go
next.
D
Maybe
let
me
give
a
quick
update
on
the
knowledge
data
integration
from
noches
orc
I
start
with
this,
and
I
am
up
to
first
of
all,
I'll
do
a
similar
page
as
LuAnn
page,
because
we
have
lots
of
articles
which
are
the
same
like
10:00
p.m.
or
like
console
lock
and
that
kind
of
stuff
I
don't
know
I
would
go
for
a
new
page
first
of
all
and
leave
it
there
until
people
I,
don't
know,
can
work
with
and
fix
it
a
bit
because
I
don't
think
so
that
will
be
I.
D
D
E
A
So
for
context,
we
have
a
whole
bunch
of
articles
in
what's
called
the
current
knowledge
base,
not
organized
not
arranged
in
any
particular
way,
some
of
which
might
already
be
duplicated
in
the
existing
learn
page,
some
of
which
might
be
completely
new.
My
kind
of
hope
for
the
learn,
page
and
I'm
sure
there's
extra
there's
more.
We
can
do
from
a
design
standpoint
to
communicate.
This
better
is
to
really
good
encouraged
sectioning
out
sent
like
this,
so
it
might
not
just
stop
at
advanced
guides.
A
A
C
Mean
it
has
like
how
to
echo
script
v
with
node.
It's
like
well,
okay,
that
probably
that's
something
that
definitely
isn't
in
the
guide,
because
it's
I
think
it's
probably
assumed
context
yeah
going
through
and
D
duping
and
seeing
like
what
we
have
already
and
what
we
don't
and
which
of
the
ones
that
are
in
here
like
how
do
you
try
catch
that
kind
of
stuff
like
what
is
required?
C
A
So
that
D
duping
will
be
important,
and
it
might
be
time
to
add
that
advanced
guys
section
because,
like
somebody
getting
started
with
node,
doesn't
need
to
know
what
event
emitters
are
necessarily
but
like
if
you're
really
diving
deep
and
wanted
to
get
to
know
it
intimately
like
people,
I
get
the
foot
or
you'll
probably
want
to
want
to
pick
this
up.
So
for
a
lot
of
these,
they
might
just
be
able
to
go
into.
For
the
moment.
D
D
A
If
you
take
just
a
first
pass
and
sticking
in
that
Advanced
section
where
there
isn't
very
duplicate
content,
we
great
and
the
the
PR
make
sure
that
they
live
in
the
right
place
and
there
would
probably
be
a
couple.
Tricky
ones
where,
like
we'll,
have
to
have
a
good
conversation
around
it.
Services.
A
E
D
What
we
also
can
do,
of
course,
we
can
create
a
learn,
well
knowledge
pace
which
I
called
whole
tree
actually
because
a
lot
of
article
well,
it
starts
with
how
to
so
I
called
it.
How
to's,
maybe
we
can
integrate
them?
I
mean
we
can
pull
the
content
down
to
not
just
Africa.
We
can
have
a
page
which
gets
created
from
guess
tree
statically.
Well,
we
just
don't
like
link
it
nor
there,
so
we
can
just
edit
it.
So
we
don't
need
to
necessarily
publish
it
in
some
way.
Yeah.
D
To
it,
so
you
don't
have
I
mean
we
don't
need
to
link
to
the
page,
Nova
and
another
in
the
top
navigation
or
in
the
well
left
bar.
You
don't
need
to
link
it.
No
we're
just
the
page
exits
for
you.
Don't
have
access
from
the
index
so
that
people
can
still
edit
it
and
work
on
it,
but
it
doesn't
really
need
to
necessarily
wished
I'd.
A
See
what
you're
saying
so
just
get
the
content
into
the
repo
have
a
essentially
private
page
where
we
can
start
or
stash
the
content
for
now,
and
we
can
triage
later
will
be
an
option.
Yes
yeah.
That
is
certainly
an
option.
I
mean
this:
it's
largely
documentation
content,
so
wouldn't
it
Oreille
ting
in
a
PR
as
if
we're
putting
it
in
learn
page
for
D
duping
content
like
the
functionally
the
same
like
there's,
not
we're
not
blocking
anybody
by
not
having
it
live
on
the
the
deployed
site
right
now,
not
yet
at
least.
C
I
mean
it's
also
worth
noting
that
I
yell
I
don't
have
the
metrics
for
this
site.
I,
never
seen
this
page
before
and
I
use
this
site.
More
than
probably
most
people
do
like
I,
don't
even
know
how
you
get
yourself
I
doubt
it
gets
a
ton
of
traffic,
and
so
you
know
that's
another
thing
to
consider
is
also
I'm
looking
at
which
of
these
pages
actually
do
get
traffic
to
know,
which
are
the
topics
that
people
care
about
right
now.
B
C
A
I
want
to
triple
check
I'm
gonna,
stop
screen
sharing
for
you
sure
what
stop
screen
sharing
for
a
hot
second
and
try
and
dig
up
this
Google
Analytics
right
now,
because
I
remember
a
little
while
back
that
the
Google
Analytics
got
gutted
from
the
web
site,
oh
yeah,
for
privacy
reasons
yeah.
So
we
might
have
old
data.
Yes,
I!
Don't
think
we'd
even
get
a
new
date
over
the
past
few
months,
I
thought
he'd
gotten
credit
for
like
two.
B
C
A
Yeah,
so
they
they
gave
me
access
a
while
back
to
the
Google
Analytics
account,
so
I
can
actually
just
go
log
in
and
see.
Let's
see
what
the
ladies,
this
data
is,
so
I'll
I'll
get
it
on
that
an
Oscar
I'll
get
you
that
data
I
can
start
working
on
that
and
Oscar
I
know.
I
know
you.
You
have
to
piece
out
at
9:30
ish,
which
is
coming
up.
I
want
to
make
sure
that
we
have
whatever
we
need
to
get
for
you,
so
that
you
can
your
own
block.
We
can
start.
A
B
Great
question:
thanks
Sam,
so
I
had
a
couple
of
questions
for
you
guys
or
nod.
Questions
were
like
maybe
action
items
I
do
want
to
create
a
like
an
information
architecture
of
the
entire
site
and
and
for
each
page
can
I
put
what's
the
real
goal
behind
each
page
like
was
the
like
the
purpose
of
existence
of
that
page
right
and
why
we
need
to
have
it
so,
for
example,
where
you
were
when
you
guys
were
talking
about
the
learn
page.
B
You
know
all
that
all
those
little
things
I
want
to
be
able
to
have
a
really
good
understanding
of
the
entire
like
tree
of
the
site,
and
then
so
that's
that's
the
first
thing.
The
first
thing
was
to
do
a
like
an
information
architecture
tree
of
the
site
share
with
you
guys,
based
on
what
you
put
together
Adam
with
this
envision.
So
I'll
share
with
you
guys
and
then
each
page
will
have
maybe
a
goal,
and
you
guys
can
tell
me:
yes,
that's
pretty
much.
B
So
that's
the
second
thing
and
then
I
was
I
was
gonna.
Ask
you
guys
if
we
could
reach
out
to
the
community?
Maybe
we
talked
about
this
Adam,
but
I
think
it
would
be
nice
to
to
involve
the
community
in
this
process
so
in
the
design
redesign
process.
So
we
could
ask
them
like
some
of
the
questions
on
the
on
the
Google
Doc,
like
you
know,
what
do
you
like
the
most
about
no
J
or
I?
B
Don't
know
like
we
can
word
it
differently,
like
what's
the
best
documentation
side
that
you
have
encountered
or
something
like
that,
so
we
can,
or
what
do
you
like
to
see
more
on
the
nodejs
site
so
that
you
know
starts
to
become
more
like
a
community
involvement
redesign?
So
what
are
you?
What
do
you
guys
think
about
all
those
three
things
so
the
outreach
to
the
community
yeah
Twitter?
B
A
Yeah
so
I
think
this.
This
Google
Doc
that
you
you
put
together
is
a
great
start
and
I'd
love
to
get
it
in
a
format.
That's
a
bit
more
digestible
for
a
larger
group
and
honestly
I
think
all
we
have
to
do
is
copy
these
questions
into
a
google
google
form
like.
Let's
just
get
this
step,
one
step,
two
step.
Three
answer:
these
five
questions:
click
Submit
you've
contributed
back
to
two
DOJ's
web
website
redesign
and
we
can.
We
can
get
this
tweeted
out,
probably
by
the.
B
I,
like
that,
the
full
Google
Form
thing,
because
then
we
will
have
data
to
back
up
or
you
know,
design
rationale
as
to
why
we
ain't
creating
a
bag
like
that,
so
yeah
I'll
be
they'll,
be
really
cool.
Also
I
mean
the
role.
If
we
can
get
the
Google
Analytics
I'll
be
awesome
to
see
you
know
what
each
if
we
could
like
I,
don't
know
how
much
we're
tracking
but
you'll
be
nice
to
know
where
people
go
first
and
then
from
there
kind
of
like
this
is
to
worry
behind
each
session.
C
I
thought
I'm
said
like
the
analytics
might
have
been
taken
out,
but
we
do
have
historical
data.
I
can
tell
you
right
now.
90%
of
traffic's
to
downloads
I
can
tell
you
that
right
off
the
bat,
so
I
think
that's
a
lack
of
having
other
having
a
strong
navigation
or
information
architecture
and
navigation
structure,
and
you
know
having
resources
that
people
want
to
come
back
to
and
so
I
don't
think.
That's
like
our
main
thing.
I
think
it's
just
like
this
is
the
one
thing.
C
C
I
mean
eh
it's
if
they're
using
javascript,
they
basically
have
to
use
node
and
so,
like
whatever
I
mean,
like
I'm,
not
saying
that
in
a
negative
way,
but
like
if
you're
gonna
use,
webpack
or
reactor.
Anything
like
that
anything
from
the
register.
Npm
registry
you're
gonna
have
to
have
node
to
be
able
to
use
NPM
and
to
build
systems
and
all
that.
So
it's
very
good.
F
F
A
B
A
A
Give
me
up
so
the
the
trademark
for
the
logo
specifies
the
Pantone
or,
like
sorry,
Penta
would
have
been
yeah,
Pantone,
colors
and
there's
a
little
bit
of
wiggle
room
and
how
those
are
translated
to
hex
values,
because
they
don't
translate
one
to
one
on
web,
so
that
color
palette
proposal
that
I
have
that
on
medium
right
now
has
a
subtle
enough
change
to
the
green
scale
that
it
maps
to
the
same
Pantone
color
doesn't
violate
the
trademark
but
looks
better
on
display
screens,
so
I
would
highly
recommend
use
that
green
spectrum
in
that
proposal.
A
B
Cool
yeah,
okay,
maybe
we
can
start
with
with
what
you
had.
Obviously,
maybe
we
can
do
some
small
tweaks,
but
the
idea
would
be
to
be
awesome,
like
you
said,
to
be
able
to
theme
this
and
maybe
see
how
how
things
look
once
you
know,
once
we
roll
out
the
society
would
be
nice
to
just
change
a
couple
values
on
a
like
a
config
file
or
whatever,
and
be
able
to
have
like
individual
paintings.
B
If
people
want
to
make,
maybe,
like
a
I,
don't
know
like
we
talked
about
this,
a
time
like
like
meetup,
page
and
I,
don't
know
Argentina
or
whatever
they
could
use
designs,
and
it
was
really
really
fast.
Hardly.
A
Yeah
as
far
as
implementation,
I
want
to
very
much
separate
the
design
phase
of
getting
the
system
down
and
the
execution
phase
of
getting
the
system
down,
because
I
I
do
design
systems
that
LinkedIn
for
my
full-time
gig
and
it's
yes,
it's
a
pain
to
build
one
from
scratch
thousand
percent,
but
taking
one
off
the
shelf
and
and
renaming
it
is
better
for
our
use
case.
My
people
approach.
We
also
are
a
giant
team
of
developers
all
over
the
world,
so
it
may
be
not
the
worst
thing.
A
If
we,
you
know,
we
are
able
to
customize
things
off
the
shelf
a
little
bit
faster
than
most
robably.
We're
also
probably
able
to
build
stuff
from
scratch
faster
than
milk,
so
I
mean
it'll,
probably
be
determined
by
the
needs
of
the
pages
that
were
on.
If
we,
if
we
can
identify
a
good
existing
design
system
like
component
library,
that's
easy
to
redeem
and
we
can,
we
can
adjust
with
our
own
typography
and
item
spacing
and
color
palette.
B
B
It
so
I'm
gonna
create
I'm
gonna,
sir,
creating
them
the
the
style
sheet.
We
can
change
their
values,
but
but
at
least
we
have
a
structure
of
what
what
are
the
five
really
the
five
foundation,
so
colored
epigraphy
is
spacing,
and
do
we
have
like
an
iconography
library
that
we
could
use
or
like
okay?
Oh.
A
We
can
use
any
of
them
yeah
and,
and
there
I
I
would
probably
stick
more
towards
the
open-source
side
of
the
icon
library
world.
But
if
there
are
options
Weedon
that
you
think
would
absolutely
fit
perfectly
for
one
reason
or
another,
we
can
investigate
getting
a
license
for
it
or
hanging
on
like
a
one-time
people,
seeing
what's
possible,
no.
B
Cool
cool,
so
so
actions
for
me
for
me,
specifically
I'm
gonna
start
creating
the
information
architecture,
the
tree
also
a
structure
for
the
style
sheet,
the
Google
form
with
the
questions
that
are
on
the
Google,
dog
and
and
yeah.
That's
so
I
had
four
for
me
and
for
you
guys
what
I
had
was
see
if
we
can
get
any
Google
Analytics
info
and
that's
it
I
like.
B
I'm
basing
it
on
on
what
Adam
already
did
so
that
just
as
a
starting
point
but
but
I'm
I'm,
assuming
that
it
will
change
a
little
bit
once
we
get
the
data
from
from
the
from
the
survey
or,
ideally
you
know,
we
would
get
the
data
from
the
survey
and
say:
okay
yeah.
This
is
this
is
that
this
is
the
right
approach
to
do
the
site.
But
that's
what
I'm
my
approach,
yeah
well
I,
don't
know.
B
B
A
Exactly
yeah,
okay,
so
so
this
is
the.
This
is
the
current.
This
is
the
website
structure,
as
it
currently
is
abomination
of
weak
pages
that
were
slapped
in
there
with
no
good
rhyme.
The
reason
I,
it's
probably
a
little
bit
more
intentional
than
that,
but
but
the
yeah.
So
we
would
want
something,
probably
similar
to
this
for
the
entire
site,
just
to
formalize
it
and
make
sure
we
forget,
I,
wouldn't
certainly
recommend
like
there.
A
There
was
a
little
bit
of
work
done
here
already,
probably
not
as
in
granular
detail,
as
as
you
were
thinking
so
feel,
free
to
use
this
as
a
launching
point,
yeah.
B
When
I
make
sure
that
every
page
that
is
in
there
every
like
make
a
little
note
in
that
in
that
tree
has
a
purpose
right
like
it's
actually
we're
dedicating
time
based
on.
You
know
a
valuable
you
know
something
that
would
be
valuable
for
our
users
right,
so
yeah,
I'll
Cesar.
Is
that
what
the
one
that
you
just
copied
on
yeah.
B
A
A
I
want
to
start
thinking
about
what
we
can
do
to
start
working
like
what
we
need
right
now
and
we
know
we'll
need
regardless
of
design,
but
what
data
will
mean
flowing
to
be
able
to
make
these
pages
work
and
how
we
can
start
approaching
that,
because
that's
a
big
fun
conversation
which
will
be
fun
to
slice
up
so
cool.
Thank
you
for
staying
a
little
longer,
Oscar,
okay,.
A
So
like
this
is
the
this
is
the
type
of
what
we're
gonna
need.
This
like
list
of
content
in
order
to
make
the
releases
page
happen,
I
don't
know
where
it
currently
lives
in
what
format
it
lives,
but
we
get
it
there.
Any
of
you
have
any.
C
C
A
Diggity
Dog,
look
at
that
cool.
Well,
that
was
easy,
so
I'd
love
to
make
a
task
for
hitting
up
this
file
and
being
able
to
just
at
least
display
a
list
of
all
prior
versions,
and
we
can
start
thinking
about
how
to
make
it
searchable
or
navigatable,
but
like
we'll
need
this
data
loaded
onto
some
page
on
the
site
in
order
to
make
it
work.
So
I'm
gonna
make
you
for
that,
but
a
lot
of
our
next
faves
tasks.
If
we're
gonna
lump
we're
gonna
lump
these.
A
A
Yeah
tyranny:
do
you
have
any
context
and
how
the
current
API
documentation
is?
Is
the
built
in
stored
I
know,
I
looked
at
this
like
a
year
and
a
half
ago
a
long
time
ago,
but
I
don't
remember
exactly
how
I
have
no
clue.
No.
E
A
Yeah,
that's
fun,
so
I
think
a
good
first
step
for
getting
API
stuff
displayed
and,
like
I
said
we
can
get
data
flowing
without
design
so
far
right
now,
because
it's
gonna
be
a
large
task
in
and
of
itself,
so
I
don't
entirely
know
what
they
use
to
generate
current
API
Docs,
but
as
long
as
we're
pulling
content
like
I
think
we
can
probably
take
a
similar
approach
as
long
as
just
playing
content.
We
can
probably
a
similar
approach
to
how
we
currently
build
the
Gatsby
site.
A
C
Or
discrete,
it
would
also
be
interesting
if
we
could,
instead
of
pulling
doden
as
a
dev
dependency,
because
I
yeah
we'd
have
to
do
a
git
dependency
instead
of
doing
it
that
way,
I
wonder
if
we
could
publish
have
a
separate
repo
or
a
separate
tool
that
pulls
pulls
in
the
docs
and
that
publishes
them
as
a
module
and
MPM
building
anything
it's
soon.
That
might
be
too
complex
for
what
we're
trying
to
do,
but
that'd
be
a
nice
thing
to
do.
E
A
A
C
D
C
Though
is
that
the
docks
evolved
over
time
so
like
when
you
know
they
release
a
point?
Fifteen
point
one:
it's
different
from
eighteen
point:
fifteen
point:
oh
and
like
every
single
incremental
version,
effectively
changes
docks
like
there
are
usually
50-plus
changes
to
docks
in
every
release.
So
you
do
one
like
for
someone
who
is
looking
for
who
is
on.
You
know,
eight
point
fourteen
point
two
or
even
ten
point
0.7
or
like
whatever
sorry
Oh
point
ten
point:
seven,
whatever
ancient
versions,
people
still
need
those,
and
so
it's
you.
C
You
have
to
have
those
older
versions
and
I
believe
that's
I
mean
we
might
be
able
to
just
pull
the
data
directly
from
the
build
system.
I'm,
not
sure
how
that
works,
but
you
do
need
to
have
that
source.
Also
I
believe
there's
Jason
for
all
of
this
actually
on
the
website
right
now,
but
now
that
I
remember
thinking
about
it
more
I
believe
it
all.
A
Solution,
Jason,
so
anything
that
we
even
that
what
tab
I
have
it
open
it
now
that
route
pass
releases,
JSON
page
like
we
can
depend
on
that
for
right
now,
but
if
we're
hoping
to
go
towards
a
world
where
we
replace
nodejs
org,
then
we're
gonna
have
to
replace
any
data
sources
for
leverage
things
if
they're
deployed
to
the
current
static
site.
So
you
know
it's:
it's
there's
the
diff.
C
E
C
A
A
It
has
markdown
files
in
it
that
I
consider
API
documentation,
I
want
to
display
it
so
for
the
first
pass
of
that,
we
can
actually
have
a
get
a
get
target
in
our
package,
JSON
to
current
head
of
node
and
just
use
this
Doc's
directory
with
markdown
the
all
the
markdown
commit
there'd
in
it
and
just
get
it
displaying
on
something
that
looks
like
an
API
page
with
a
version
switcher
that
will
only
have
one
version
which
is
latest.
Another
task
will
be
getting
historical
API
documentation
in
a
consumable
way.
So
this
will
be.
A
Cool
I'll
capture
that,
in
this
issue,
this
issue,
which
issue,
was
it
this
issue,
yeah
I'll
capture
that
in
this
issue
and
probably
spin
out
a
separate
issue
for
the
the
dedicated
module
tier
Nia
I,
know
you've
been
working
a
lot
with
pulling
in
historical
intro.
Here
like
it's,
something
that
you
be
interested
in
tackling.
C
A
That's
fine
I'll
make
at
least
a
requirement
spec
in
we
can.
We
can
divvied
out
the
people
who
wanted
there.
Maybe
somebody
in
the
community
will
scoop
it
up
and
make
it
happen.
We
can
I'm
assuming
that,
once
we
get
once
we
get
a
something
up
and
running
that
that
can
easily
pull
in
documentation
at
a
at
a
version
we'll
be
able
to
throw
in
a
get
hook
to
kick
off
that
build
process
of
some
sort.
Whenever
there's
a
release
right,
we
can
talk
with
build
about
that.
All
right.
A
A
Anything
else
to
add
about
API
documentation,
ingestion
too
many
tabs
open
y'all,
it's
terrifying!
You
can
actually
see
my
my
crazy
screen
here.
There.
E
E
C
A
E
A
A
A
Awesome
I'll
flash
that
up.
Thank
you
for
that
reminder.
That's
very
important
awesome.
The
other
issue
on
this
list.
Localized
document
consumption.
We
do
have
two
minutes
left
this
I'm,
just
gonna
up,
keep
bugging
nights
and
unfuck
to
get
that
meeting,
set
up.
I
think
there's
work
to
be
done
on
their
end,
to
publish
the
node
module
and
to
really
get
the
API
interface
worked
out
for
us,
so
we'll
yeah,
well,
lucky
bug
and
Imfurst
been
automating
and
just
scheduled
myself.
A
If
I
can,
if
they're
too
too
busy
to
doodle,
there
was
a
future
request
for
a
search
on
the
docs
page
I
think
it's
a
great
idea.
I
think
we
need
it.
I
think
it
might
be
a
little
bit
too
early
to
execute
on
it,
since
we
don't
have
API
Doc's
up
and
running
yet,
and
we
don't
know
how
integration
is
gonna
look
but
I
wanted
to
raise
it
as
a
hell.
Yes,
we're
gonna
do
this.
This
needs
to
happen.
Let's
do
it.
E
A
Cool
I
and
then
the
last
part
I'm
gonna,
make
stub
tickets
by
meal.
I'm
gonna
make
stub
tickets.
The
last
comment:
I
have
at
least
I'm
gonna
make
some
tickets
for
pulling
in
past
version
releases
and
just
getting
an
ugly-looking
page
that
just
dumps
all
that
info
out,
we'll
probably
keep
it
in
PR
for
a
while
until
we
start
getting
designs
for
it.
So
we
don't
have
something
ugly
sitting
around
but
similar
to
how
we
need
to
get
API
Doc's
ingestion
working.
A
We
need
to
get
past
version
releases,
ingestion
working
and
for
now
we
can
probably
just
rely
on
that.
Json
file
like
the
juice
is
very
comprehensive,
yeah,
so
we'll
just
we'll
get
a
page
that
makes
it
makes
client-side
call
that
JSON
file
like
an
API
request
and
dumps
the
data
on
the
page
and
we'll
call
that
an
early
integration
for
now
and
make.