►
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
Thanks
everybody
for
joining
another
episode
of
the
website.
Redesign
committee
today
is
the
7th
of
july.
B
Our
year,
2021
yeah
like
we're
saying
there
are
there,
aren't
many
issues
on
the
agenda,
so
we'll
maybe
touch
on
that
and
then
just
kind
of
take
a
look
at
how
things
are
you
want
to
take
over
ben
halverson.
C
Yeah
sure
so
the
agenda
are
the
issue
number
one.
Four
five
one
is
issue
opened
by
me:
called
homepage
logos
and
it's
a
question.
Should
we
add
logos
to
the
home
page
by
bringing
this
up,
because
in
the
design
that
we
have
a
bunch
of
like
big
name
logos
on
it,
of
course
we're
not
going
to
use
those
beginning
logos
without
their
permission.
C
B
Yeah,
I
don't.
I
don't
have
a
strong
opinion
on
this.
I'm
trying
to
pull
up
the
site
to
see
how
it
looks
just.
B
Without
yeah
I
mean
no,
it's
mature,
I
don't
think
we
really
need
to
be
like
boasting
about
who's
using
it
and
where
necessarily
so,
I'm
okay,
with
just
kind
of
you
know
tabling
it,
and
you
know
we
can
revisit
it
later.
We
can,
you
know,
do
some
sort
of
homepage
review
at
a
later
date
and
I
say
just
leave
it,
as
is
okay,.
B
Cool
is:
are
there
I
haven't
looked
at
the
repo
much
lately
just
trying
to
get
back
into
the
swing
of
things
are.
Are
there
any
other
things
ben
that
you
think
or
or
anyone
else
frankly
that
that
we
should
look
at
or
consider
or
think
about
or
talk
or
whatever
discuss
hello.
A
B
Yeah,
so
let
me
just
reiterate
make
sure
I
understand
so
if,
if
I
understand
the
question
correctly
you're
asking
about
like
company
logos,
yeah
yeah,
I
think
we
had
talked
about
that
in
the
past
too.
Right
is
that
maybe
that's
what
you're
referring
to
as
well?
B
And
I
don't
know
what
the
decision
was
there
per
se,
but
I
think
we
decided
to
keep
it
simple
for
now
and
just
try
to
get
the
the
rest
of
the
site
done
and
then
you
know
we
can
evaluate
whether
we
want
to
you
know
reach
out
to
companies.
I
think
yeah.
B
I
think
it's
an
interesting
idea
and
I've
I've
seen
graphics
with
you
know.
Dozens
of
you
know
big
name
companies
using
node.js,
but
that
gets
tricky.
You
know
you
gotta
make
sure
you
get
every
everything
approved
and
but
you
know
it
could
be
the
sort
of
thing
that
we
set
up,
something
that
you
know.
B
If
you
want
your
company
to
appear
here,
you
know
we
get
the
approval
and
then
we
can
just
kind
of
rotate
through
different
companies
or
something
we
can
have
fun
with
it
later.
But
I
think
that's
more
think
of
that
more
of
as
an
enhancement
and
we'll
just
get
the
rest
of
the
stuff
done.
First,.
C
I
guess
there
was
another
issue,
I
didn't
add
the
label
to
it.
I
created
it
about
eight
days
ago,
it's
titled
automate
banner
display
on
home
page.
It's
issue
number
1502.
C
So
right,
right
now
node.js.org
every
once
in
a
while.
They
they
have
announcements
and
display
a
banner
of
some
of
the
announcement
right
now
the
announcement
is
there's
new
security
updates
yeah.
So
what
I
was
looking
to
do
is
whenever
that
happens
also
just
display
the
same
message
on
node.js
in
a
automatic
magical
way
automated
way,
so
there's
a
little
bit
of
discussion
on
how
to
do
it
like
using
github
actions,
and
we
need
to
figure
out
some
kind
of
data
structure
and
things
like
that
yeah.
B
Yeah,
it's
not
I.
I
agree,
it
is
an
enhancement,
but
I
think
it's
a
good
one
to
you
know.
If
somebody
wanted
to
work
on
it,
I
don't
think
it's
a.
B
I
think
it
would
be
a
good
use
of
time,
and
I
I'm
reading
trot's
rich's
comment
here
and
makes
sense
to
me
and
having
rich
say
this
would
be
an
improvement
for
both
sides
and
we
could
iterate
on.
It
sounds
good
to
me.
C
All
right
so
I'll,
I
can
add
a
help,
wanted
tag
today.
C
D
I
think
in
general,
just
on
the
good
first
issue
note:
the
scope
of
this
is
slightly
too
large
for
that
just
you
know
just
because
it
touches
on
doing
things
like
being
a
github
action,
there's
just
stuff
like
once.
Once
you
take
something
good
first
issue,
you
might
get
like
people
early
on
in
their
stage.
You
know
phases
of
like
being
a
developer,
so
you
know
they
might
need
a
lot
of
hand
holding.
D
A
Getting
this,
I
had
a
question
like:
are
we
open
to
making
some
large
changes
in
the
northeast.
A
C
C
B
Yeah,
but
what
is
what
that's
interesting?
What
is
what
was
trot
suggesting,
though,
is
that
sort
of
similar
I'm
trying
to
get
back
to
that
issue
here.
It
is
because
I'm
not
sure
their
approach
is
the
best
approach,
so
if
there
is
an
opportunity
to
make
it
a
little
better,
I
think
that's
good,
I
mean
basically
their
thing
is
you
have
some
text.
B
The
whole
text
is
a
link
and
that's
the
banner,
but
if
we
were
able
to
perhaps
take
a
small
bit
of
markdown
or
something
and
maybe
have
two
links
in
it,
that
that
would
be,
I
think
better.
C
C
Yeah,
so
it's
published
now
so
if
we
want
to
know
gs.gov
slash
community,
it
does
load.
E
B
B
The
community
link
in
the
header
on
nodejs.dev-
oh
wait;
no,
it
does
work.
Weird,
it
didn't
work
at
first.
Try
try
refreshing
punish
yeah.
Maybe
you
might.
B
One
bug
that
I'm
seeing
that
I
don't
think
is
you
know
critical.
Is
that
when
you
scroll
to
the
bottom
of
the
community
page
the
very
bottom,
the
left,
nav
bar
slides
up
a
little
bit
and
and
maybe.
A
B
Yeah,
I'm
sorry
minis,
it's
probably
a
combination
of
your
microphone
and
my
really
bad
hearing,
but
I'm
having
trouble
discerning.
What
you're
saying
am
I
already
well
now
yeah,
that's
a
little
better.
Thank
you.
A
B
All
right,
so
it
seems
like
in
the
feature
parity
board
here
we
can
move
community
to
done
implemented,
so
I
will
do
that.
B
B
So
really,
it
feels
to
me
like
and
I'd
like
to
spend
a
little
more
time
kind
of
reviewing,
but
it
feels
to
me
like
we
should
start
to
figure
out
perhaps
what
we
think
about
the
news
and
blog
localization
and
docs
and
start
to
engage
with
the
current
team,
perhaps
or
anyone
who's
you
know
if
there
are
teams,
that's
specific
to
any
of
these
engage
with
them.
B
So,
like
you
know
open
source
like
localization,
you
know,
I
don't
know
if
the
international
internationalization
team
would
be
interested
in
helping
us
there
or
anything.
I
I
think
there
was.
There
are
some
people
who
are
on
top
of
docs.
You
know
so
we
may
want
to
kind
of
rope
them
in
and
start
to
maybe
move
these
other
things
forward
as
well.
D
Yeah,
I
think,
circling
circling
the
different
working
groups
together
with
you
know
a
common
goal.
So
for
this
I
think
you
know
the
the
goal
for
the
website
would
be
a
release.
Did
I
lose
you
all
right
for
us
for
a
second
okay?
So,
like
the
you
know,
the
common
goal
would
be
like
a
release,
for
you
know
the
website.
So
what
does
it
look
like
to
do
a
release
from
the
perspective
of
this
group?
D
D
D
So
in
the
documentation
I
mean
there's
other
stuff
that
the
internationalization
team
would
love
to
talk
about.
You
know
with
someone
from
the
nodejs.org
doc,
so
we
need
to
get
somebody
over
on
that
side
anyways,
but
I
think
like
coordinating
these
efforts
together
or
conversations
or
relevant
stakeholders,
I
think
will
be
really
good.
D
Instead
of
you
know,
kind
of
dragging
it
out
in
silos,
I
think
we're
kind
of
at
that
inflection
point
yeah
makes
sense
to
me
so,
like
I
guess
it's
sort
of
it's
not
really
an
issue,
but
is
do
we
have
like
a
I
didn't
look
closely.
Have
we
defined
like
a
milestone?
D
You
know
like
for
like
a
release
or
anything
like
that
for
the
future.
Like
you
know,
are
we
at
the
point
where,
because
to
me,
like
you
know,
the
release
would
be,
let's
have
consensus
on
feature
parody
and
then,
let's
you
know,
let's
get,
let's
figure
out
what
we're
gonna
do
with
docs
and
then
let's
get
you
know,
let's
get
it
internationalized.
So,
like
those
those
three
things
seem
like.
If
those
are
all
in
place,
then
it
would
be
like
kind
of
go
time.
D
You
know,
but
you
know
that's
that's
just
sort
of
like
a
broad
topic.
I
know
we've
been
plugging
away
at
a
lot
of
things
here.
You
know
all
to
get
all
those
three
things
in
place.
Like
you
said,
there's
gonna
be
different
stakeholders
coming
together
to
do
it
or
you
know
making
sure
that
we're
doing
it
right.
So
I
just
think
it's
something
worth
discussing.
I
don't
know
if
you
want
to
discuss
that
right
now
or
save
that
for
another
time,
but.
B
What
just
so
I
understand,
what
are
you
asking
if.
D
We
should
discuss
yeah
just
like,
should
we
define
a
release
or
like
requirements
for
a
release.
B
I
mean
my
first
instinct
is
again
like
feature
parody
and
now
that
so
the
first
thing
that
comes
to
mind
when
I
think
of
that
is
like
localization.
D
B
And
you
know
we
could
perhaps
link
to
the
old
blog
and
the
old
and
the
you
know
current
implementation
of
docs
until
we
get
those
two
things
built
yep
which
I
don't
feel
great
about.
But
I
mean
if
we
were
in
a
hurry,
which
I
don't
think
we
are
but.
D
There
was
more,
this
was
sort
of
a
this
is
like
half
of
this
is
like
rhetorical,
but
also
just
having
a
desire
to
want
to.
You
know
want
to
get
this.
You
know
out
there
at
the
same
time,
so
maybe
there's
some
pressure
just
in
the
fact
that
you
know
we
don't
want
to,
we
don't
want
to
drag
it
out
too
long.
I
mean
the
dream
of
the
like
sort
of
the
dream
of
this
right
is
that
we
would.
D
This
would
be
replacement
for
you
know
nodejs.org,
so
I
think
anything
that
we
can
do
to
sort
of
give
us.
You
know
a
road
map
to
being
that,
I
think,
like
having
a
defined
having
a
defined
you
know,
release
would
be
an
obvious
vector
for
being
able
to
have
that
conversation
with.
You
know
like
the
people
who
are
who
are
supporting
or
maintaining
a
nodejs.org,
so
being
able
to
say,
like
you
know,
this
is
what
we
foresee
being
a
viable
candidate.
You
know
for
that.
D
I
think
could
be
a
place
to
start
that
conversation
and
then
it
you
know,
depending
on
how
that
goes
or
whatever
time
frames
will
always
change.
But
you
know
it's
just
like
providing
that
kind
of
definition.
I
mean,
I
think,
as
we've
been
talking
about
these
building
blocks,
you
know
these
three
sort
of
things
you
know,
like
you
said:
localization
docs,
you
know
and
then
consensus
on
like
feature
parody.
D
You
know,
I
think,
are
like
three
columns
of
like
check
check
boxes
for
for,
like
a
solid
release.
Yeah.
B
Yeah
yeah,
it's
it's
a
good
question
ben.
B
I
honestly
don't
know
if
it's
premature,
though
like
should
we
should
we
just
start
talking
with
the
team
start
to
see
what
the
work
is
going
to
look
like
and
I'm
always
nervous
about.
You
know,
for
lack
of
a
better
term
like
a
deadline
for
for
open
source
work.
D
Yeah
yeah
now
and
I'm
not
suggesting
that
we
create
one.
I
guess
what
I'm
saying
is:
how
do
we
foster
that
conversation
with
another
group
with
a
unit
of
work?
That
makes
sense
so
it's
like
if
we
say
this
is
what
we
foresee
to
be
the
things
that
we
need
for
this
to
be
a
reality.
You
know
like
a
reality
or
like
something
that
we
would
release.
D
B
Yeah
yeah,
I
don't
know
if
this
is
what
you're
talking
about
exactly
but
like.
I
think
it
would
be
good
to
have
those
things
completed
for
launch
the
localization
news,
blog
docs
and
making
sure
like
links
are
all
good
and
stuff.
D
Yeah-
and
I
do
I
do
too-
that's
that's
part
of
what
I'm
getting
at.
I
think
the
other
part
is
that
you
know
we
can
operate
in
our
own
group
and
kind
of
do
our
own
thing
like
we've
been
doing
but
like
we
were
just
talking
about
like
having
we're
kind
of
at
that
inflection
point
where
we
need
to
correlate
with
these
other
groups
that
have
ownership
over
those
parts.
D
So
if
we
just
had
some
kind
of
definition
of
to
date,
what
we
foresee
being
where
we
want
to
take
this,
that
could
be
a
great
you
know
that
could
be
a
very
clear
indicator
for
them.
On
like
oh,
this
is
you
know,
this
is
what
they
have.
This
is
what
they've
been
doing.
This
is
what
they.
This
is.
Where
they're
going,
how
you
know
and
then
then
they
can.
You
know
people
from
other
groups
can
provide
their
insights,
clearly,
understanding
our
where
we're
at.
B
Yeah
yeah
yeah.
It's
interesting.
I
think
you
know
what
I'm
thinking
about.
I
think
it's
along
the
same
lines
is
perhaps
we,
as
a
team
should
start
to
document
the
status
of
where
we
are.
You
know
what
we're
thinking
these
other
buckets
kind
of
dig
into
those
a
little
bit.
You
know,
I
think
you
know
both
you
open
source
and
you
ben
halverson,
have
thoughts
about
the
docs
and
the
localization
stuff,
and
luckily
gatsby
is
a
blogging
platform.
So
getting
getting
that
going
should
should
be
okay.
D
B
So
I
mean
maybe
if
this
is
along
the
lines
of
what
you're
thinking
about
ben.
Maybe
we
should
start
like
a
hack,
md
file
yeah.
The
the
team
here
can
contribute
to
scoping
out
where
we
think
we
are
essentially
like
putting
a
best
face
on
on
what
we
have
here
to
give
to
the
other
stakeholders
to
start
to
have
the
conversations.
D
Absolutely
yeah
and
that
that's
all
I'm
getting
at
is
like
yeah,
let's
put
our
best
foot
forward,
let's
create
like
a
place
for
people
to
clearly
see
what
we've
done,
because
you
know
it's
good.
I
mean
it's
good,
like
we
kind
of
know,
you
know
where
we're
at
and
what
needs
to
be
done
in
this
silo,
but
other
you
know.
Other
people
might
have
assumptions.
If
we
don't
define
them.
C
One
thing
I
wanted
to
bring
up
was
the
blog.
The
backend
portion
of
it
from
the
gatsby
side
is
is
done.
I
think
it
was
that
did
that.
So
all
we
need
is
some
option
files
and
it
will
automatically
create
some
blog
posts.
C
B
C
C
Right
yeah,
we
probably
if
if
they
do
have
a
rss
implementation,
because
there's
a
blog
well
part
of
a
block.
More
of
like
a
news
updates
kind
of
thing.
D
C
Right
so
if
yeah
that's
the
thing,
then
we
probably
want
to
also
implement
that.
C
And
then
also
an
issue
since
right
now,
maybe
just
then
points
to
the
updated,
the
old
blog
page,
not
the
current
one.
A
Actually,
before
that,
we
need
a
little
change
to
the
back
end,
that,
on
the
on
the
on
the
side,
I'm
saying
that
there
are
categories
for
the
blocks
and
that's
not
implemented.
C
B
That
is
a
very
good
question
and
it's
a
question
that
we
have
talked
about
on
a
variety
of
people,
a
variety
of
contexts
I
think
in
an
ideal
world
we
would
have
a
more
full-featured
blog
available.
We
would
stop
thanks
to
tilford
for
joining.
Oh
there.
He
goes
because
I
don't
we're
not
really
using
medium
anymore
and
even
if
we
switch
to
like
dev2
or
something
I.
B
I
have
always
been
of
the
mind
that
having
your
own
blog
is
best-
and
you
can,
you
know,
syndicate
it
out
to
these
other
platforms,
but
really
own
your
own
content.
You
know
great
and
it's
something
we've
talked
about.
B
I
frankly
think
there
should
be
a
content
team
that
works
on
that
and
I
think
we've
kind
of
tried
to
do
that
in
the
past.
So
I
don't
know
you
know
if
there's
really
an
appetite
for
that
necessarily.
B
But
you
know,
as
with
most
of
these
things,
I
think
we
should
just
focus
on
getting
the
news
aspect
working.
You
know
if
the
feature
to
be
able
to
categorize
blogs.
Is
there
great,
but
you
know
at
a
minimum,
just
implementing
what
is
currently
on
the
site
makes
sense
to
me,
but
I
I
would
love
if,
if
you
know
we
did
more
with
it
we'll
see
you
know
once
once
we
get
this
this
whole
damn
effort
done.
Maybe
some
some
people
have
some
time
and
we
can
contribute
there.
C
B
B
The
social
team
is
just
tierney
and
me
and
we
primarily
focus
on
twitter.
We
do
a
little
bit
of
linkedin
and
and
facebook,
but
very
very
little
really
just
and
even
with
the
twitter
stuff.
We're
kind
of
doing.
I
don't
want
to
say
the
bare
minimum,
but
we're
not
doing
a
lot.
I
would
want
to
be
doing
more,
but
you
know
been
pretty
been
pretty
busy
on
both
tyranny
side
and
my
side
I
mean
the
good
thing.
B
Is
we've
been
automating
some
of
the
things
you
know
some,
like
you
know,
regular,
build,
thank
you
tweets
and
and
those
sorts
of
things.
So
that's
been
good,
but
we
definitely
want
to
be
doing
more.
Hey,
davia,
hey
guys,
so
we're
just
chatting.
We
only
had
one
thing
on
the
agenda
which
we
discussed
and
are
kind
of
talking
more
about.
You
know,
generally
speaking,
that
we're
feeling
pretty
good
about
where
the
site
is
in
terms
of
all
the
low-hanging
fruit.
B
You
know
all
the
basic
pages
getting
them
and
what
we
essentially
have
left
is
the
the
localization
docs,
the
blog
and
news
aspects
and
and
then
like
finally,
just
making
sure
that
links
on
the
current
website
will
not
be
broken
onto
the
new
site
got
it.
It
just
created
an
issue
for
just
to
really
kind
of
make
it
clear
that
that's
something
that
someone
could
do.
B
I
put
the
help
wanted
tag
on
there
like
basically
just
going
go
through
and
look
at
all
the
links-
and
you
know
see
if
they
will
work
on
the
new
site
so
yeah
and
and
the
thought
there
divya
just
to
catch.
You
up
is
and
actually
I'll
say
you
know.
B
B
You
know
those
sections
that
I
just
mentioned
and
we
can
work
on
that
together
because
you
know
ben
halverson
has
ideas
about
docs,
open
source,
has
ideas
about
localization
and
basically
try
to
put
something
together
that
we
can
take
to
the
current
nodejs.org
team
and
the
docs
people,
the
local.
You
know
the
internationalization
team
and
start
to
you
know
soon
start
to
bring
people
into
the
fold
and
align
and
work
on
these.
These
these
remaining
chunks
of
work
and
try
to
get
things
over
the
finish
line.
E
Yeah
sure
I
think
that'll
be
good.
Let
me
know
when
you
guys
do
that
working
session.
I
would
love
to
have
a
be
a
part
of
it.
B
B
And
new
notes
do
I
need
to
no.
B
Redesign
cool-
I
will
share
this
here
and.
B
I
will
also
do
it
here
website
redesign
group.
Where
is
that.
B
D
B
Is
no
just.dab
is
that
some
sso.
B
B
All
right
cool
yeah-
I
mean
we
don't
have
to
spend
all
the
time
looking
at
this,
but
this
is
something
we
can
work
on,
asynchronously
and
then
rope
in
trots
and
and
other
folks
who
would
be
interested
in
and
starting
to
figure.
This
out.
B
Yeah
so
I'll
just
say,
current
status,
larger
efforts
still.
C
And
ensuring,
oh
sorry,
god,
oh
I
said
talk
about
this
one,
so
I
guess
there
already
is
one
brokenly
that
is
like
this,
so
node.js
dot
or
slab
community
is
actually
getting
involved.
I
think
it's
the
actual
link
getting
dash
involved,
whereas
we
we
don't
currently
have
that,
because
that
page
could
have
just
gone
away.
B
B
I
think
that
we
should
make
both
links
work
like
if
you
went
to
get
involved,
slash
get
involved
like
maybe
you
had
a
bookmarked,
it
would
go
to
the
community
page.
It
would
essentially
do
what
is
that
a
301
or
something
and
redirect.
B
I
have
to
assume
gatsby.
Has
that
feature
you
know.
I
know
I
know
you
can
declare
your
slug
and
stuff,
but
it
would
be
cool
to
not
only
have
our
slug
declared
but
like
alternates.
That
would
also
resolve
to
the
the
slug.
B
I
don't
know
how
that
works,
and
that's
kind
of
what
I
was
actually
about
to
say
too,
like
ensuring
link's
work
in
a
way
is
sort
of
a
bit
of
an
architectural
discussion
too,
because
I
think
you
know
there
are
some
things
that
we've
talked
about
recently
about
where
files
live
and
stuff
and
ensuring
that
they
kind
of
are
aligned
with
the
way
it
works
currently,
so
we
may
even
need
to
look
at
how
the
site
is
structured
currently
to
make
sure
that
it
does
sort
of
align
with
that.
B
I
don't
know
if
we
need
to
make
some
move
some
things
around
exactly
or
what
and
then,
of
course,
the
other
big
elephant
in
the
room
there
is
like
localization
needs
to
happen
too,
but
yeah
so
ensuring
there
are
no
broken
links,
isn't
as
simple
as
it
sounds.
A
Right
actually,
regarding
the
redirects,
the
react.js
at
org
site,
it
uses
netlife
redirects
for
such
type
of
things
like
it's
also
made
on
gatsby,
but
users
netlify
to
like
301
rearranged
kind
of
things.
So
are
we
using
any
we're
not
using.
C
Them
where
our
our
site
is
hosted
on
a
google
cloud,
ooh
cloud
bucket
and
that's
it
there's
no
internet
server
or
vm
or
anything
it's
just
since
it's
all
static
files
just
into
the
file
bucket.
A
B
A
A
B
Yeah
yeah,
okay
yeah
I
will,
I
will
close
the
other
one
as
a
duplicate.
I
created
this
one.
The
one
406
is
sort
of
like
a
guiding
principle,
but
I
think
it
is.
I
maybe
would
reword
that
title
and
then
we
can
just
use
this
existing
one
and
see
if
becky
does
jump
in
here.
So
I
will.
Let
me
let
me
do
that.
B
B
B
B
Cool
yeah,
I
mean
feel
feel
free
to
jump
into
this
dock
and,
and
you
know,
add
more
stuff.
I
will
put
some
more
notes
in
there
as
well
and
yeah.
This
is
a
good
starting
point
to
think
about
bringing
this
effort
to
other
groups
who
have
overlapping
interests.
That
are,
you
know,
currently
managing
the
live
site
or
aspects
of
it,
and
we
can
go
from
there.
B
Well,
I
got
12
more
minutes
left,
I
don't
know
if
we
want
to
just
call
it
a
wrap.
I
would
probably
just
start.
You
know,
keep
keep
working
on
the
stock
for
a
few,
but
whatever
you
all
want
to
do
yeah
and
we
can
even
leave
the
meeting
open
if
we
want
to
I'll
just
start
working
on
the
dock
and
we
can
chat
if
anybody
wants
to
whatever
whatever
you
all
want
to
do.
B
Cool
I'll
leave
it
running
but
feel
free
to
drop
anyone
or
or
or
not
whatever
you
wanna.
B
E
I
just
I
just
had
a
question
real
quick
about
the
docs
page.
I
thought
we
were
going
to
migrate
the
docs
from
the
existing
site
into
the
new
one
and
then
and
then
make
sure
that
it
is,
you
know,
formatted
and
styled
to
the
new
to
the
new
one.
So
how
are
we
gonna
do
that?
Because
do
we
do
we?
I
mean
I
right
now.
D
C
A
C
But
to
do
that,
we
we
need
some
markdown
in
the
markdown
files
or
some
front
matter
in
the
markdown
files
properly
parse
it
and.
C
To
do
that,
we
need
to
get
like
some
consensus
from
node
core
to
add
what
matter
to
the
markdown
and
that
might
be
challenging.
I
I
don't
know.
E
C
So
yeah,
when
we
first
our
our
smart
town
yeah,
we'll
have
to
consider
that
too
and
figure
out
a
way
to
update
the
links.
E
E
So
I
I
added
those
notes
into
the
hack
and
the
just
what
we
spoke
discussed
so
that.
D
B
E
B
E
I
think
that,
because
the
colors
are
changed
as
well
and
the
font
is
different
than
on
our
current
website
than
the
old
website,
the
new
website
that
we're
working
on
the
font
and
the
color
scheme
is
a
bit
different
than
what
is
there
on
the
current
website.
Right
now
and
when
you
look
at
the
docs
page,
it's
displaying
that
old
old
font,
so
we
would
need
to
change.
That's
that's
why
I
said
yeah.
B
Perhaps
perhaps
you
didn't
hear
exactly
what
I
was
saying
and
ben
halverson:
do
you?
Maybe
you
did
hear
the
doc
should
be
fairly
basic.
Markdown
right
and
dropping
them
into
place
should
should
adopt
all
of
the
styles.
I
don't
think
we
have
to
do
anything
there.
C
That's
right,
so
it
basically
is
the
same
idea
as
if
how
we
created
the
slash
about
it's
a
just,
a
plain
markdown
file,
where
it
doesn't
have
any
styling
from
the
content
perspective
and
the
goal
would
be
to
to
do
the
same
from
the
docs,
where
we
have
an
existing
style
in
the
new
site
and
we'll
just
consume
the
mark.
Down
and
he'll
accept
the
same
kind
of
styling
that
missouri
developed
so
like
if
you
go
to
like
the
slash
blur.
C
C
So
we
would
also
have
a
table
contents
and
the
ability
to
click
on
a
link
at
the
top,
and
it
would
slide
down
to
wherever
it
needs
to
go,
so
that
functionality
would
still
be
the
same
and
the
styling
as
far
as
far
as
font
and
headers
and
and
things
like
that
would
be
the
same.
So,
since
we're
using
markdown
like
a
a
single
hash
would
be
a
the
equivalent
of
h1,
whereas
two
hashes
is
h2
and
so
on.
So
all
that's
would
be
the
same,
so
we
would
since
we're
consuming
the
original
markdown.
E
E
E
Ben
and
joe
and
manish
I
have
to
drop
off
because
I
have
a
call
at
three
for
work
and
we
have
like
three
minutes
left
and
I
need
to
prep
for
that
call.
So
I
will
talk
with
you
guys
later
and
you
know
we
will
keep
on
working
on
this
and
you
know,
let
me
know
what,
if
anything,
if
you
guys
do
have
a
working
session,
please
let
me
know
I
would
like
to
people.
C
C
So
joe,
I
do
have
a
pr
in
note
core,
where
I
added
support
for
a
matter.
C
C
I
think
they're
generally,
okay
with
it
the
the
person
his
name
is
just
wanted
to
see
an
actual
like
pr
of
the
documents
on
and
what
it
looks
like
before
he
merges
it.
So
I
think
they're,
generally.
Okay,
with
that.
B
Great
great
so
yeah
we
can
pick
up
that
conversation
with
them
again
and
look
at
moving
that
forward.
B
Yeah,
let's-
and
that
was
a
node
core.
C
Yeah,
I
I
just
that's
the
link
right
there.
Three
three,
seven,
seven
yeah.
E
B
Cool
all
right
well
we're
at
three
o'clock,
but
I
think
this
document
already
is
is
great
and
you
know
we
can
all
continue
to
work
on
it
and
hopefully
have
something
to
share
soon
with
other
other
folks.
A
A
B
B
B
B
Yeah,
so
even
14
months
ago,
this
was
this
was
elsewhere
yeah
I
mean,
I
think
this.
That
line
item
in
that
table
is
really
old
and
I
don't
even
know
what
it
means
anymore.
Actually,
let
me
see
if
there's
what's
in
the
repo.
E
B
B
Where
is
javascript
yeah
there?
It
is
so
I'll.
Just
share
this
link
with
you
all
javascript
landia
is
a
place
where
we
are
going
to
flesh
badges
out
further.
B
B
B
Anyway,
I
am
going
to
drop
because
I
gotta
get
ready
for
another
meeting
and
I'll
work
on
the
doc.
But
I'll
see
you
all.
On
slack
and
next
week.