►
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
B
A
A
But
progress
being
made
and
see
if
there's
more
to
talk
about
agenda
has
not
changed
much
since
last
week,
but
we'll
go
through
it
for
formalities,
sake
probably
skip
over
good
chunks
of
it
and
then
we'll
talk
about
give
a
little
design
update
and
then
Miniland
me
and
other
folks.
Interested
can
can
talk
about
content
creation
again.
Philony
cool
first
ticket
is
creating
a
branch
of
Doc's
using
around
kit
and
Cisco.
You
can
give
an
update
and.
C
A
C
A
C
A
A
But
that's
not
what
that
tickets
for
so
yeah,
let's,
let's
at
least
just
go
off
and
get
a
quick
design
update
from
from
Joey
Lee
yeah.
Before
your
own
update,
yeah.
A
Awesome
yeah
I
can
brought
a
little
more
context
for
folks
to
this
was
Joey's
Joey's
in
San,
Francisco
and
and
Tierney
is
also
magically
in
San
Francisco
this
week.
So
we
had
a
we
had
kind
of
like
a
really
high-level
meet
and
greet
and
and
knowledge
dump
from
tyranny,
and
and
myself
and
Joey
had
prepared
six
like
very
high
level
experiments
about
what
directions
our
code
had
in
so
very
nitty-gritty
and
high-level
conversation.
A
Best
way
to
describe
it,
I
really
was
yeah
yeah,
so
we
yeah,
we
went
over
some
of
those
directions
and
talked
about.
You
know
how
we're
where
to
set
true
north,
or
at
least
the
general
direction
that
might
be
for
design
work
yeah.
As
we
start
getting
higher
fidelity
Moxon
better,
better
direction
chosen
out
will
will
probably
open
it
up
to
a
more
public
venue.
Now,
as
we
keep
iterating
on
on
content.
But
the
worst
thing
at
the
very
beginning
is
always
designed
by
committee.
So
we're
we're
hoping
they
keep
and.
E
E
E
It's
just
to
kind
of
get
since
I'm
dude.
The
community
knew
the
project.
It
was
beneficial
for
me
to
kind
of
just
mix
some
things
together
and
kind
of
present
them
as
they
might
even
in
the
ballpark
kind
of
thing.
So
it's
it's.
That's
one
reason
why
we
don't
want
to
share
with
anybody,
because
it's
really
more
for
my
benefit.
C
Anyway
and
along
the
team
being
like,
hopefully
at
some
point,
this
will
be
at
a
place
where,
like
it
can
be
represented
with
bugs
and
the
issue
tracker
I,
don't
necessarily
think
that's
that's
ready
for
that
now,
however,
I
thought,
maybe
a
couple
things
we
talked
about-
might
make
sense
an
issue
tracker
specifically
like
they
know
the
foundation
stuff
I,
don't
know
if
we
want
to
start
just
having
that
in.
There
is
like
just
to
have
a
place
to
be
like
how
is
this
going
to
fit
into
the
site
or
anything
like
that?
A
Each
record
awesome
cool,
so
segue
into
content
creation,
big
staple
issues,
issue,
number,
60,
I,
don't
believe
any
significant
work
has
been
done
to
push
this
forward
since
last
time.
I
believe,
last
time
we
talked
about
identifying
specific
stakeholders
and
trying
to
assign
them
it's
very
specific
and
scoped
documents
to
write
or
ask
them
to
do
so,
and
we
also
agree
that
we
need
a
we
needed
to
take
a
step
back
and
think
about
the
structure
of
these
getting
started
guides
and
what
the
best
format
they
should
take
is.
Okay,.
B
B
Sorry,
so
I
I
think
what
we
do
need
to
provide
them
is
like
cool
here's,
how
you
can
start
because
I
can
prefer
the
issue
at
them
and
making
kind
of
I'll
try
to
pull
that
card,
but
I,
don't
think
that's
necessarily
a
starting
place
for
the
content,
and
so
that
I
think
would
be
most
helpful
of
like
here's.
What
we're
looking
for
even
building
out
like
a
template
of
the
structure
of
the
document,
and
then
they
can
go
and
kind
of
do
their
magic
with
it.
A
You
have
so
we
we
have
a
template,
but
it
basically
has
a
section
says:
content
goes
here:
do
we
do
we,
as
a
group,
have
an
idea
of
what
format
we'd,
like
actually
the
actual
pages
to
take,
or
do
we
think
that
the
via
consists
in
enough
structure
that
we
can
provide
top-level
headings
or
at
what
point
are
we
essentially
writing?
Subject
headings
for
them,
depending
on
the
page
handing
it
off
for
them
to
fill
in
content
like
how
granular
can
we
make
a
template
without
getting
too
prescriptive?
Yeah.
B
And
I
personally
have
a
lot
of
feelings
around
this,
but
one
of
the
things
I
think
I,
like
least
layout.
The
structure
for
them
of
like
cool
you're
gonna,
do
an
introduction
to
say
what
this
is
about.
Then
you're
going
to
do
whatever
the
content
is
and
like
also
a
style
guide
around
like
they're,
only
gonna
use
a
choose
and
below
and
go
down
to
h6,
but
try
not
to
do
that
and
then
you
know
have
a
conclusion
as
well.
Oh
and
then
have
a
guideline
of
what
they
like.
B
Can
they
go
promote
a
product
or
is
you
know,
does
this
need
to
be
a
you
know,
agnostic
of
hey,
you
should
go
check
out
our
product,
which
it
probably
does
so
I'm
just
trying
to
like.
We
need
to
get
those
kinds
of
things
of
like
okay,
I'm
gonna,
write
content.
What
are
my
guidelines
here?
What
can
I
do
and
what
can
I
not
do
and
then
how
do
I
need
to
approach
this?
In
terms
of
you,
like
five
paragraph
essay
type
of
structure,
you
know
there
needs
to
be
nature.
B
There
needs
to
be
a
conclusion
and
there
needs
to
be
content
in
the
middle
and
then
also
something
like
how
do
I
add
screenshots.
These
are
it's
consistent,
formatting
that
they
need
to
have
things
like
that.
That's
probably
getting
a
little
bit
too
deep
a
little
bit
too
soon,
but
it
is.
You
know
something
that
we're
gonna
want
to
consider.
Consider.
A
Yeah
so
I
just
link
to
place
note
site
redesign
rebuild
that
documentation
folder.
That's
the
probably
the
right
place
to
put
this
guidance
right
now
we
can
I
believe
it
yeah.
It
links
out
to
voice
into
a
guidelines
to
give
some
instructions
I'm
like
where
to
put
your
markdown
file
for
the
article
and
it
gives
that
sample
template,
which
is
basically
cotton
goes
here.
Content
goes
here.
A
It
would
be
pretty
straightforward
to
flesh
that
out
with
you
know
the
stock
level
sections
literally.
What
you
just
said,
I
wish
I
was
notes
on
that,
because
we
could
hear
good
I
can
do
that
yeah,
but
it
yeah,
if
you
could
take
10
minutes
after
this
call
and
and
open
up
er
with
with
just
that
very
limited,
getting
started,
content
and
I
think
we
could.
We
can
call
that
done.
C
Trying
to
figure
out
how
to
like
kind
of
allowed
like
not
getting
to
one
of
these
like
deadlock
situation
to
our
like,
you
know,
they're
waiting
on
designs,
if
be
able
to
make
the
thing
go,
we
can't
really
make
the
design
without
seeing
something.
Are
there
any
just
like
existing
cool
articles
that
we
could
like
incorporate,
like
maybe
Deb
DUP?
C
B
C
C
Guess
one
one
just
related
question
to
that:
I
don't
know,
I
certainly
know
plenty
of
people
on
the
electron
team,
and
maybe
you
guys
did
too
I
just
see
that
it's
on
here
kind
of
just
something
I
was
curious
about
is,
like
you
know,
given
our
existing
timeline.
If
people
start
writing
stuff
now,
I
think
there's
a
good
chance.
They
might
not
see
like
the
fruit
of
their
labor
for
kind
of
a
mile
yep.
It
should
be
not
be
trying
to
reach
out
to
early
just
I.
Don't
want
them
to
like
spit
something
out.
C
B
And
that's
that
kind
of
goes
to
to
my
original
point
around,
like
I'm
with
the
initial
batch
of
people.
That
I
think
I
personally
have
in
mind.
That
would
be
interested
in
doing
this
and
have
the
cycles
and
the
ability
to
do
it
like
on
in
their
work
time.
That
shouldn't
be
as
much
of
an
issue
as
it
would
be.
With
someone
who's
coming
in
and
just
like
dropping
content.
And
then
you
know
going
on
moving
on.
A
Once
we
find
once
we
find
like
two
or
three
people
to
contribute,
maybe
five
articles
total,
like
I,
think
that's
the
first
set
jump.
Oh
yeah.
We
won't
make
a
public
call
for
contributions
until
very
scoped
right
now,
yeah,
but
like
that
the
first
few
people
to
give
feedback
on
what
structure
they
should
take,
and
you
know
to
kind
of
refine
that
voice
and
tone
we
can
have
those
five
articles
to
then
say
this
is
what
we
currently
have
you
want
it
in
this
vein.