►
From YouTube: 2021-07-21-Node.js Website Redesign Meeting
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).
B
Welcome
everyone
today
is
july.
21St,
welcome
to
another
website,
redesign.
C
B
B
Yeah,
it's
in
a
couple
issues
so
I'll.
C
B
B
It
looks
like
something
our
agenda
didn't
get:
auto-populated,
that's
okay,
yeah,
so
first
one
1561
is
dad.
Thomas
he's
been
pretty
active
lately
and
I
think
from
from
that
issue,
there's
a
bunch
of
enough.
We
have
a
majority
as
far
as.
B
I
have
no
issues
with
that.
Actually
I
I
created
the
issue,
so
I
would
like
to
join
and
then
the
other
one
is
rodent.
He's
also
a
I
think,
he's
already
on
package
maintenance
working
group,
so
he
would.
He
also
does
quite
a
bit
of
reviews,
so.
B
Yeah
yeah
and
he
nominated
himself
that
I
forgot.
B
B
So
I
think
the
next
step
would
be
according
to
the
to
the
documentation
in
the
readme.
So
if
no
there's
no
objections,
then
we
can
ask
somebody
from
comcom
to
add
these
two
users
to
our
watching.
B
We
can
update
and
then
numbers.
B
Yeah,
okay,
so
michael
we
were
going
to
discuss.
B
Let's
know
how
we
should
do
this,
should
we
just
like
go
through
page
by
page
like
and
maybe
take
some
notes
in
the
factory
created
a
few
weeks
ago.
A
I'll
stop
sharing
it
just
one
person's
thoughts
like
I
haven't
necessarily
you
know
delved
into
it
in
too
much
detail
or
given
a
lot
of
deep
thought
or
represent
a
bunch
of
other
people,
but
joe
kind
of
said:
hey
he'd,
like
somebody
to
come
and
give
some
feedback
so
happy
to
do
that
as
long
as
it's
it's
in
the
hey,
it's
just
my
my
opinion.
Don't
don't
read
more
into
it
than
that,
so
here
yeah
I
can
share,
and
where
are
we.
A
Right,
so
this
is
the
old
one.
This
is
the
new
one.
I
guess,
like
you
know
from
my
my
personal
perspective,
some
of
the
things
that
are
like
you
know
where
I
know
are
most
actively
used
or
like
certainly
the
downloads.
A
A
A
A
I
do
like
some
of
the
the
things
here
where
it's
like
you
know,
it's
it's
and
just
looking
flipping
back
and
forth
to
like
here
like
this
is
fairly
busy,
and
this
is
still
yeah.
So
I
mean
that's.
A
A
B
B
Yeah,
I
think
the
intent
was
if
the
hexagon
is
filled
in
then.
B
C
B
16,
you
see
that
only
the
current
is
filled
in
and
none
of
the
other
ones
are
filtered
because
node
16
is
not
is
not
lcs
yet.
A
A
Oh
that's,
not
current,
oh
wait
a
sec,
so
I
can
understand
it,
but
it
took
me
some
time
to
kind
of
understand
it,
whereas
if
it
was
just
like
the
you,
the
names
might
need
to
be
a
bit
different
like
you
know,
there's
lts
and
then
it
could
be
lts
maintenance
and
then
end
of
life
or
something
right,
but
that
that
would
be
like
if
I,
if
it
was
just
the
one
filled
in,
I
would
like
yeah.
Okay,
I
exactly
know
what
you're
getting
at
there.
A
A
A
A
B
Oh,
so,
if
you
scroll
down
a
little
more
so
like,
if
you
click
on
like
note
14,
you
would
expect
to
see
like
more
details
about
node
14
in
this
table.
B
A
B
I
think
I
I
agree.
The
the
top
half
of
the
bottom
half
are
kind
of
duplicate,
showing
the
same
information
with
the
initial
release,
active
maintenance
and
life.
B
C
B
It
shows
the
different
hexagon
information
it
doesn't
affect
the
table
down.
B
A
B
Where
you
can
download
it
yeah,
it's
a
different
view.
B
Yeah,
this
is
like
on
the
original
site.
There's
a
releases
page
somewhere
right.
A
B
A
B
Well,
the
additional
installers
are
the
same
thing
as
if
you
were
to
click
on
where
it
says
under
release.
You.
C
B
A
Sure
yeah
yeah,
I
mean
I
think
I
would
move
this
section
to
write
underneath
the
down
like
downloads
and
then
additional
downloads,
because
honestly,
like
depending
on
the
user,
I
I
never
use
the
installers
and
I'm
always
looking
for
these.
So
having
all
the
downloads
together
and
it's,
I
guess
it
would
kind
of
be
the
lts
and
current
downloads
right
and
then
this
is
almost
like
additional
releases.
B
B
I
think
we
can
probably
add
that
in
the
as
like
another
row
like
after
linux,
like
we
could
add
unofficial,
I
think
when
I
made
this,
I
was
following
the
original
design
right,
so
I
didn't
include
it
because
I
I
made
the
assumption
that
the
original
design
was
what
was
improved.
A
A
A
B
A
Person
don't
ask
me,
I'm
the
stick
and
stick
and
stick
drawing
person,
but
right,
yeah
yeah,
like
the
thing
I
the
thing
that
strikes
me
is
like
this
page
is
actually
nice
and
concise.
A
Like
I
don't
need
to
scroll
up
or
down.
You
can
see
everything
you
know
you
can
quite
easily
get
to
the
the
what
you're
likely
trying
to
get
to
which
is
like.
I
either
want
one
of
the
installers
click.
Click
click
likely
the
lts
one,
which
is
the
default
or
one
of
these
other
ones
right,
whereas
even
like
here,
I'm
gonna
need
to
like
I
just
I
gotta
scroll,
I
gotta
click
and
I
gotta
click
again,
so
it's
added
another
click
to
the
to
the
the
process.
A
Just
something
to
think
about
in
terms
of
like
I
don't
know
how
you
change
that,
but
like
is
it
it's
kind
of
like?
Is
it
worth
having
a
click
here
versus
just
having
them
on
the
side,
because
it
wouldn't
add
any
more
space
right
right.
A
I
don't
know
yeah.
I
know
I
know
that,
like
as
the
as
the
as
a
the
stick
person,
the
extra
click
over
over
overrides
the
like
visually.
This
is
very
pleasing,
but
so
anyway,
one
one
type
of
user.
Well,
we'll
value
that.
A
A
Yeah
so
downloads,
that's
one
like
you
know,
that's
one.
I
use
a
lot
security.
Let's
look
security
is,
I
guess
there
isn't
a
security,
it's
actually
down
at
the
bottom.
A
A
B
A
B
Yeah
msi,
if
you're
all
interested.
A
A
A
A
B
Yeah,
the
content
is
a
copy
paste
from
the
original
okay
yeah.
A
A
B
Yeah,
maybe
inside
the
markdown
file
it
had
a
table
content
section
or
something
and
that's
now,
it's
being
parsed.
D
Mike
out
of
curiosity,
though,
usually
the
left
navigation
is
where
I
would
find
the
table
of
contents.
I
wouldn't
find
it
on
top.
So
I
think
when
the
question
comes
in
is
we're
just
moving
functionality
from
one
place
to
another?
The
question
is:
what's
the
purpose
of
the
left
nav
right,
because
otherwise
the
table
of
contents
should
actually
just
be
a
sub
category
within
the
left.
C
D
So
the
question
is,
do
you
know
I'm
not
a
you
experience
person
a
ux
experience?
I
just
know
that
we
we
don't
want
both
right.
We
just
want
one
or
the
other,
because
now
we're
repeating
functionality
that
we're
just
moving
from
one
place
to
another.
A
D
If
I'm
making
sense
and
the
other
thing
on
the
left
now
out
of
curiosity,
if
in
doubt,
if
there's
not
a
a
real
order
of
the
preface
or
you
know,.
D
Reason
for
order,
then,
by
default,
should
be
alphabetical
right
so
about
whatever
you
know:
research,
privacy
policies,
but
the
other
thing
is
like
where
I
see
the
policies
and
everything
and
that
that's
all
under
governance
right,
those
those.
So
those
could
be
categorized
right.
So
I'm
not
sure
exactly
when
the
person
or
people
decided
how
the
purpose
of
the
left
nav
and
how
they
wanted
to
make
the
user
experience.
But
I'm
not
sure
I
thought
it's
clear
on
the
newer
version,
as
it
is
clear
on
the
previous
one.
B
If
you
look
at
the
nodejs.org
under
getting
involved,
those
those
are
where
those
pages
came
from
and
what
we
did
was
we
took
those
markdown
files
from
each
one
and
just
recreated
the
file
in
this
style.
So
that's
all
we
did.
We
didn't
think
about
ux
or
anything.
It
was
just
basically
copy
pasta
of
the
existing
fight
into
the
new
one,
so
yeah
totally
open
to
like.
A
With
me
like,
there
is
a
nav
already
here
and
there's
space,
so
it
does
seem
more
natural
for
me,
for
when
you
click
on
security
reporting
that
then
the
table
of
contents
would
pop
up
underneath
that
and
that
it
doesn't
take
up
space
in
your
in
your
actual
page
and
it's
it's
sort
of
a
natural
you're
already
going
into
something
so
then
having
it
pop
up.
Something
where
you
could
then
go
directly
actually
makes
a
fair
amount
of
sense.
To
me.
C
Am
I
audible
hello,
hi
yeah
hi,
so
I
was
saying
that
the
table
of
contents
is
actually
generated
from
the
headers
in
the
markdown
right,
so
any
file
that
does
not
have
any
hashtag
like
headers.
It
won't
have
a
table
of
contents
and
it's
actually
consistent
with
the
learn
page.
So
if
you
go
to
the
learn
page,
every
page
in
there
has
a
table
of
contents
by
default
and
we
can
move
that
into
sidebar.
Actually
so
for
consistency
like
will
it
be
good
if
we
move
table
of
content
to
the
side.
A
A
A
A
A
A
A
You
know,
I
mean
like
the
the
download
one.
Well
yeah
we,
you
know
this
is
a
minor
thing
which
we
can
fix,
but
that's
just
an
opportunity
for
somebody
to
say:
oh
wait,
a
sec
that
doesn't
look
quite
right
and
getting
a
lot
of
discussions
so
like
some
of
them,
I
think,
are
quite
a
bit
closer
like
I
guess.
Documentation
is
the
same.
B
A
A
A
B
So
one
thing
I
was
curious
about
is
like
the
coded
learn.
I
don't
think
we
included
that
and
from
looking
at
that
page
it
hasn't
been
updated
in
quite
a
while.
So
is
that
even
still
a
thing.
A
Yeah,
we
definitely
still
like
that's
still
something
we
try
and
do
this
last
couple
years,
obviously
hasn't
been
so
good
for
them,
but
we
did
a
virtual
one.
A
A
How
this
might
be
a
good
time
to
to
basically
say
you
can
add,
you
can
add
some
but
we're
starting
from
from
scratch
right
to
make
sure
they're
live
or
they're
fresh
right.
A
A
You
know
when
it
comes
to
when
it
comes
to
say,
hey
we
want
to
switch
over
that
may
be
easier
than
you
know.
It's.
It's
kind
of
like
with
code
reviews,
a
huge
review,
it's
very
hard
to
get
people
to
look
at
all
the
things
and
consume
it
all,
and
you
either
end
up
in
one
or
two
things
like
massive
discussions
about
all
sorts
of
side,
things
or
no
comments
at
all
right.
So
that's
where
you
know.
A
C
A
A
I
personally
just
again
my
own
feeling
I
like
get
involved
better
than
community
like
I
might
know
that
I
want
to
get
involved.
Do
I
care
about
the
community?
Maybe
right?
So
it's
it's
kind
of
the
same
thing,
but
it
depends
on
what
you're
looking
for
so
again,
just
one
one
person's
sort
of
thought
in
terms
of
title
or
whatever,
but.
B
Right
and
one
of
the
things
that
joe
wanted
to
try
and
push
was
keeping
the
old
urls
kind
of
working
so
like
right,
we
should
be
able
to
do
still
do
like
node.js.dev
slash,
get
involved.
B
A
A
B
Well,
no,
it's
we're
kind
of
doing
that
in
some
places
like
on
the
the
the
data
that
we
get
from
the
download
page
like.
A
B
B
B
C
A
A
B
On
the
homepage,
I
had
a
question
for
you
sure,
really
anyone
what
are
your
thoughts
on
having
like
other
in
the
original
design.
If
you
scroll
back
down
a
little
bit,
there
was.
C
B
Used
so-and-so
companies
also
use
node,
it's
not
here
because
we're
not
using,
we
didn't
include
it,
but
the
design
has
like
a
netflix
logo.
Microsoft
logo
ibm
like
these
companies
are
using
node.js.
So
the
question
is:
should
we
even
include
like
logos
or
it's?
You
know
it's
like
a
common
way
for
startups
or
even
companies
to
show
social
proof
of
you
know.
These
companies
are
using
node.js
and.
A
I
like
that
personally,
the
thing
I
don't
know
like
do
any
of
those
other
ones
like.
I
know
some
companies
like
for
ibm,
for
example,
I'm
not
I'm
not,
as
I
haven't
checked
it
red
hat,
but
like
they're
they're,
pretty
picky
about
the
logos
so
like
if
I
just
pr
it
in
I'm
not
supposed
to
do
that
right,
I'm
supposed
to
get
approval.
B
B
So
then
I
suggested
why
don't
we
just
include
opengs
logos
like
express
then
what
else
there's
a
few
others
that
I
there's
some
open
issue
score
for
getting
permission
from
the
maintainers,
but
then
they're
under
opengl,
so
who
owns
the
logo
and
the
ip
of
that
stuff.
B
A
B
A
Yeah,
like
I,
wouldn't
I
wouldn't
mix
it
in
this
switch
over,
but
I
I
personally
would
really
like
to
see
that
I
think
we
would
just
need
some
sort
of
like
here's
the
process
we
follow
for
landing
those
pr's
and
it's
got
to
include
some
sort
of
assertion,
or
you
know
we
have
to
figure
out
what
does
it
take
for
us
to
be
comfortable
that
we've
gotten
the
okay
to
use
that
logo.
B
So
I
I've
chatted
with
brian
gray's
last
name.
B
Yeah
yeah
from
in
slaps,
I
I
believe
we
have
approval,
we
just
need
to
do
it,
but.
A
Yes,
yeah,
it's
maybe
less
so
than
a
startup,
but
I
personally
would
still
be
useful
for
me
like
within,
I
still
use.
There's
a
there's.
The
2017
ser
user
survey
included
a
slide
with,
like
you
know,
I
don't
know:
50
logos
of
companies
using
node
and
I
still
like
when
I'm
talking
to
people
and
evangelizing
within
you
know,
within
my
own
company
and
within
customers
and
stuff.
A
It's
it's
really
handy
to
be
able
to
say,
look
at
all
these
people
who
are
using
it
right
and
right,
yeah
and
so,
but
but
as
a
as
a
you
know,
once
once
the
new
website's
in
place.
That's
something
to
think
about,
or
you
know,
versus
a
let's
try
and
figure
that
all
out
and
make
it
a
blocker
for
the
first
one
right.
A
B
Yeah,
I
believe
that
if
you
are
on
mac,
you
would
auto
select
mac
os.
Just
like
this
detects,
your
os
yeah.
B
Okay
and
then
the
re-documentation
button
actually
takes
you
to
the
the
current
package,
manager's
page,
which
is
all.
A
B
Like
yeah
yeah,
actually,
the
certification-
we
don't
have
any
link
on
that.
So
I
didn't
didn't
know
how
to
include
that
or
where
to
include
it.
A
We
just
need
a
link,
and
you
know
they
may
want
to
spend
a
little
bit
of
time,
make
it
look
like
something
that
fits
in
a
little
bit
more
or
just
leave
it
the
way
it
is.
I
guess,
because
it's
a
different
site
but,
like
I
suspect,
all
of
these
that
are
across
the
top,
somebody
might
say:
hey
wait
a
sec.
B
Yeah
on
the
plot,
one
thing
I
think
last
week
we
talked
about
was
right
now
the
blog
is
mostly
just
like
announcements,
yep
security
updates
and
things
like
that.
Not
really
like
a
blog
article
when
you
think
of
blog,
I
think
of
articles.
B
Yeah,
I
I
think
right
now,
the
actual
blog
articles
are
medium
and
I
think
yeah.
You
mentioned
that
you're
trying
to
move
away
from
medium
to
to
actually
own
the
content.
A
B
It's
probably
both
I'm
not
really
sure,
there's
probably
that
but
then
a
medium.
I
I
think
when
it
first
started,
you
didn't
need
to
be
assigned
in
or
have
it
account
or
anything.
C
B
They're
starting
to
move
like
towards
like
a
pay-to-play
kind
of
a
system
where,
after
viewing
three
articles,
you
gotta,
you've
gotta,
say
yeah,
so
that
can
be
like
a
limitation
too
yep.
A
D
D
Well,
I
just
I
don't.
I
just
know
that
most
people
use
medium
and
other
services
like
that,
mainly
so
that
they,
when
they
add
post
things,
that
things
are
not
only
emailed
out
where
email
services
are
used
because
somebody
subscribed
to
it,
but
things
like
rss
feeds
and
all
those
will
be
updated
because
timely
information
came
out
and
then
our
news
services
that
are
monitoring
that
would
know
something's
changed
so
that
that
would
be
my
only
concern
as
a
system
requirement.
Not
necessarily
you
know
what
platform
and
how
we
do.
It.
D
A
D
D
The
only
concern
that
I
have
is
that
we
might
have
to
remove
the
word
chocolatey
specifically
or
is
chocolately
our
official
way,
because
a
lot
of
people
don't
necessarily
use
chocolaty
to
install
in
this
shell,
a
lot
of
people
using
other
things
like
scoop,
or
you
know,
using
powerscript,
directly
and
stuff
like
that.
So
I
don't
know.
B
D
B
Right
so
we
went
with
chocolaty
here
because
I
think
that's
I
think
I
spoke
with
tierney
about
it's,
probably
the
most
common
to
use,
but
and
then
for
same
with,
like
nvm
nvm,
we
selected
instead
of
like
brew
or
n
or
valence,
because
it's
under
the
open,
js
foundation
and
it's
probably
also
the
most
common
commonly
used
at
least
for
osx,
I'm
not
sure,
really
sure
about
linux.
B
D
B
Yeah
brew
is
actually
not
recommended.
According
to
jordan,.
D
D
Least,
put
a
clarification
if
we're
aware
out
to
some
link
to
an
article
about
it.
B
Yeah
yeah,
I
guess
I
would
point
to
the
read
the
documentation,
but
because
I
had
that
lead
you
to
like
the
all
the
possibilities
like
right.
B
Yeah
like
a
lot
of
the
possibilities-
maybe
not
all
so
yeah
if
you
click
on
the
re-documentation
button
it
will
and
if
you're
like
on
the
windows,
it
takes
you
to
the
united
states.