►
From YouTube: Node.js Website Redesign Initiative Meeting
Description
B
Life
awesome,
hello,
everybody
and
welcome
to
another
edition
of
the
node
J
s
website
leads
non-committee,
I,
guess
we'll
start
going
around
and
doing
introductions
as
usual
as
usual,
I'm
Adam
Miller
I
work
at
LinkedIn
as
a
front-end
web
developer,
I
a
member
of
the
community
committee
and
co-chair
of
website
redesign
committee
Darren
you
wanna
go
next.
Yes,.
C
D
F
B
So
we
have
a
first
point
here,
which
I
actually
think
might
be
premature
to
talk
about
miles.
Florence
pratas
is
issue
number
31,
essentially
using
an
API
service
for
website
content
miles
brought
up
that
it
may
be
best
to
use
a
hosted
CMS
rather
than
living
in
markdown
files
or
having
a
hard-coded
content,
and
they
spend
a
little
bit
of
discussion
on
here
thought
we
bring
it
up
in
the
larger
meeting.
B
C
D
B
I
think
Olivia
added
the
agenda
label
a
couple
weeks
ago,
when
this
first
went
up
so
I
think
we
can
take
it
off
for
next
week.
General
consensus
on
the
ticket
was
it's
a
good
idea.
It's
worked
very
well
for
us
at
LinkedIn
for
our
internal
site
having
this
kind
of
content
management
thing,
but
we
got
to
be
careful
cost
and
we
can
look
at
it
closer
when
I
get
to
that
stage.
So
well,
I.
C
Can
I
will
just
add:
I
can
give
a
little
bit
of
insight
into
the
one
he
explicitly
proposed,
which
is
contestable.
We
use
them
at
note
source
and
they
are
also
very
open
to
community
stuff.
I
know
if
you're
there
Deborah's,
so
we
might
be
able
to
go
through
the
path
of
getting
an
open
source.
You
know
version
of
that.
If
that's
a
need
or
you
know,
we
can
go
through
the
foundation
to
get
money
for
that
so
awesome,
but.
B
B
B
Sorry
to
do
one
time,
iteration
on
getting
started
content
and
nobody
responded
to
the
deal
I
will
reaping
reaping
I.
Do
something
for
one
that
a
separate
meted
meaning
for
iterating
on
on
getting
started.
Contents
drafting
that
is
wanted
or
needed
should
I
react
that
that
call
for
call
for
attendees
or
didn't
want
to
scrap
that
maybe
save
it
for
an
in-person
session
over
in
Berlin.
So.
C
I
think
we
should
definitely
do
an
in-person
session
in
Berlin,
but
on
top
of
that,
I
think
we
do
have
two
people
here.
That
probably
are
gonna
be
helpful
in
guiding
us
a
bit
on
that,
and
you
know
discussing
them
of
implementation.
Details
of
that
I
mean
I,
know
we're
still
in
the
design
phase,
but
that
should
yeah
getting
their
feedback
and
input
on.
That
would
probably
be
helpful,
so
yeah
I.
Would
you
to
like
do.
C
D
I'm
thinking
that,
in
terms
of
I,
mean
just
like
those
other
sites
do
having
a
working
example
that
people
could
just
like
spin
off
of
with,
like
I
guess,
very
low
effort.
I
haven't
thought
about
in
terms
of
what
those
examples
could
be.
This
is
my
first
time
coming
to
this
meeting,
but
I'm
very
interested
in
helping
working
out
that
kind
of
stuff
I've.
A
lot
of
experience
with
building
education
materials
around
node
so
be
happy
to
help
out
with
that
yeah.
B
B
B
B
D
We
don't
need
that
negativity
in
our
lives,
cool
so
yeah
for
those
who
are
saying
that
aren't
in
the
minutes,
if
you
could
go
to
glitch
no
js'
org,
that
glitch
taught
me
or
no
Jase
org
as
I've
read
it
so
yeah
I
know
not.
Everyone
is
familiar
with
glitch
or
who
the
hell
I
am
or
like
where
I
work,
whatever
I'm
John
Shaffer
I
work
at
fog,
Creek
glitch
is
the
product
I'm
working
on
as
a
community
engineer.
Sod
Creek
is
a
small
company.
We're
headquartered
in
New
York
City
in
this
financial
district.
D
I
say
that
we
were
the
cool,
not
bad
people
in
Wall
Street
and
we've
been
around
for
like
18
years
building
all
sorts
of
tools
to
help
debs
do
their
best
work.
That's
sort
of
our
mission.
We
created
fog
bugs
17
years
ago,
which
is
now
manuscript.
We
co-created
Stack
Overflow,
invented
Trello
and
now
we're
working
glitch,
which
we
call
the
friendly
community
where
you'll
build
the
app
of
your
dreams.
D
I
have
a
background
in
education
and
art
and
full-stack
engineering
and
I
vividly
remember
learning
that
you
can
write
JavaScript
on
the
server
and
being
like
okay.
Now,
nothing
will
ever
surprise
me
and
we've
spent
the
last
year
on
glitch,
enhancing
the
Deaf
experience
specifically
for
node
you
it's
there
can
every
app
as
a
container
and
the
code
that
you
write
in
the
editor
auto
deploys.
D
So
we
have
examples
of
different
languages
on
the
community
site,
glitch
comm,
but
our
full
support
is
for
node
applications
and
static
sites
and
in
fact,
static
sites
are
just
an
abstraction
of
a
node
application.
We
just
launched
a
rewind
get
interface
a
node
debugger.
So
now
you
can
not
only
have
you
brought
view
source
to
server-side
code,
but
we've
also
brought
full
stack
debugging.
D
All
over
the
world
we
have
developers
using
glitch.
We
have
companies
like
slack
using
as
a
teach
people
how
to
build
slack
bot
and
integrations.
We
have
people
embedding
glitch
apps
into
their
blogs
because
it
has
own
bed
support.
I,
guess,
projects
that
have
been
using
it
embedded
within
their
dogs
include
pros
mere
element
square
and
so
forth
and
we've
recently.
D
So
miles
told
me
about
the
redesign
going
on
which
I
was
very
excited
about
and
that
you
were
looking
for
a
sandbox
and
I.
Think
that
there's
a
lot
of
different
use
cases
for
node
to
be
on
the
site
and
I
think
some
of
them
would
be
really
great
for
rent
kit
and
I.
Think
some
of
them
would
be
really
great
for
glitch,
I'm
glitch
in
particular
lets
you
have
multiple
files.
It's
just
an
application,
that's
embedded
in
essentially
an
iframe.
D
It
allows
front-end
trials
also
and
I
think
that
a
very
important
thing
to
remember
is
that,
though,
nodejs
is
a
framework
for
server-side
code,
it
really
is
being
introduced
widely
to
front-end
developers
and
so
having
these
sort
of
full
stack
application.
Examples
in
there
would
be
really
effective
to
getting
people
to
understanding
like
the
concepts
of
server-side
code
and
how
node
makes
that
sort
of
lack
of
context.
D
Switching
and
language
change
like
really
powerful
and
we've
already
been
witnessing
that
in
past
years,
so
using
something
like
glitch
and
I
have
an
embed
example
in
that
document.
I
posted
the
project,
hello
express
this
is
one
of
the
three
apps
that
you
see
on
glitch
comm.
When
you
want
to
get
started
with
the
new
project,
it's
very
minimal.
It's
we
call
it
the
dream,
the
dream
of
the
future
app
and
it
just
shows
a
form
where
you
can
sort
of
add
your
dreams.
It's
a
abstract
to-do
list,
and
so
this
is
embedded
here.
D
We
allow
you
to
customize
the
embeds
to
whether
you're
gonna
just
show
the
app
view
the
code
or
both
you
can
also
give
it
query,
parameters
for
what
file
you
want
it
to
show
initially
and
I.
Think
one
of
the
coolest
things
about
it
is
that
once
you
start
editing
that
code
and
you
can,
we
have
Hawtree
mixing,
so
it
remixes
when
you
edit
so
within
seconds.
You
have
a
copy
of
this
app.
That
is
your
own
that
you
can
play
around
with
and
it
auto
deploys.
D
So
you
don't
have
to
worry
about
the
DevOps
death
glitch
doesn't
allow
doesn't
require
a
login,
so
users
aren't
gonna
have
to
like
log
into
anything
in
order
to
do
the
Hawtree
mixing
apps
exist
for
five
days.
If
you
don't
have
a
login,
so
it's
great
for
just
playing
around
here
and
there.
But
if
you
do
login
you
get
that
copy
of
the
app
forever.
D
So
so
yeah
and
beds
can
be
remixed.
It
can
be
edited.
Remixes
are
secured.
We
have
the
dot
end
file
for
adding,
like
your
tokens
for
third-party
api's
and
stuff,
which
you
might
want
to
work
into
your
node
examples,
but
those
values
don't
get
remixed.
Neither
does
anything
that
the
dot
data
folders,
that's
where
I
typically
have
people
put
their
database
files.
That
hello
expressed
example,
there's
a
hello
sequel,
like
example,
as
well
and
in
the
dot
data,
is
where
the
sequel
Lite
file
is
generated.
D
If
that
service
goes
away
and
with
glitch,
we
think
about
that
a
lot
in
terms
of
not
having
Block
in
the
apps
that
you
builds
on
glitch,
there's
no
proprietary
protocol
and
a
special
languages,
those
set
of
commands.
We
just
look
at
the
NPM
scripts
and
deploy
from
there.
So
you
can
export
all
these
examples.
All
these
apps
to
github
or
if
you
don't
use
github,
you
can
just
download
a
zip
file
so
we're
not
locking
you
into
it
in
that
sort
of
way.
D
This
goes
to
say,
though,
that
we've
been
around
for
18
years,
we've
never
taken
funding
we're
a
self-sufficient
company
that
wants
to
be
here
for
the
long
run
and
so
glitch
right
now
the
current
features
are
free
and
they
will
remain
free,
we're
gonna,
be
adding
four
teams
feature
will
or
membership.
You
can
go
to
glyph
comm,
slash
for
teams,
no
err
space
where
we're
asking
for
feedback
and
what
people
want,
because
I
am
in
the
rest
of
my
team
are
such
a
huge
fan
of
nodejs
and
it's
a
big
part
of
this
platform.
D
We
are
fully
ready
to
support
the
node
community
and
the
site,
so
we
will
be
giving
four
teams
for
free
and
basically
an
eel.
My
CEO
he's
like
yeah,
we'll
give
them
everything
for
free,
we'll
put
it
in
writing
like
we,
don't
want
the
nodejs
org
to
have
to
like
pay
for
anything
on
our
service
and
so
that's
sort
of
our
way
of
supporting
it
in
return.
So
yeah
that's
my
mission.
D
If
you
have
any
questions
beyond
this
meeting
Jen
at
glitch,
comm
is
my
email,
that's
Jen
with
two
ends
and
then,
if
you're
working
with
glitch
or
trying
it
out-
and
you
have
any
issues
you
could
message
me-
we
have
a
very
active
support
forum
at
support,
deck
glitch,
calm
and,
if
you're
working
on
any
code
within
glitch-
and
you
get
stuck,
you
could
highlight
it
and
ask
the
community
for
help
and
people
could
come
in
in
real
time
and
help
you
out
with
that.
So
yeah
are
there
any
questions.
B
Thank
you
so
much
Jen,
and
and
thank
you
for
the
very
generous
offer
or
the
the
free
fourteens
account
yeah
I
I
have
I
have
a
couple.
A
couple
questions
for
one
I
I
have
also
used
your
product
before
we
use
it
a
little
bit
over
at
LinkedIn
just
just
touchin.
It's
a
I
just
actually,
but
it's
I
really
and
do
enjoy
the
the
full
project
experience
here,
but
I
I
don't
have
a
strong
understanding
around
I
like
a
debug
experience
for
more
server-side
stuff.
A
D
Working
on
a
node
app
on
glitch
and
you
open
up
the
logs
there's
a
little
ladybug
icon
there.
It
gives
you
a
link
to
open
up
in
chrome,
dev
tools,
connection
to
the
glitch
app,
so
you
can
do
breakpoints
in
the
server
side
code
in
chrome,
dev
tools.
It's
not
it's
not
like
the
perfect
experience,
but
for
security
reasons.
Of
course,
the
browser
vendors
are
not
going
to.
Let
us
open
up
someone's
dev
tools
for
them.
D
So
that's
my
design,
but
it's
a
lot
closer
than
people
have
been
getting
and
again,
we've
been
talking
to
the
Firefox
dev
tools:
team,
like
literally
met
with
them
I
think,
like
yesterday
morning
times
the
social
contract.
It
was
sometime
this
week
about
them,
bringing
their
debugger
back
into
the
dev
tools,
because
it's
kind
of
like
not
complete
and
not
really
like
an
owned
project,
but
they're
ready
to
bring
that
back
in
so
hopefully,
there'll
be
a
time
where
the
node
debugger
feature
and
glitch
can
work
on
all
browsers.
Yeah.
B
Yeah
I,
really
what
you
said
about
having
front-end
files
in
here
running
in
here
as
well.
He
resonated
with
me
Donna
personally,
a
front-end
dev
by
training
myself
and
journey
I.
Believe
last
time
we
talked
about
having
at
least
on
the
home
page
having
leave
it
is
he
who
said
that
there's
there's
more
than
one
target
audience
for
node
and
go
right,
yeah,
absolutely
and
having
having
sections
of
a
getting
started
track,
be
targeted
towards
different
people
with
different
concerns.
C
D
I
don't
know
if
that
is
a
use
case
that
works
within
the
confines
of
the
glitch
app
like
I
said
earlier.
There
they're
gonna,
be
examples.
I
think
that
run
kit
really
shines
on
that
sort
of
like
right
within
the
page
showing
log
stuff.
You
can't
see
the
logs
and
an
embed
and
you'd
have
to
like
open
it
up
into
glitch,
and
if
you
own
the
projects,
you
can
see
it
so
for
those
like
sort
of
more
entirely
server-side
log.
Examples
from
kit
would
be
great,
as
for
doctor,
I
have
explored
that
idea,
but
I.
C
B
We
don't
we
don't
have
any
concrete
artifacts
yet
of
of
what
we
want
from
a
getting
started.
Work
we
had
been
talking
about
coordinating
working
with
what
note
school
has
has
already
started
to
put
together
and
kind
of
a
you
know,
hammering
that
into
the
shape
of
a
curriculum
for
the
website
or
a
learning
path
for
the
website.
E
D
D
B
D
B
Getting
started
cool
yeah.
That
is
something
we
definitely
want
to
iterate
on
and
as
I
said
before,
I.
If
we
do
want
this
this
additional
meeting
for
like,
is
it
sound
it's
time
to
actually,
you
know,
sit
down
and
collaborate
on
a
shared,
Google,
Doc
or
something?
Let's
totally
do
that
I
will
reaping
that
thread
with
the
with
the
doodle.
B
Yeah
it
got
it
got
next
to
no
response,
since
what
I
posted
it
off
the
last
meeting,
so
we'll
try
and
reaping
that,
and
we'll
we'll
keep
working
offline
for
a
dedicated,
dedicated
list
of
content
ideas.
But
what,
from
at
least
votes
from
I've,
seen
from
both
glitch
and
and
run
kit
is
y'all
occupied
slightly
different
spaces,
slightly
different
concerns.
B
C
F
F
We
called
be
like
x-ray
app,
and
so
what
we're
thinking
is
kind
of,
like
you
know
your
different
files
or
the
front-end
or
back-end
package.json
yarn
again,
like
that's
another
like
important
question,
guys
like
what
is
a
full
lap
like.
Are
we
saying
we're
only
pretending
on
p.m.
exists
or
pretending
shrink
wraps
exist
for
pretending,
yarn
exists
and
then
the
goal
would
be
like,
as
you
click
through
the
files,
some
of
them
totally
edible
an
HTML
file,
a
Jess
file
package,
not
JSON,
we
were
thinking.
F
Maybe
you
can
only
edit
the
title
or
something,
and
then
we
don't
let
you
edit
the
dependencies
because
I
write
the
package.
Json.
Is
this
weird
file
for
like
half
of
it
is
computer-generated
most
the
time
and
half
of
it
is
like
free
rain
and
then
like
the
yarn
paw,
like
not
editable
at
all
and
like
basically
at
the
top-
and
this
is
I
kind
of
the
most
important
part
in
our
mind,
explaining
what
these
files
are
right.
F
So,
as
you're
clicking
through
like
the
left
hand,
thing
of
the
files
saying
hey,
is
this
the
package.json?
Why
is
this
in
here?
Well,
because
this
describes
the
title
of
your
app
whatever
this?
Is
the
yarn
file
you're?
Probably
not
going
to
touch
this
like
this-
is
generated
by
this
really
cool
thing?
F
B
I
think
I
think
what
we'll
probably
want
to
do
is
let
the
let
the
content
dictate
the
the
layout
here.
We've
we've
gotten
we've
gotten
very
good
demos
from
from
from
both
of
you
and
and
what
we
need
to
do.
Is
it
as
the
website
you're
just
time
to
figure
out
what
this
design
looks
like
and
then
make
the
choice
based
on
it
for
what
we
use
where
based
on
based
on
the
content
we're
trying
to
present.
C
I
WI
I
definitely
agree
with
that,
and
I
also
think
that
you
know,
as
Jim
mentioned,
that
there's
very
different
use
cases
for
each
of
them.
Each
of
the
platforms
and
like
that
that
demo,
that
y'all
shared
with
us
from
Ron
KITT
last
time
was
incredible
for
the
docs
like
that
was
a
really
solid
demo
and
that's
honestly,
something
that
I
think
we
should
probably
do,
because
it
takes
out
a
lot
of
the
pain
of
Doc's
on
our
end
and
on
the
users.
C
His
the
docks
are
one
of
the
most
painful
things
to
me
in
nodejs
right
now,
just
in
terms
of
usability
and
stuff.
So
that
was
really
solid
and,
like
that's
a
really
good
use
case.
I
imagined
that
there's
gonna
be
other
similar
use
cases
just
across
the
site
and
then
like
in
in
the
vein
of
getting
started.
I
do
think
that
glitch
the
way
glitch
is
organized
lowering
the
barrier
in
having
that
kind
of
full
insight
into
your
application
is
probably
a
really
good
approach
for
some
of
the
getting
started
content
as
well.
C
So
I
I
definitely
think
that
we're
gonna
end
up
going
with
a
little
bit
of
both
like
a
little
bit
of
a
a
little
bit
of
combi
just
because
of
the
nature
of
how
broad
nodejs
is
and
how
much
we
have,
and
we
have
to
do,
and
each
of
the
two
platforms
offer
a
really
solid
solution
for
our
two
biggest
problems.
So
yeah
that
that's
just
my
guess,
like
obviously
not
committing
to
anything.
But
that's
my
guess
of.
What's
going
to
happen.
B
A
B
If
you
guys
find
it
always
helps
with
these
community,
you
know:
ask
her
ask
for
content
from
the
community
of
there's
a
legacy
there.
So,
if
you'd
like
to
like
draft
at
least
a
little
bit
of
scaffolding,
for
what
what
you
think
would
be
good,
can
you
know
help
kick-start
Commerce,
a
absolutely
yeah,
you're,
wonderful.
B
C
B
This
is
the
perennial
wireframes
issue
which
I
believe
said
last
time
we
are
wrapping
up
and
we
are
moving
on
to
starting
to
kick
off
actual
visual
design,
just
a
reminder
to
everybody.
Listening
in
on
the
node
I'm,
sorry
on
the
the
YouTube
stream
and
everybody
else
here
we
have
a
channel
in
node
slackers,
where
we're
hoping
to
do
faster,
faster
iterations
of
content
and
ideas,
we're
all
hanging
out
in
there.
So
please
come
join
I,
but.
B
Hold
on
sorry
yeah,
okay,
so,
but
we
had
wanna
ters
and
move
on
to
this
more
visual
design
phase,
which
we
are
in
need
of
people
to
get
down
and
dirty
with
actual
design,
iterations
we'd
love
to
base,
probably
what
we're
making
off
of
the
wireframe
prototype.
Let's
then
put
out
at
least
loosely
based
on
that,
but
we're
also
in
need
of
a
a
process
for
how
we're
gonna
handle
this
I.
Don't
think
we
have
really
tackled
this
before,
especially
since
just
being
an
open
source
project.
There's
no
one!
A
C
C
I'm
helping
go
through
that
with
the
certification
right
now,
it's
not
a
short
process,
so
you
know
if
we
can
do
it
through
the
community.
That
would
be
stellar,
but
you
know
we
we
do
have
that
option
if
we
need
to
go
back
to
that
beyond
that.
I
do
know
that.
There's
some
you
know
designers
in
the
JavaScript
community,
and
you
know
we
would
absolutely
love
to
have
them.
I
know,
Rachel
white
knows
a
few
of
them.
C
That
would
be
interested
in
helping
our
well
had
been
interested
in
helping
out
with
a
different
node.js
website
project
that
you
know
might
be
willing
to
help
out
this,
but
I
definitely
like
to
open
the
first.
You
all
to
you
know.
If
you
all
have
any
suggestions,
we
love
to
reach
out
and
interact
those
people.
B
This
call
for
call
for
submissions
of
people's
take
on
the
design,
unfortunately
collaborative
like
true
collaborative
design
like
what
we
do
with
code
is
exceptionally
difficult
if
you're
not
sitting
in
the
same
room,
I
think
we'd
have
to
go
for
this.
This
async,
like
everybody,
submitting
your
proposal
like,
let's
we'll
vote
on,
which
which
direction
we
like
better
and
then
ask
people
to
iterate
off
of
off
of
that
and
kind
of
go
through
this
evolving
evolving
around
with
submissions
for
actual
actual
mocks,
and
that
would
be
100%
drone
by
interest
like
we
need.
B
C
One
of
the
things
that
I
will
kind
of
give
context
around
is
in
no
js'
and
I
ojs
we
did
I
think
three
or
four
rounds
of
design
by
committee,
including
like
basically
exactly
what
you're
proposing
once
for
website.
For
I
oj
s,
we
got
all
the
designs
they
actually
smell,
they're
in
the
gate,
history,
I
I,
went
through
deleted
them,
but
they're
in
the
gate,
history
of
the
evangelism
repo.
C
So
there
we
go
amazing
designer
did
a
ton
of
work
on
the
design,
but
the
thing
that
always
happens
are
that
I've
seen
happen
at
least
three
times
now.
Is
we
get
a
bunch
of
designs
and
then
like?
We
don't
really
have
a
good
way
to
stop
and
we
don't
have
a
good
way
to
select
like
yes
this.
This
one
has
good
elements.
This
one
has
good
elements.
This
one
has
good
elements
like
for
20
different
designs.
C
C
Let's
go
on
to
the
next
stage
with
you
know
two
or
three
people
or
just
choose
one
of
them
rather
than
going
through
the
whole
path
of
like
expecting
a
full
design,
because
you
know,
even
in
a
focus,
I
will
need
to
work
with
people
a
little
bit
closer
I
know:
I
I'm,
just
I'm.
We've
done
this
design
by
competing
a
few
times,
and
it's
always
been
a
little
bit
confused
and
a
lot
of
people's
feelings
have
gotten
hurt,
and
it's
not
been
great,
so
I'm,
just
something
else
and
I'm
a
little
worried.
B
D
B
Feel
slighted,
ER
and
you're
appreciated.
That's
for
sure,
but
I
do
like
this
idea
of
maybe
giving
out
sections
of
the
website
and
and
having
people
iterate
on
them
separately
at
smaller
bite,
size
chunks
and
this
this
group,
that's
body,
be
the
the
glue
that
holds
it
together
and
making
making
sure
it
gets
stitched
together
in
a
reasonable
way.
But
again,
this
is
all
predicated
with.
B
C
So
the
notification
went
out
two
weeks
ago
and
it
hasn't
like
their
proposals,
haven't
been
completed
because
the
foundation
is
the
foundation,
is
going
through
its
processes
so,
like
the
proposals
aren't
even
in
for
that
yet
and
that's
after
I
think
a
week
or
two
of
defining
the
RFP
itself,
which
was
non-trivial
and
basically
it
just
someone
just
stepped
up
and
did
it
who'd
like?
Does
this
professionally
so
yeah
I?
C
B
C
D
C
C
B
Not
us,
it's
not
a
buy-in
to
using
the
funds
yep
finding
a
partner
for
it.
Okay,
yeah
I
think
it
would
be
good
to
start
going
through
that
process.
Okay,
just
in
case
we
find
ourselves
one
month,
two
months
from
now
with
a
half
designed
website
and
ya,
know
clear
path
forward.
We
can.
We
can
pull
the
trigger
on
that,
if
need
be
cool
yeah.
B
C
A
B
You
know,
let's
figure
out
how
we're
going
to
be
giving
up
the
site
and
asking
people
to
claim
a
piece
of
it,
maybe
self-assign
in
a
in
a
in
a
spreadsheet
or
something
to
to
taking
a
stab
at
a
section
of
the
site.
You
know
get
some
some
basic
visual
guidelines
out
there.
So
don't
get
people
coming
out
of
left
field
with
new
iterations
and
at
least
set
up
the
funnel
for
people
coming
in,
but
then
actually
make
this
a
big.
B
You
know
hey
know:
Jason's
redesigning
everybody
come
help,
but
you're
interested
call
to
action.
Awesome
yeah
I
will
create
the
issue
to
set
up
that
pipeline
on
our
end,
and
work
towards
I
might
use
that
nifty
github
projects
feature
so
work
towards
a
public
public
call
to
action
for
designers
on
our
on
our
sounds
good
sweet
do.
B
C
B
B
Yeah
we
have
been
invited
to
give
a
little
presentation
at
the
collaboration
about
the
work.
That's
then
the
work
that's
been
happening
here
in
the
website
redesign
committee,
and
we
also
want
to
host
a
dedicated
session,
presumably
for
getting
started
content,
but
also,
maybe
for
other
topics
its
if
we
have
other
things
bring
up
there.
B
So
I
just
wanted
to
make
sure
that
state
talk
with
everybody
finds
and
that
many
of
you
and
I
make
sure
that
we
work
towards
getting
whatever
we're
gonna
be
saying:
it's
collaboration
summit
polished
and
it
almost
Alice
before
we
we
show
up
so
I'm,
not
sure
if
we
have
anything.
If
we
have
time
today
or
if
we
you
didn't
have
stuff
as
a
group
that
we
can
do
here,
but
I
wanted
to
make
sure
it
stayed
at
the
top
of
everyone's
mind.
So
we
will
be
there
we'll
be
talking.
It's
gonna,
be
a
blast.
B
B
It's
my
understanding
that
it
will
be
live-streamed
and
there
will
also
be
meeting
notes.
I
saw
that
going
on
in
the
in
the
conversation
there
was
somebody
who
brought
up
that
previous
ones
had
not
been
well
documented,
and
we
want
to
make
sure
that
it
is
this
time
so
from
what
I've
heard.
Yes,
it
will
be.
It
will
be
well
documented,
excellent
yeah,
while
we're
all
here.
Is
there
anything
else
that
we'd
like
to
see
happen
in
an
in-person
meeting
of
website
redesign
other
than
like
really
knocking
out
getting
started.
C
B
That's
very
true:
okay,
that's
awesome!
Well,
if
that's
all
we
got
on
the
agenda
I.
Thank
you.
Everybody
on
the
the
YouTube
stream
for
calling
and
listening.
Please
feel
free
to
jump
in
on
the
the
github
issues
as
you
see
fit
and
as
you're
as
you're
interested,
and
thank
you
all
for
calling
him
today.
Thanks.