►
From YouTube: Node.js Website Redesign
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
some,
we
are
live
on.
Youtube,
hello,
internet,
welcome
to
another
episode
of
website
redesign
ojs
edition
yeah.
So
we
have
a
good
chunk
of
stuff
to
talk
about
today,
because
there's
actually
been
a
lot
of
movement
in
the
past
week,
so
we
will
dive
right
into
the
agenda
here.
This
is
issue
number
one.
The
agenda
is
issue
number
one
33
in
the
website:
redesign
repo
and
we're
gonna.
Kick
it
off
with
come
from
calm,
calm
anymore,
but
kick
it
off
with
hu
134.
A
This
is
more
of
just
a
visibility
issue
and
also
Rachel
for
just
a
ping.
I'd
literally
just
threw
this
up
before
the
meeting,
so
don't
worry
about
it,
but
this
is
I
kind
of
synthesized
in
a
rather
not
too
pretty
way,
but
the
confidence
all
there
are.
The
discussion
about
foundation
website
content
that
we
had
at
the
end
of
the
last
meeting
we
walked
through.
This
is
refresher.
A
We
walk
through
all
the
content
on
the
foundation
website
that
we
could
find
and
kind
of
flag
stuff
as
either
keep
Orkut
keeping
in
mind
that
there
is
a
foundation
merger
going
on.
So
a
lot
of
the
foundation
specific
content
will
probably
disappear.
The
goal
is
not
to
have
this
all
in
for
the
first
version
of
the
site,
and
this
will
probably
be
follow
up,
but
we
should
keep
in
mind
where
it
fits
into
the
I
structure
I
and
by
the
time
we
get
to
it.
A
Presumably,
by
putting
the
bootstrap
timeline
the
founding
or
the
merger
will
have
gone
through
and
the
new
foundation
is
gonna
get
its
own,
its
own
branding,
its
own
site,
presumably
I,
so
yeah
Rachel.
If
you
want
to
run
this
like
content
list
by
anybody
who
might
have
a
vested
interest
in
it
and
love
to
see
if
we're
missing
anything
or
if
we've
mislabeled
stuff
is
important
or
not
important,.
B
A
Awesome
and
at
some
point
we'll
probably
want
to
break
these
out
into
individual
tickets
and
prioritize
them,
which
we
will
talk
about
a
little
later.
Okay,
cool
any
other
points.
We
want
to
bring
up
on
foundation,
website
content
before
moving
on
to
they're,
really
exciting
stuff.
A
A
You
know
it
just
you
know:
I'm
gonna
have
to
look
at
that.
If
that's
unfortunate
well,
I
think
the
wrong
thing
in
the
docks
there.
So
moving
right
along
we're
gonna
take
a
look
at
a
closed
ticket
which
is
actually
linked
wrong
in
the
meeting
issue.
This
is
issued
to
96
in
nodejs
admin,
so
we
popped
open
an
issue
to
go
and
make
the
new
nodejs
website
prototype
repository
and
lo
and
behold
it
got
created.
A
A
There
we
go
awesome,
we're
talking
towards
a
February
12th
date
to
get
website
the
the
learn
page
up.
There
I
had
a
prototype
running
in
a
personal
repository.
It's
not
what
pulled
into
the
nodejs
org,
so
it
is
official
now
so
we'll
be
iterating
in
this
repo
on
on
the
content
and
on
the
display
of
it.
There
is
a
link
here.
You
can
see
what
this
thing
renders
out
to
at
nodejs
redesign
dot,
Serge
Sh,
it's
not
gonna
live
here
forever,
it's
absolutely
literally
just
so.
A
A
Build
and
he'll
have
more
information
on
that
after
he
gets
probobly
for
next
meeting
after
he
gets
approval
and
gets
it
gets
all
this
spun
up,
but
presumably,
whenever
something's
pulled
into
master,
will
we'll
see
it
automatically
deploy
to
the
Google
cloud,
build
servers
and
whenever
you
he's
hoping
to
get
it
so
that
whenever
you
put
forward
a
pull
request,
you'll
it'll
automatically
deploy
that
branch
to
a
temporary
URL.
So
you
can
see
a
preview
of
the
site
as
well,
so
we're
gonna
have
a
pretty
nifty
CI
CD
process.
A
A
It's
arm
stem
they're
like
a
brain
dump
of
of
everything
we
talked
about
last
time,
but
we
are
this
first
page
that
we're
putting
together
is
gonna,
be
this
learn
page,
which
I
just
linked
to
the
envision
app
and
four
people
following
along.
It's
linked
in
it's
linked
to
the
envision.
App
is
linked
to
an
issue
296
of
Jas
admin.
A
We're
just
gonna
be
building
out
just
this
learn
page,
which
should
look
familiar.
It
looks
like
that
surge
surge
that
Sh
link
that
I
posted
in
there
with
just
all
the
documentation
content,
but
need
a
little
prettier
Adams
working
on
making
this
into
a
nice
single
pager
that
will
not
just
have
documentation
cut
then,
but
look
pretty
and
look
like
node
as
well,
so
we
can
get
it
rolled
out.
It'll
be
handing
over
a
higher
fidelity
mock
of
that
pretty
soon.
So
we
can
get
things
updated,
but
there's
also
a
lot
of
work.
A
We
can
do
in
the
meantime
until
we
get
that
single
page
or
design
that
your
Moulton
will
have
probably
this
weekend
yeah.
So
that's
kind
of
the
current
direction.
We're
headin
in
there
like
what's
been
done
and
in
kind
of
the
direction
was
starting
to
move
in
any
thoughts
or
opinions
from
people
called
in
right
now.
Otherwise
you
can
talk
about
like
what
work
actually
needs
to
get
done
to
get
there
for
February
12
I,
actually.
C
B
A
Yeah
yeah
I'll,
I'm
gonna,
be
there
in
April
I'll,
give
them
a
cool
thing.
That's
good!
That's
very
good
to
know
cool
yeah!
So
there's
there's
a
good
chunk
of
stuff
that
we
need
to
do
today
to
the
site
itself.
Before
that
we
can,
we
can
actually
do
before
we
even
get
to
get
to
making
it
look
nice,
which,
honestly,
it's
text
formatting
and
a
sidebar,
so
I'm,
hoping
the
make
it
pretty
part,
will
be
pretty
straightforward,
so
I
to
kind
of
support.
This
work
inside
the
website.
A
Prototype
repo
I've
made
us
a
project
board
where
we
can
track
towards
that
February
12th
deadline.
We
have
so
I've
seeded
it
with
a
couple
tickets.
Here,
there's
gonna
be
more
as
I
find
time
to
start
making
new
new
tickets.
What
we
should
track
against
everybody
feel
free
to
make
tickets.
If
you
see
the
need
and
drag
it
to
the
project
board,
I'm
hoping
use
project
boards
pretty
heavily
for
a
website.
The
website
prototype
since
we're
gonna,
be
we're.
A
Gonna
have
a
series
of
different
deadlines:
I'm
hoping
they
keep
so
I'll,
be
keep
it
pretty
well
organized,
but
we,
the
two
tickets
currently
in
there
are
the
glitch
integration
with
the
getting
started,
content
which
Potch
is
working
on
and
we
need
to
get
a
status
update
on
him
from
fairly
soon
and
then.
The
other
kind
of
meaty
thing
that
we
need
is
there's
a
right.
Now.
A
A
The
data
that's
getting
ingested
render
out
a
sidebar
with
all
the
top-level
items
and
make
it
so
when
you
click
on
it,
it
just
swaps
out
the
page
in
the
main
content,
that's
kind
of
the
big
media
thing
we
can
do
right
now
without
mocks,
and
it's
also
a
great
first
issue
for
people
to
start
getting
familiar
with
with
Gatsby
and
the
setup
here
so
I.
You
know
I'd
love
to
offer
that
ticket
up
to
anybody
who's,
looking
to
contribute
back
and
I,
get
their
hands
dirty
and
code.
Finally,.
A
I'm
gonna
make
the
the
promise
/
not
threat,
but
please
save
me
for
myself.
You
know
if
we
don't
get
to
it
by
probably
Tuesday
of
if
somebody
else
doesn't
get
to
it
by
Tuesday
of
next
week.
It
shall
probably
just
pop
in
and
knock
it
out,
but
I
would
love
the
extra
extra
hands-on,
so
yeah
feel
free
to
claim
that
ticket
as
your
own
just
leave
a
comment
and
say:
I
got
this.
If
you
want
to
commit
to
it
and
we'll
make
it
happen,.
A
A
A
A
A
You
know,
keep
it
sounding
like
a
like
a
documentation
website
and
not
a
an
opinion
piece.
It's
not
like
he
did.
Oh,
he
did
a
large
effort
to
make
sure
that
it
to
convert
a
lot
of
that
stuff.
So
it's
just
a
couple
places
where
it
was
missed
or
where
it
just
sounds
a
little
funky.
So
we're
gonna
want
to
tweak
that
there's
also
some
like
probably
nice,
nice
to
have
type
of
features
like
the
I
really
like
that.
A
A
A
A
B
A
That
would
be
absolutely
wonderful,
yeah.
Here's
the
issue,
I
just
threw
it
in
the
chat,
so
the
you
can
either
do
it
feel
free
to
do
in
whatever
format
is
this
for
you,
you
can
either
do
it
just
reading
through
the
website
and
making
notes
of
where
it
needs
to
change
or
like
if
you're
comfortable,
with,
though
with
the
markdown,
with
the
markdown
view
inside
of
it's
out
of
github,
you
can
sift
through
that
other
documentation
link
in
there,
but
yeah
feel
free
to
feel
free
to
do
it.
Whatever
format
feels
best
more
sure.
A
B
A
Copy
editing
like
copy
I,
think
he's
not
gonna
block
any
other
features,
we're
hoping
to
roll
out,
but
it
should
yeah
we
can.
We
can
get
it
in
anytime
between
now
and
then
techfoot
mm-hmm
cool,
thank
you
for
jumping
on
that
is
amazing,
sweet
other
than
that.
We
have
just
one
other
issue
and
website
redesign
that
has
been
getting
some
activity
just
kind
of
this
continued
discussion
about
tech.
A
Stack
consideration,
however,
were
moving
ahead,
pretty
fortunate
with
the
Gatsby
at
the
moment
and
I
think,
especially
for
the
the
12th
date
we're
hoping
to
hit
it's
a
it's,
not
tenable
to
switch
frameworks
at
the
moment
and
honestly,
looking
at
mohit,
newer,
I
think
your
comment
there
is
accurate,
like
Dhaka
Soros
doesn't
have
that
federated
sorry.
This
is
issue
107.
A
A
Yeah
Dhaka
Soros
is
is
great,
I.
Think
for
like
single
standalone
projects
that
aren't
pulling
in
from
all
different
locations.
However,
I
I
kind
of
want
to
take
this
and
evolve
it
into
an
outstanding
question
of
how
we
should
host
like
what
our
longer-term
plan
is
for
hosting
API
documentation,
because
there's
no
reason
why
that
needs
to
live
in
a
giant
single
page,
app
like
that
can
be
generated
into
a
bunch
of
individual
HTML
pages
and.
C
A
C
I
mean
also,
on
top
of
that,
you
know
we
current
and
like
currently
I.
You
could
prefer
not
to
degrade
the
experience
of
hearing
of
which,
like
is
a
single
page
single
static
page.
So
there
I,
don't
think
is
actually
any
JavaScript
loaded.
There
might
be
for
the
syntax,
highlighting
there's
individual
pages
for
each
section
and
for
each
actual,
like
subsection,
I,
believe
and
then
there's
also
the
jason
view,
which
is
basically
a
parsable
edition
of
the
docs
yeah.
A
So
my
my
kind
of
hope
in
the
in
the
medium
term
for
API
Docs
its
we,
we
literally
just
reskin,
what's
already
getting
built,
which
I
think
is
just
it
just
spits
out
a
whole
bunch
of
HTML
files.
Yeah
it
don't
so
we
can
yeah,
we
can
reskin
it
for
a
version
of
it.
So
we
have,
you
know
the
same
nav.
It
has
the
same,
look
and
feel,
but
it's
still
just
hosted.
A
Html
content,
I
think
for
the
main
site,
like
we're,
hoping
to
do
some
extra
enough
extra
stuff
that
it
makes
sense
to
have
the
extra
infrastructure
of
a
single
page
app
for
you
know,
pulling
in
content
from
contentful
for
foundation
desk
material
for
a
community
page
where
we
probably
want
to
list
start
listening
some
of
these
meetups
that
we're
starting
to
like
we
have
a
doc
running
of
meetups
in
your
area.
Now
it
would
be
great
to
get
that
displayed
in
a
nicer
way.
A
C
Doc's
with
the
nice
part
about
Gatsby's,
they
expose
all
of
their
content
via
graphic
uol's.
So
you
can
actually
just
basically
have
another
build
stuff
that
will
you
build
SP
a
and
then
you
can
kick
it
out
to
another.
Build
step
of
okay
now
go
build
the
docs
in
a
static
site
that
doesn't
doesn't
need
this
deeper
level
of
infrastructure
and.
A
Mm-Hmm
yeah
and
we'll
need
to
play.
There's
there's
some
like
architecting.
We're
gonna
need
to
figure
it
out
in
this
website,
prototype
repo
to
make
that
happen.
I
know
a
few
other
open
source
documentation
sites
just
went
the
mono
repo
route.
So
it's
it's
possible
that
we
can,
in
this
one
location
have
pretty
well
defined.
A
Well
defined
projects
that,
like
this
one
just
builds
the
API
documentation
this
one,
it's
just
the
Gatsby
site
and
we
have
something
unified
together,
they'll
spit
out
the
production
thing
that
we,
you
know,
actually
get
up
onto
a
web
server
and
post
the
end
of
the
day.
It's
all
static
content,
whether
you
run,
though
there's
JavaScript
or
not
so
yeah,.
B
A
Yeah
it'll
be
interesting
if
anyone's
interested
in
coming
up
with
a
few
proposals
for
how
we
could
approach
that,
like
I,
feel
free
to
to
open
up
an
issue
with
with
a
few
ideas
on
where
we
can
go
with
that,
because
there's
also
some
really
cool
stuff.
We
can
do
with
the
API
documentation
page
that,
depending
on
where
we
want
to
take
the
API
Docs
and
what
they
do
we
have
available
for
us
and
like
in
the
longer
term,
I,
don't
really
know
what
makes
sense
best
for
that.
But
you
know
there's.
If
you
go.
A
If
he
can
make
it
because,
like
he
has
so
much
historical
context
on
on
all
the
website
stuff,
it
would
be
amazing
to
have
in
here
and
actually
has
already
been
helpful
with
like
trying
to
figure
out
scoping
for
how
the
heck
I,
you
know,
is
gonna
work.
We
need
a
spin-off
meeting
with
with
Ben
and
folks
to
talk
details
about
that,
so
you
might
want
to
actually
when
in
doubt
make
an
issue
for
it
right.
I'm
gonna
make
a
new
issue
for
just
for
me
to
make
a
new
or
make
a
make
a
meeting.
A
A
A
A
C
C
A
Your
hands
dirty,
that's
a
yeah,
it's
a
really
fun
set
up
to
like
the
the
readme
right
there
is
it's
pretty
straightforward,
good
directions
on
how
to
get
it
spun
up.
Apparently,
you
do
have
to
use
yarn
I'm
sorry
journey,
but
nobody
yeah
yeah,
just
dive
in
and
start
thinking
about
how
we
can
improve
it.
All.