►
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
C
B
So
for
a
lot
of
the
ci
and
task
management
using
run
and
that's
been
great
and
using
that
for
a
while
and
so
so
now
you
know
we've
kind
of
focused
on
yelling
for
some
of
the
project.
Scaffolding,
let's
kind
of
focus
right
now
is
kind
of
building
out
these
platform,
different
libraries
that
properties
like
magazines-
and
you
know,
magazines,
yahoo,
attack
food
and
in
my
yacht,
can
use
to
build
their
sites.
B
Yeah,
it's
interesting,
I
mean
so
a
few
months
ago,
actually
telling
myself.
We
did
a
presentation
at
yuykov
about
run
and
one
of
the
things
we
used
in
there
was
grunt
init,
which
is
a
very
simple
utility
to
create
scaffolding
for
your
projects,
and
I
was
actually
happy
with
grunt
and
I
liked
running
it,
but
unfortunately,
it's
being
deprecated,
and
so
I
had
spent
a
fair
amount
of
time.
B
Writing
all
these
templates
and
scaffolding
for
our
projects
and
kind
of
the
back
story
to
our
projects
is
we
have
different
type
project
types
that
you
can
build?
You
can
build
these
kind
of
modules
that
would
show
up
on
my
yahoo
or
you
can
build
full
applications
so
to
make
that
easy
to
do
we
wanted
something
we
needed
a
way
to
keep.
B
You
know
folder
structure
and
power
structure
of
the
system
across
these
projects,
and
so
the
brightness
was
very
simple
to
use
and
since
we're
already
using
grunt,
we
were
familiar
with
the
toolset,
and
so
we
were
using
that
for
a
while
and
then
when
I
saw
that
it
was
deprecated
and
kind
of
slow
to
get
fixes
in
or
any
new
enhancements.
And
the
author
basically
said
you
know
we're
probably
going
to
switch
to
yeoman
eventually.
D
C
B
Necessarily
look
at
a
lot
of
other
things
outside
of
that
I
mean
I
looked
at
yeoman,
real,
quick
and
I
kind
of
saw
the
community
behind
it
and
the
people
that
were
working
on
it
and
how
active
it
was,
and
it
was
kind
of
a
no-brainer
to
continue
using
it,
how
to
use
it.
And
then
you
can
get
the
support
from
there
cool.
B
B
And
then,
if
they're,
building
a
you,
know,
full-page
app
like
rapid
screen
and
then
we'll
use
that
to
generate
the
files
and
structure
and
kind
of
give
them
a
skeleton
project
that
they
can
actually
run
right
away.
And
so
it's
a
little
it's
it's
a
little
more
than
just
folders
and
a
couple
of
files
it.
Actually,
when
you
build
that
module,
you
can
actually
run
it.
B
You
can
run
node
and
then
you
know
the
server
file
and
it'll
start
up
the
the
module
and
you
can
run
it
in
your
browser
and
so
you'll
get
an
actual
working
example.
So
you
can
see
you
know,
how
do
you
fetch
data?
How
do
you
use
templates
and
dust
and-
and
you
can
even
run
the
functional
tests
that
come
associated
with
it
actually
run
as
well?
So
you
kind
of
get
an
end-to-end
idea
of
how
to
build
something
in
our
framework,
so
cool.
B
Yeah
yeah
very,
very
simple
use
case,
but
yeah,
but
it's
it's
been
great.
I
mean
we
haven't,
had
any
issues.
You
know.
I
think,
if
we
didn't
have
that,
there's
hundreds
of
developers
using
using
our
libraries
and
the
platform
now
and
trying
to
get
consistency
across
all
this
people
would
be
really
difficult.
E
One
of
the
benefits
of
yeoman
is
like
the
fact
that
you
can
create,
like
custom
prompts
and
stuff
like
that.
Have
you
guys
like
experimented
with
that?
All
like
I
don't
know
if
there's
any
like
customized
features
that
you'd
want
to
like
have
as
like
questions
or
anything
like
that
when
you
start
up.
B
Yeah-
and
I
can-
I
can
show
that
as
well.
I
can
show
sort
of
how
we
built
out
our
scaffolding
and
yeah
really
having
those
custom
prompts
being
able
to
when
we
name
our
modules.
We
have
a
certain
convention
that
we
follow,
and
so
we
can
kind
of
we
can
have
those
prefixed
ahead
of
time,
so
people
follow
the
same
conventions
across
across
the
different
modules
are
used,
that's
just
consistency
across
projects
and
across
developers.
That
has
been
the
biggest
thing
and
you
know
before
you
came
in.
B
B
Okay,
you
can
see
here,
you
can
see
everything
now
right,
yep,
so,
as
I
was
saying
before,
with
modules
they're.
Basically,
on
my
yahoo
you'll
see
these
modules
internally,
we
actually
call
them
applets,
but
because
we
have
a
lot
of
names
for
modules.
You
know
npm
modules,
yui
modules,
so
we
named
it
a
little
differently
about
these
boxes
that
are,
on
my
home.
B
C
B
So
here
is
our
folder
structure.
We
have
different
project
types,
app,
what
I
call
what
we
call
applet,
which
is
a
module
libraries
which
are
just
npm
modules,
but
we
have
a
scaffolding
for
that.
Just
so,
there's
certain
components.
Internally,
we
have
a
travis
like
ci
release,
pro
service
called
screwdriver,
and
so
we
can
set
up
some
of
those
files
automatically
and
have
the
right
settings
in
our
package.json
created.
B
F
B
B
C
C
B
Quickly
for
the
applet,
so
within
the
applet,
this
is
just
a
structure
that
yeoman
sets
up.
You
have
a
templates
folder,
which
is
going
to
contain
all
the
files
that
you
want
to
file
in
folders.
You
want
to
scaffold,
then
indexed
is
essentially
the
generator
file
that
yeoman's
going
to
read
to
figure
out
which
prompts
you
want
to
use
and
I'll
show
those
in
the
the
editor
here.
B
This
is
the
setup
of
basically
our
modules,
so
we
have
similar
things.
We
have
a
error
config,
we
have
a
grunt
file,
so
they
can
run
unit
tests,
functional
tests,
a
git,
ignoring
hearing
all
this
stuff.
The
app.js
is
what
starts
the
module
locally,
so
when
developers
are
running,
they
can
start
their
module
up.
B
We
have
configs
for
json
files
for
doing
configuration
and
just
different
things
with
stores
and
models
and
views,
yui
models
and
views
that
we
share
as
well,
and
when
you
look
at
models,
we
have
a
simple
file
in
here
that
will
be
replaced.
The
name
is
just
a
token
that
will
be
replaced
when
you
generate
your
store.
Let
me
see
see
if
this.
B
B
B
See
here
we
have
it'll
take,
you
know
the
name
of
it
and
generate
the
module
name
and
just
the
example
app
that
we
have
that
we
set
up
for
them
and
some
of
the
using
our
framework
that
we
have
will
generate
some
of
these
things.
But
you
can
see
that
it
will
use
the
name
everywhere
to
pre-populate
everything.
So
it's
correctly
identified
and
set
up.
B
So,
besides
that
I
can,
I
think
what
would
be
interesting
is
kind
of
how
we
set
it
up
so
in
each
in
each
one.
If
I
go
back
to
applet,
the
index
file
is
basically
just
calling
this.
The
yeoman
generator
creates
a
generator
constructor.
We
inherit
from
this
base
one,
and
then
we
just
grab
some
of
the
methods
that
we
need
and
we
export
the
generator,
and
this
is
what's
going
to
run,
yeoman's
going
to
run
and
basically
export
and
the
cool
thing
is
for
all
of
these
they're.
B
Basically
the
same,
I
didn't
change
much
and
it
they
used
the
the
folder
name
as
the
yo.
You
know
when
I
called
yo
tv
applet
before
they
use
the
folder
name
for
that,
and
so
the
everything
is
based
is
in
base.js,
which
is
just
a
convention
I
created,
and
this
is
the
idea
that
usually
this
file
would
be
if
you
were
going
to
do,
yo
seth
and
if
you
didn't
have
like
the
td
colon
namespace,
it
was
just
seth
was
the
generator
name.
This
would
be
here,
but
because
we
wanted
sub
generators.
B
B
Yeah
I
wanted
to
do
a
sub
generator
just
to
it
would
be
easier
for
us
to
manage
updates
across
our
generators.
If
we
had
to
have
an
npm
package
for
each
generator,
it
would
be
really
hard
to
get
everyone
to
update
and
be
up
to
date,
because
it's
actually
even
hard
now,
just
because
if
we
make
a
change
to
a
generator,
we
rely
on
the
user
to
run
an
npm
update
first,
and
you
know
to
get
those
changes.
A
B
It
was
grunt
actually
is
a
bit
easier
to
start
up.
The
learning
curve
is
pretty
low.
It's
pretty
easy,
but
sharing
these
things
across
I
had
to
do
a
lot
of
duplicate
code
and
so
within
yeoman.
This
is
a
lot
easier
to
set
up
the
inheritance
and
kind
of
leverage
everything
from
one
from
one
file.
So
I
think
it
was
a
little
bit
steeper
of
a
learning
curve,
just
because
everything's
really
it's
really.
B
B
It
took
a
little
bit
to
ramp
up,
but
once
you
know
you
get
past
that
it's
it's
really
simple
and
a
lot
of
the
stuff
in
here
is
just
kind
of
trigger
methods
that
I
did
to
generate
energy
based
on
our
namespaces
or
conventions,
so
getting
the
namespace
that
we
use
to
generate.
You
know
the
name
of
the
package,
a
message
at
the
end
after
you
run
it.
B
I
may
have
run
out
of
buffering
so
anyways.
We
have
different
messages
based
on
the
type
and
before
you're
asking
about
the
prompts.
So
this
is
where
we
can
declare
which
prompts
that
we
want
to
do
and
have
you
know,
default
a
default
value
for
that,
for
that
prompt
and
luckily,
across
all
of
our
packages,
we
share
the
same
prompts
because
they're
pretty
generic
they're,
basically
just
filling
in
the
package.json,
and
then
we
have
extra
ones
to
capitalize
things
and
set
that
up.
B
We
have
other
conventions
where,
if
it
starts
with
a
dot,
we
basically
we
put
a
an
underscore
in
front
of
it,
so
that
it
doesn't
get
picked
up
by
our
build
process
and
try
to
install
the
generators
there's
a
little
bit.
We
had
to
deal
with
and
then
just
some
other
conventions
and
what
files
to
pick
up.
B
E
Right
now,
so
you
mentioned
before,
like
yeoman,
is
easier
to
like,
extend
and
create,
like
some
sort
of
like
inheritance
chain,
for
your
generators
have
like
other,
more
specific
projects
like
taking
your
generators
and
build
even
more
like
application,
specific
generators
on
top
of
your
generator.
They
haven't
yet
a.
B
B
F
B
C
B
You
get,
you
know
you
get
an
app
that
works
right
out
of
the
box,
so
you
can
get
the
javascript
award
and
if
you
wanted
to
run
yeah,
this
is
different
pictures
about
touchdown,
so
a
blimp
touching
down.
I
don't
know
it's
a
leaf
touching
down
on
the
bricks
in
a
ball,
but
you
can
even
get
functional
tests
out
of
it.
So
it's
really
convenient.
B
B
In
there
with
it,
or
is
it
just
the
app
so
the
docs
we
have?
We
have
a
readme
for
each
one,
but
the
reading
is
very
simple.
It
basically
just
says
how
to
install
and
how
to
use
it
and
then
the
accompanying
docs
for
each
one
is
in
the
message
at
the
end,
and
it
says
you
know
we
have
an
internal
github
yahoo
and
we
have
different
wiki
pages
for
each
type.
So
we
say
when
you
build
your
app
okay,
now
go
to
this
applets
101
doc
and
to
learn
how
it
works.
B
B
What
was
nice
about
grunt
knit
before
is
when
we
did
this
grunting
it
puts
all
your
templates
at
a
grunt,
init
folder
in
your
home
directory
and
it'll.
Look
at
that
folder
when
it's
when
it's
running
and
so
what
we
did
is
we
had
a
post
install
npm
script
that
would
go
in
and
inject
the
updated
templates
into
that
location.
B
C
B
C
F
C
B
Pretty
much
the
docs
which
I
have
up
here
are
pretty
good.
We
definitely
read
the
docs
and
there's
a
lot
of
examples.
There's
you
know
an
angular
generator,
a
backbone
generator
and
then
there's
generators
based
off
those.
So
it's
the
docs
are
really
good.
I
think
you
can
follow
that
and
they
have
a
good
set
of
information
and
step
by
step
on
how
to
create,
prompts
and
all
that
stuff.
So
that's
your
friend
and
then
the
examples
that
they
come
with
as
well,
that
you
can
use
right.
C
B
Yeah,
I
think
so
right
now,
so
when
you
install
a
generator,
it's
basically
just
how
I
installed
mine
before,
but
you
would
do,
I
think
it's
generator
angular,
whatever
the
npm
package
name
is
and
then
it'll
show
up
in
this
list
when
you
do
help
so
right
now
it
shows
all
of
our
namespace
ones,
but
no,
I
don't
have
any
cautionary
tales
or
anything.
I
think,
as
long
as
you
follow
the
docs
and
examples
you'll
be
fine.
A
B
Yep
yeah,
that
was
that
was
nice,
I'm
glad
they
didn't
say
you
know
we're
not
doing
it
anymore,
see
ya
something
else
that
was
out
there
surprised
and
you
can.
You
know
you
can
still
use
it.
It's
not
going
anywhere.
I
just
you
know,
I'm
a
little
ocd
on
that
stuff
and
I
didn't
want
to
be
left
behind
and
I
wanted
to
use
yeoman
and
try
it
out,
because
I
heard
really
good
things
about
it.
So
I
think
you
know
it's
a
great
thing
to
use.
B
Yeah,
that's
what's
ironic
about
when
you
create
a
grump
plug-in
like
I,
I
was
looking
at
this
too
and
seeing
how
there's
like
grunting,
knit
grunt
plug-in
script
or
whatever
and
and
that's
still
like
the
de
facto
one
to
use-
and
I
there
like
wasn't
any
updates
with
the
yeoman
one
or
the
human
one
didn't
work
so,
but
it
seemed
like
that.
That's
it's
still
in
use,
at
least
for
people
to
create
grunt,
plug-ins
yeah.
Definitely
and
it's
yeah
it'll
be
around.
You
know
forever.
B
A
B
A
A
B
Yeah
right
I
mean
with
yeoman
right
now.
It's
it's
pretty
stable.
We've
we
haven't
had
to
do
many
updates,
it's
really
just
keeping
up
and
making
sure
we're.
You
know,
staying
up
to
date
with
the
features
that
they're
doing
that's
about
it.
It's
it's
good!
It's
in
a
good
place
right
now,
where
it's
working
great
and
it
hasn't
broken
anything
yet.
B
Well,
it's
interesting
within
media,
because
within
media
you
know
everyone's
kind
of
moving
to
what
we've
been
working
on.
So
you
know,
there's
people
interested
in
how
to
use
it
and
and
that,
but
we
haven't
seen
much
yeah,
I'm
not
sure
how
teams
are
managing
that
you
know
maybe
a
nail
or
search
or
how
they're
doing
things
over
there
with
scaffolding
I
mean
some
people
might
just
still
be
using.
You
know,
make
files
or
something
to
do
some
of
that
stuff.
So
I'm
not
sure
across
the
oregon.
Things
will
go
but
yeah
we're.
B
Well,
I
think
the
only
reason
yeah
grunting
it
only
went
away
because
yeoman
generators
came
around
so
there
wasn't
a
need
to
have
two
and
the
generators
had
just
more
feature
set
and
more
people
want
to
work
on
it.
So
it
made
sense.
So
I
don't.
I
don't
think
there
shouldn't
be
any
fear
that
it's
going
to
go
away
anytime
soon,
cool.
A
B
So
if
we
like
ship
pure
with
some
specific
media
queries
in
there,
then
you
have
to
have
those
and
there's
no
way
to
get
out
of
them
or
unless
you
override
all
the
rules
that
are
defined
inside
that
media
block.
So
we
we
realized
that
okay,
this
is
going
to
be
a
limitation.
There's
really
no
way
out
of
it.
So
what
we're
going
to
do
is
not
have
the
core
part
of
pure
contain
any
media
queries
and
the
first
step
with
that
is
to
revamp
grids
to
remove
the
the
pure
gr
class
name.
B
And
so
that's
that's
what
we
have
in
pure
0.5
and
we've
we've
shipped
an
rc
one
of
that
last
week,
and
I
think
we
announced
the
beginning
of
this
week
and
and
so
what
we
did
is
okay,
so
we
removed
this
feature.
This
was
like
a
big
feature
of
pure
having
these
responsive
grids.
So
what
are
we
going
to
do
to
to
deal
with
that?
B
And
so
what
we
ended
up
doing
is
having
a
separate
file
called
gridsresponsive.css,
and
this
contains
a
set
of
default
breakpoints
that
we
think
will
apply
to
most
devices
out
there.
We've
done
it
on
a
device
like
screen
size
basis,
and
but
then
we
realized
that
okay,
obviously
people
are
going
to
want
to
customize
these.
B
So
so
we
created
a
whole
bunch
of
tooling
around
this
to
to
one
actually
generate
the
responsive
grids
file
that
ships
with
pure
and
again,
it's
like
outside
of
the
main
pure
rollup
file,
and
it's
an
additional
include
that
you
put
into
your
page.
So
we
can
dive
right
in
and
I
can
get
the
website
up
so
so
we
we've
pushed
a
ton
of
changes
to
the
website
to
stage.pure
css.io,
so
I'll
go
into
that
now.
B
B
So
this
is
the
staging
site,
but
let
me
first
go
back
to
the
the
main
pure
website.
This
is
the
current
peer
website
and
if
you
go
to
get
started
right
here,
you're
presented
with
not
very
useful,
get
started
information,
so
this
is
kind
of
like
a
stop
gap.
As
you
can
see
in
the
menu
it
goes
to
customize
and
it,
and
it
shows
like
information
that
you
probably
don't
care
about
most
likely
so.
D
B
If
we
go
back
to
the
staging
website
and
which
I
just
reloaded
here,
it
looks
very
similar,
but
we
have
a
couple
new
things
in
the
menu
get
started
in
tools.
Let's
start
with
get
started,
so
we
have
this
completely
revamped,
get
started
page.
That
really
tries
to
almost
tell
not
not
like
tell
a
story
but
like
really
guide
you
through
the
the
beginnings
of
like
really
getting
started
with
pure,
and
so
the
first
thing
is
obviously
throw
this
this
link
on
your
page,
but
then
you
can
also
download
pure.
B
B
That
has
a
grid
a
pure
g
and
then
you
have
pure
use
inside
and
they
can
have
different
widths
and
then
we
we
went
through
and
completely
revamped
how
we
do
these
like
code,
like
these
code
blocks
and
then
show
the
examples
below.
So
this
is
running
the
code.
This
third
third
thirds
thing
here
and
what's
nice
is
like
that.
B
So
there's
there's
a
built
version
that
has
all
the
media
queries
stripped
out
of
it
and
there's
one
that
has
them,
and
so
you'd
want
to
serve
the
ones
without
them
to
internet
explorer
and-
and
the
approach
we
took
here
is
a
mobile
first
approach
to
the
css,
and
so
what
that
means
is
inside
of
the
actual
css
file.
That's
defining
grid's
responsive,
I
mean.
Maybe
I
can
just
go
to
it.
It's
probably
easier:
let's
open
it
a
tab
here.
B
Okay,
so
bump
this
up,
so
we're
we're
taking
a
mobile
first
approach
here.
So
so
what
this
means
is
like
when
you,
when
you
don't
have
any
okay,
so
I
I
should
first
start
with
well,
if
you
look
at
this
class
this
table
here,
it
has
these
class
names
and
so
the
default
one
that
ships
with
pure
is
just
pure.
B
But
then
we
have
these
media
queries
that
are
inside
of
the
grid's
responsive
file
and,
as
you
can
see,
they're
mapped
over
here
and
so
like
inside
of
this
this
this
one
that's
going
to
represent
the
small
class
names
they're
defined
here
and
and
so
what
happens
is
as
the
screen
gets.
Bigger
more
of
these
class
names
become
available
and
so,
like
all
of
a
sudden
after
768,
the
medium
one
is
available.
B
So
now
all
three
of
these
will
apply
and
there
therefore
like
the
last
one,
will
win
if,
if
an
element
has
multiple
class
names
so
like,
if
you
have
an
an
element
which
we
can
see
down
here
in
this
example,
if
you
have
an
element
with
a
you
know,
actually
tula,
I
was
thinking
we
should
probably
show
the
code
above
this.
For
that
actually
generates
this.
It
would
probably
be
handy
but
like
so
this
element
at
the
top
just
gets
a
pure
u1
class.
B
So
that's
going
to
take
up
100,
always
and
then
this
these
ones
here.
This
second
row
has
these
three
class
names,
and
so
what
what
this
will
will
mean
is
that,
after
it
hits
these
media
query
breakpoints
the
the
like
largest
one
will
win
essentially
so
in
this
case
on
large
screen
sizes.
We
want
this
to
display
one-fourth
and
that's
what
we're
seeing
here
and
now,
if
I
start
moving
this
down
now,
all
of
a
sudden
we're
no
longer
hitting
that
large
break
point
so
we're
less
than
20
10
24
pixels.
B
B
So
you
can
always
essentially
ignore
this
grid's,
responsive
css
file
here
and
just
drive.
Everything
through
css,
like
you
normally
would
by
like
manually,
writing
in
your
your
media
blocks
and
defining
them
and
then
defining
widths
in
there
and
then
just
sticking
with
peer
g
and
peer,
u
class
names,
and
so
that's
that's
one
of
the
reasons
why
we
wanted
to
separate
this
out.
But
then
the
other
reason
is
these
break
points
may
not
be
the
ones
you
want
to
use,
or
these
labels
like
sm
from
small
and
md
for
medium
etc.
B
But
since
we
did
go
with
the
min
width
here,
we
also
have
this
this
ie
version.
So
if
I
go
back
here
and
just
type
in
old
ie,
so
internet
explorer,
8
and
less
don't
support
media
queries.
So
what
we
do
is
we
basically
strip
them
out
of
this
file
and
then
just
output,
all
these
class
names
and
their
widths
all
the
way
up
to
large,
so
extra
large,
isn't
included
because
by
default,
we're
we're
saying
like
that.
B
The
the
1024
breakpoint
with
is
is
kind
of
like
this
default
for
older,
like
people
who
are
using
older
versions
of
internet
explorer
on
windows,
xp
or
whatever,
and
and
so
that
that's
what
they
get
so
then
what
that
means
is,
as
you
use,
peers,
responsive
grids
and
then
you
all
of
a
sudden
load.
Your
page
in
internet
explorer,
eight
it'll
get
the
desktop
version
of
the
layout
instead
of
getting
the
mobile
version,
and
we
we
assume
that
you
know
most
likely.
B
You
want
the
desktop
version
in
that
situation,
but
then
this
is
where
the
really
cool
stuff
comes
in.
So
so
we
thought
okay,
so
we
have
this.
You
know
this.
This
nice
set
of
defaults.
This
probably
can
apply
to
a
lot
of
projects,
but
we
understand
that
that
people
are
going
to
want
to
customize
this
stuff.
B
So
this
is
another
reason
why
we
wanted
it
to
not
be
built
into
pure
main
css
file,
because
we
we
now
have
this
ability
to
customize
pure,
and
so
what
I'm
showing
here
is
a
starter
kit.
So
this
is
a
new
thing.
We
we
developed
for
the
website
that
allows
you
to
like
configure
the
media
queries
you
want
to
use,
set
some
grid
options
like
the
number
of
columns
in
a
prefix.
B
But
if
I
come
in
here
now
and
I
say,
use
default
media
queries
the
page
updated
with
listing
out
the
exact
same
details
we
see
in
this
table.
So
this
is
just
using
the
defaults
and
what
this
did
is
it
updated
in
real
time
and
added
in
that
other
that
these
other,
this
condition
I.e
conditional
comments
around
bringing
in
the
grid's
responsive
styles
as
well.
So
this
way
now,
your
page
is
automatically
going
to
have
these
and
you
can
download
this.
B
This
will
give
you
a
zip
file
for
this,
but
then
the
other
neat
thing
is:
it's
probably
really
hard
to
see
on
my
screen,
but
the
url
is
updated
as
well
with
query
string
parameters
that
represent
the
settings
that
you,
the
these
options
and
settings
that
you
set
here.
So
this
becomes
really
powerful.
B
400
pixels-
and
you
can
see
here
this
updated
to
400
pixels,
the
url's
updated
here.
So
now.
If
I
were
to
like
refresh
this
page
and
come
back
to
it,
it's
automatically
going
to
come
back
with
my
exact
same
settings.
So
you
can
share
this
with
people
as
well,
and
this
is
all
rendering
on
the
server
side
and
then
it's
using
the
yui
app
framework
to
enhance
the
experience
by
doing
html5
push
state
routing.
B
Yeah
yeah
exactly
and
that
that
was
one
of
the
things
we
wanted
to
have
and
we
didn't
want
you
to
like
settle
these
options
and
then
all
of
a
sudden
hit
the
back
button
and
then
lose
everything
that
you
just
did.
So
we
wanted
to
keep
maintaining
that
state
of
all
these
options
that
you
might
have
set.
So
another
thing
like.
If
I
wanted
to
change
this,
I
only
need
six
columns,
so
this
automatically
updated
here
I
can
come
back
and
make
sure
that
my
media
queries
are
showing
up.
Oh
yeah.
B
B
B
B
F
The
other
reason
why
we
didn't
do
that
is
because
there
would
be
other
styles
on
this
page
that
would
conflict
with
the
preview
stuff
right,
so
we
would
have
to
figure
out.
You
have
to
show
it
through
like
an
iframe
or
something
like
that,
and
of
course,
it's
technically
possible,
but
like
what's
what's
the
use
case,
so
the
download
thing
is
really
useful,
though
yeah.
E
B
Yeah,
so
so,
what's
what's
really
cool
about
this?
Is
we?
This
website
is
being
powered
both
on
the
server
and
the
client,
with
javascript,
tooling,
using
rework,
which
is
a
css
pre
or
post
processor?
Whichever
way
you
care
to
say
that
it
is
but
rework
is,
is
something
to
allow
you
to
process
css,
and
so
it
doesn't.
B
So
so
we
have
like
an
example
here
of
generating
the
custom,
responsive
grids
and
that's.
This
is
exactly
what's
used
under
the
hood
to
power
that
web
ui
that
I
was
just
showing
and
as
you
can
see,
the
options
are
are
pretty
similar.
So
you
can
specify
the
number
of
grid
units
or
columns
and
then
the
set
of
media
queries
that
are
used
and
then
very
similarly
with
rework.
B
So
so
separating
these
things
out
in
these
layers
made
it
very
easy
for
us
to
do
this,
and
then
we
also
have
some
other
tools
here
like
this
is
one
to
strip
media
queries
to
serve
files
to
old
internet
explorer.
So
we
use
this
so
actually
pure's
own
build
process
uses
these
plug-ins
as
well
to
generate
all
these
things,
so
we're
really
like
dog
fooding
all
this
stuff
and
in
basically
every
way
possible.
B
So
yeah,
that's,
really
awesome,
and
then
we
also
went
through
and
completely
revamped
the
grid's
documentation
along
with
this
release.
So
one
of
the
things
we
have
is
like
showing
kind
of
visually,
then
also
the
the
different
fractional
class
names
you
can
use
for
for
specifying
widths
of
different
units
which
we're
now,
including
both
the
like
whole
number
widths
like
one
along
with
like
12
12
or
12
24
and
one
half
so
like
reduced
fractions
and
the
full
fractions,
which
makes
it
a
lot
easier.
B
B
So
this
makes
it
much
easier,
but
then
we
have
where
we
talk
about
the
grid
stuff
again,
but
then
we
have
these
really
nice
examples
which
show
off
the
the
power
of
the
the
grids-
and,
I
believe,
are
these
responsive.
We
should
probably
also
have
the
code
examples
yeah,
so
here
this
is
collapsing
nicely
cluster
screen.
B
F
B
So
we
have
amateur
photographers
awesome
photos
here,
which
is
cool
and
and
yeah,
so
this
documentation
has
been
revamped
a
lot
just
to
really
help
get
people
started
with
what
they're
they're
trying
to
do,
but
so
we're
really
eager
to
have
people
try
out
this.
This
new
take
on
how
to
do
responsive
grids
and
the
peers
website
itself
has
been
completely
revamped
written
in
this
way
to
be
mobile.
First,
using
this
approach
of
using
extra
html
class
names
to
define
how
the
grid
should
behave
at
different
break
points.
B
So
we're
doing
all
this
like
we're
using
it
all
all
the
layouts
have
been
adapted
that
way,
and
we
have
this-
you
know
new,
getting
started
page
which,
which
we
put
a
lot
of
time
in
trying
to
really
guide
people
through
the
process
of
getting
up
and
running
as
quickly
as
possible
and
being
successful
with
it
right
out
of
the
gate.
So.
B
Yeah
so
we'll
we'll
also
then
so
right
now,
yui
depends
on
pure
through
bauer
and
it
pulls
it
in,
and
so
once
we
get
0.5
out
in
like
the
final
release,
then
then
we'll
we'll
do
that
process
again
of
importing
it
into
yui.
We
actually
use
one
of
the
tools
to
do
that.
We
have
this.
This
rework
and
grunt
grunt
plugin
to
mutate,
css
selectors,
either
like
prefixing
them
or
replacing
them.
B
So
we
actually
use
this
in
our
process
where
we
import
pure
into
yui,
where
we
switch
out
all
the
pure
dash
class
names
with
yui
three
dash
and
that's
to
support
backwards
compatibility.
So
so
we
do
that.
So
we
have
we
talk
about
those
tools
on
this
page
as
well,
because
other
people
may
want
to
do
similar
things
so.
B
B
B
So
yeah
we're
we're
thinking
too,
that
this
approach
kind
of
lays
the
groundwork
for
how
we
want
to
deal
with
it,
this
kind
of
stuff
in
the
future.
So
things
like
skinning,
so
we've
been
talking
for
a
while
that
we
want
to
integrate
skin
builder
into
pure's
website
itself,
and
so
what
we
did
with
the
getting
started
page
really
helps
us.
Have
this
like
infrastructure
to
be
able
to
do
this
so
we're
you
know
we're.
A
B
Yeah,
definitely
I
mean
it.
We
we
think
it's
it's
going
to
be
like
it's
just
like
one
little
touch
that
we
think
is
is
going
to
be
very
helpful
to
the
person
who
tries
to
fill
out
all
these
customizations
and
then
hits
the
back
button
and
or
closes
their
browser,
and
then
they
can
just
go
back
in
their
history
and
go
right
back
to
it.
So
exactly
we
think
that
it'll
it'll
be
worth
it
in
the
end
for
those
people.
E
B
E
I
mean
like
the
only
problem
I
could
possibly
think
of
is
if
everyone
has
like
their
own,
like
individual
version
of
pure.
I
don't
know
if
that
might
be.
Issues
like
people
are
relying
on
a
specific
like
on
specific,
like
pure
class
names,
or
something
like
that
when
they're,
like
installing
from
bauer
like.
B
I
mean
so
our
plan
is
to
always
keep
the
core
pure
library
as
like
the
way
it
is
now
where
it's
like,
guilt-free
drop
it
on
your
page.
It's
like
four
kilobytes
and
just
use
use
it
even
if
you're
not
using
everything
in
it.
It's
fine,
because
it's
so
so
small,
but
you
can
also
optimize
it
because
it's
modular
as
well
and
then
you
know
you'd,
add
in
something
like
this
additional
link
tag
on
your
page
for
the
the
responsive
grids
or
your
customized
version.
B
So
I
think
that
that
that
would
be
the
approach
we
want
to
continue
going
and
maybe
providing
some
of
those
default.
Additional
files
that
you
can
include
instead
of
you,
know,
shipping
them
in
there
and
then,
if
if
people
are
doing
their
own
their
own
thing,
I
think
that
should
be
fine.
I
mean
in
terms
of
extending
the
library
to
add
more
functionality.
B
B
A
B
A
B
Yeah
yeah,
it
could
basically,
we
could
guide
people
through
the
getting
started.
Page
was
like
developed
in
that
way
like
when,
when
teal
and
I
are
working
on
it.
That's
that's
an
idea.
Tevo
came
up
with,
like
you,
wanted
to
be
kind
of
this
like
story
or
step
process,
so
it
would
fit
well
for,
for
you
know,
leveraging
already
the
the
order
and
flow
we
created
for
the
get
starting
page.
B
To
also
have
that,
be,
you
know
summarized
in
the
generator,
so
that'd
be
really
cool
yeah
and
all
this
code
is
like
open
sourced,
like
on
on
the
website
repo.
So
you
can
see
this
and
then
the
tools
page
on
the
staging
website
stage
peer
css.io
has
all
the
links
to
the
various
tool,
grunt
and
and
rework
plug-ins
that
we
wrote,
and
so
those
are
still
kind
of
in
their
infancy,
but
they're
they're
documented
enough
and
they're
all
pretty
small.
A
B
I
mean
yeah
the
the
thing
is,
you
know
we
kind
of
have
a
backlog
of
stuff
to
apply
this
similar
process
of
going
through
forms
forms.
Has
some
media
queries
in
it,
and
then
we
want
to
revamp
menus
as
well.
So
there's
those
things
that
you
know
we
still
have
on
our
plate
that
we
want
to
do
and
we're
still
trying
to
push
forward
to
eventually
get
to
1.0,
and
we
feel
like
this
is
gonna.
B
This
is
gonna,
be
a
really
big
release
because
of
all
the
stuff,
basically
in
the
documentation,
land
and
the
website,
and
really
rethinking
this
like
core
feature
of
pure,
which
is
around
grids
which
you
use
more
than
anything
else.
So
it
was
really
important
for
us
to
try
to
try
to
make
this
better
and
help
people
through
it
and
make
it
easy.
B
B
B
Yeah,
so
you
know,
there's
a
there's:
a
ton
of
people
who
are
at
least
starring
this
and
and
based
on
the
traffic,
the
the
tons
of
traffic
we
get
on
the
website,
we're
assuming
that
a
lot
of
people
are
using
this.
We,
we
should
probably
check
the
cdn
to
see
how
how
well
it's,
how
like
how
many
people
are
actually
putting
the
link
to
appear
on
their
page
by
looking
through
the
logs.
A
B
Get
us
a
long
way
and
you
know,
hopefully
we
can
reach
a
bunch
of
new
people
who
who
haven't
been
exposed
to
it
yet
or
haven't
tried
it
out
yet
with
this
release.
So
so
that's
what
we're
hoping
for.
So
we
want
to
get
it
right,
so
any
feedback
people
have
on
the
rc
would
be
super
handy
for
us
to
to
make
any
tweaks
or
adjustments
or
fix
things.
We
we
messed
up
or
forgot
about
before.
We
actually
you
know
ship
the
0.5,
because
you
want
to
you,
want
to
push
it
hard.
F
Well,
one
thing
is
that,
like
I
would
say
most
of
the
people
who
probably
use
pure
as
a
you
know
like
who
aren't
like
who
don't
check.
Github
too
often
they
probably
don't.
They
might
not
realize
that
we
have
an
rc
out
because
they
might
go
to
pure
css.io,
which
gets
a
lot
of
traffic,
but
it
looks
the
same.
F
We
still
say
0.4.2
or
something
on
the
site,
so
they
probably
don't
know
that
the
rc's
out,
but
like
the
people
who
actually
you
know,
go
to
github,
and
so
that's
why
we're
reaching
out
here
on
on
hangouts
and
we've
been
talking
about
it
on
twitter.
This
is
like
the
right
time
to
actually
give
some
feedback,
because
otherwise
we're
gonna
have
to
it's
going
to
take
a
bit
more
time.
F
F
B
I
think
it
just
depends
on
getting
some
feedback
this
week
and
and
maybe
into
next
week
and
then
we'll
make
a
judgment
call
at
some
point
soon
here
once
we
have,
we
have
a
few
tasks
open
on
the
website.
Activa
was
saying
and
we'll
want
to
close
some
of
those
out
at
least
the
higher
priority
ones,
and
then
I
think
we'll
be
ready
and
yeah,
like
I
even
tried
it
out.
So
I
have
dropbox
installed
on
my
phone,
which
I
guess
is
registered
with
ios
to
be
able
to
accept
zip
files.
B
So
I
could
customize
a
pure
starter
kit
on
my
phone
and
then
hit
download
and
it'd
save
the
zip
file
to
dropbox.
It
was
pretty
awesome
and
it
all
works
perfectly
well
on
mobile
devices,
which
you
know
we
want
to
we're.
You
know
we're
telling
people
that
they
should
do
things
this
way
like
mobile,
first
and
make
sure
things
work,
and
so
we
wanted
to
make
sure
even
our
starter
kit
builder
works
perfectly
fine
and
it
does.
B
B
So
and-
and
all
these
things
were
we're
built
out
of
the
needs
to
actually
pull
this
off.
So
it's
not
like.
We
built
these
tool,
these
tools
ahead
of
time.
It
was
we
built
them
because
we
ran
into
a
roadblock
and
we
figured
okay.
Let's
do
this
right.
Let's
make
a
tool
out
of
this,
then
we're
using
it
everywhere
and
it's
working
out
well.
A
I
also
want
to
put
a
plug-in
if
you're,
if
you're,
watching
this
and
this
kind
of
stuff
excites
you
and
you
love
working
with
css
and
javascript,
that
you
know
yahoo's
hiring
in
a
big
way,
especially
on
our
teams
and
teams
related
to
us.
So
definitely
give
us
a
shout
out
if
you
have
any
interest
at
all
in
coming
to
work
on
things
like
this.