►
Description
An open forum to chat about all things YUI and Front End Engineering
A
If
anyone
has
any
questions,
I
can
kick
things
off
with
back
in
at
yy
conf
2013,
we
had
a
sort
of
a
roundtable
discussion
about
documentation
and
a
lot
of
people
were
giving
feedback
regarding
needing
better
documentation
and
tutorials,
and
things
like
that.
So
one
thing
that
got
me
thinking
was:
we
have
quite
a
bit
of
documentation,
but
we
don't
have
a
sort
of
good
framework
to
display
the
documentation.
There
are
a
lot
of
tutorials.
A
A
So
what
I
did
is
I
I
worked
on.
I
looked
at
a
number
of
websites,
including
udemy
and
codeacademy,
and
things
like
that
and
how
they
they
organized
the
content
that
they
created,
and
I
sat
down
and
thought
about
how
I
could
look
at
the
content
that
we
have
and
how
to
organize
that.
So
what
I
did
is
I
came
up
with
something
called
learning
paths,
and
this
is
a
sort
of
experimental
project
that
I'll
be
hosting
up
on
stage
yylab.com
in
a
few
days
once
it
gets
past
the
pr
process.
A
Folks
on
irc
are
asking
me
where
my
my
suit
is,
since
I'm
supposed
to
be
doing
a
self
interview
here,
all
right,
so
here
we
have
the
the
yy
library
regular
website.
This
is
my
local
stage
environment
and
that
way,
since
it's
not
hosted
on
stage
yet
in
the
outside
world,
I'll
show
you
my
local
version,
basically
under
documentation.
You
can
see
the
standard
things
I
had
before
now:
yeah
iqs
tutorials.
B
A
B
A
All
right,
anyway,
back
to
what
we're
talking
about
so
learning
paths
basically
are
like
guided
tours
around
the
wide
range
of
yy
documentation
with
videos
slides
examples.
Basically,
you
just
choose
a
path
that
reflects
the
current
level:
knowledge
that
you
have
in
yy
and
proceed
enjoy.
That
will
take
you
to
things
to
the
next
level
or
if
you
have
a
specific
goal
in
mind,
such
as
application
development
or
you
can
choose
a
path
that
focuses
on
that
aspect
of
why.
A
A
I
kicked
things
off
with
talking
about
sort
of
the
background
behind
it.
Where
back
at
yy,
conf
2013,
we
had
a
discussion
about
documentation
and
trying
to
come
up
with
a
framework
for
the
kind
of
documentation
that
we
already
have
so
like.
I
said
I've
gotten
a
number
of
sites
like
udemy
and
code
academy,
and
things
like
that,
and
I
know
that
we
have
a
lot
of
content
out
there,
but
there's
not
a
really
good
structure
around
it.
A
A
A
We
could
have
things
where
you
have
a
intermediate
level
or,
if
you're
an
expert,
and
you
want
to
find
out
more
about
like
say
promises,
there
could
be
a
path
around
promises
where
it
might
take
you
through
a
video
tutorial
or
you
might
like
you
know,
get
to
chat
with
juan
directly
or
things
like
that.
So
yeah,
that's!
The
idea
is
that,
once
you
go
through
one
of
these
paths,
it'll
take
you
from
once.
You
get
to
the
end.
You'll
feel
like
you
have
a
competency
in
that
path.
Awesome.
A
A
One
of
this
one
is
unique
in
that
this
is
like
the
beginning
path.
So
before
we
jump
you
right
into
the
path
itself,
we
talked
a
little
bit
about
the
javascript
itself
so
that,
if
you
are
coming
here
and
you're
not
familiar
with
javascript,
this
is
not
going
to
you're
not
going
to
get
very
much
out
of
this
until
you
get
that
background.
A
A
It
starts
off
with
answering
the
question
why
why
ui
and
I
featured
a
video
from
evan
goer,
so
I'm
gonna
go,
show
you
that
so
basically
you
get
the
guide
post
you'll
see
the
first
one
show
up
you
hit,
go
and
it'll.
Take
you
off
to
some
content.
The
content
may
be.
Video
could
be
a
tutorial.
It
could
be
anything.
That's
that's
a
resource
online
from
there
ideas
once
you
finish,
that
you
come
back
to
the
site
and
it
will
remember
where
you
are
in
the
path
cool.
A
So
that
is
the
site.
If
you
jump
to
like
uifx
and
you
go
to
the
animation
library,
the
idea
is,
you
might
you
know
the
next
day
come
back
and
it'll
remember
where
you
are
and
take
you
straight
from
there.
So
it's
a
very
simple
idea,
but
the
the
cool
part
about
this
is
these
are
sort
of
curated
content.
A
This
is
something
where
someone
who's
an
expert
or
someone
who's
really
confident
in
their
ability
to
create
these
paths,
develop
them,
and
then
they
give
that
content
out
to
the
world,
and
the
idea
is
that
you're,
not
creating
new
things,
you're
just
curating.
The
stuff
that
we
have,
and
so
who
can
contribute
to
these
right
now
like
this,
is
something
that
we
can
have
like
the
community
help
out
with
yeah.
A
No
problem
I've
been
kind
of
swapping
back
and
forth.
The
idea
for
this
is
that,
if
there
is
interest
in
this,
we
could
set
up
a
file
in
say
the
docs
directory
of
yui.
I'm
not
going
to
go
over
like
how
this
is
or
how
this
is
structured.
So
let
me
just
jump
to
that
so
ideas
again,
once
you
get
to
these,
you
get
to
the
end,
you
can
actually
skip
through
them
once
you
get
to
the
end,
you've
completed
that
task
and
you
can
work
your
way
back
to
another
pathway.
A
So
the
content
itself
is
really
simple.
The
the
the
site
handles
basically
consumes
a
json
file,
and
the
json
file
looks
like
this.
You
have
idea
of
path
info
which
is
sort
of
the
metadata
about
a
path
that
will
show
up
on
the
past
selection,
page
and
inside.
You
have
path,
content
and
within
the
path
content.
You
have
the
the
name
of
the
path,
and
then
you
have
the
list
of
guideposts.
Each
guidepost
consists
of
a
title,
a
thumbnail
image.
You
get
a
description,
and
then
you
have
this
idea
of
sub
links.
A
The
great
thing
about
the
sub
links
are:
they
are
supplemental
information
that
basically
flesh
out
this
guide
post.
Sometimes
one
link
is
not
enough.
Maybe
you
want
to
have
like
examples,
or
maybe
you
want
to
do
even
like
a
survey
at
the
end
or
something
like
that.
So
the
point
of
this
is
that
you
basically
build
out
this
just
json
file
and
right
now,
there's
of
course
just
have
one,
but
I
have
ideas
that
if
the
community
wanted
to
build
these,
we
could
put
this
up.
A
Yeah,
exactly
and-
and
the
idea
is
that
this,
since
this
is
just
json
content,
you
know
the
the
view
that
we
do
for
the
site
is
one
view,
but
other
people
could
write
other
other
finance
for
this
kind
of
stuff.
They
could
just
use
this
as
data
as
well,
so
you
might
imagine
in
an
ide
or
something
like
that.
If
you
wanted
to
see
tutorials,
you
could
just
show
up
on
the
sidebar
or
something
like
that
using
this.
A
So
that's
the
idea,
and
this
is
the
concept
it's
it's
working
now
and
I
think
it's
it's
a
good
sort
of
like
first
step.
The
the
main
reason
for
me
talking
about
today
is
to
see
if
anyone
else
has
the
interest
in
it
where
it
can
go
from
here.
I
know
that
there's
a
lot
of
improvement
in
terms
of
like
the
ui
right
now,
it's
just
a
list
of
items
it
could
be.
C
C
Like
it
to
your
github
account
like
the
example
will
be,
and
then
maybe
I
don't
know,
maybe
you
could
like
have
it
like
clone
sample
like
tutorial
repository
and
have
them
like
fill
in
like
some
things
in
there
and
make
some
changes
to
that
repo
and
then
once
they
do
that
and
commit
it
like.
Maybe
that
could
be
another
like
guideposts
or
something.
Oh,
I
see
what
you're
saying
is
it's
sort
of
like
how.
A
C
A
A
And
things
like
you
know,
like
here's,
you
know
code
academy.
Has
these
great,
you
know
getting
started
with
programming
things
where
they
they
start
you
off,
and
I
think
that's.
This
is
really
valuable
too.
So
that's
that's
sort
of
the
content
area
and
what
I
wanted
to
address
with
this
was
like
the
curation
side.
Okay,
so
for
me
this
is
like
someone's
been,
someone
really
knows
a
lot
about
javascript
and
they
know
about
why.
A
A
A
I
think
in
the
future,
if
we
know
that
there's
not
a
couple,
people
will
just
do
laptops
yeah.
Definitely
I
guess
I
could
keep
my
screen
sharing
going,
but
so
the
idea
about
the
second
thing
I
want
to
talk
about
is
one
thing:
I've
been
thinking
about
for
a
while
is
sort
of
the
state
of
yys
like
issues
list
and
pull
requests
in
a
lot.
If
you
see,
if
I
have
this
like,
I
wanted
to
show
it.
A
You
can
see
how
how
our
the
all
of
them
have
been
increasing
rapidly,
especially
in
the
past
month,
the
the
amount
number
on
of
community
involvement
has
increased
by
then
it
talks
about
lifelines
for
slow
pull
requests,
so
it
basically
shows
you
that
the
longer
and
older
a
pull
request
is
the
longer
it's
taking
to
get
closed
out
and
the
ones
that
are
like
moving
all
the
way
to
the
right.
Those
are
the
ones
that
started.
A
A
Nearer
ones
are,
of
course,
you
know,
still
live,
but
the
ones
that
are
these
ones
that
are
long
bars.
These
are
the
ones
we
want
to
try
to
get
rid
of
exactly
and
then
source
commits,
and
then
there's
this
idea
and
this
one's
really
nice.
The
commit
it's
from
the
project
community,
as
a
percentage
of
total
commits.
C
A
That
the
community
involvement
is
going
up
way,
high
yeah
and
I
think
that's
it's
good
and
bad.
I
think
one
of
the
things
is,
you
know
the
number
of
of
like
the
number
of
commits
as
relative
to
the
number
of
people
working
on
the
project
right,
so
I
think
our
committer
list
has
grown
as
well.
So
that
also
means
that,
as
we
get
more
pull
requests.
C
In
we
need
more
of
those
to
offset
exactly
so
we're
definitely
looking
for
other
people
definitely
outside
of
like
our
team
right
now,
and
definitely
if
you're,
someone
who
uses
like
yui
heavily
and
you
want
to
become
a
committer
I'll,
definitely
like.
Let
us
know
we
can
like
help
guide
you
to
like
make
the
right
like
prs,
help
solve
some
issues
and
then
we
can
definitely
get
you
computer
status.
So
that's
what
they
want
to
talk
to
you
about.
C
A
I
think
it
says
like
it
has
to
be
more
than
bug
fixes,
so
maybe
doc
fixes
or
something
that'd
be
a
better
lower
bar,
and
then
you
can
see
here.
The
number
of
committers
and
comments
like
has
increased
over
time
too.
So
I
feel
like
if
you
look
at
these,
it
just
shows
that
why
why
the
project
is
very
active
and
live
and
vibrant,
so
none.
A
Pull
request
so
one
of
the
links
off
of
the
open
round
table
link
is
the
stale
pull
request,
link
and
it
basically
shows
the
least
recently
updated,
pull
requests
so
and
the
criteria
for
this
is
anything
that's
older
than
a
week
and
anything
that's
marked
as
work
in
progress,
so
I'm
going
to
skip
through
and
look
at
some
of
the
ones
that
some
of
the
ones
that
are
internal,
we
don't
really
need
to
look
at,
but
I
think
the
oldest
one.
That
is
oh
yeah.
Let's
do
this.
A
C
C
A
Sounds
good
next
one
is
uploader
bug,
fix
and
improvement.
I
think
we
already
talked
about
this
one
I
mean
a
lot
of
these
are
like
they
they've
been
around
for
a
while.
So
one
thing
I
like
to
talk
to
you
about
potentially,
is,
if
something's
been
around
for
just
a
huge
amount
of
time
and
there's
no
activity
on
it.
Is
this
worth
just
close?
So
I'm.
C
C
So
that's
so
a
few
of
these,
like
wips,
don't
seem
like
they
have
any
activity
on
them
in
a
while,
so
for
those
those
I'll,
probably
close
out
for
the
ones
that
seem
like
fairly
stable,
I'm
gonna,
but
they
don't
have
like
tested
on
documentation
right
I'll
see.
If
I
can
just
like
write
those
for
those
people
and
get
those
in
that's
cool.
A
A
C
So
you
let
you
do
that
yeah.
I
believe,
there's
that,
oh
okay,
that's
cool!
You
just
have
to
test
them.
At
the
same
time.
No,
I
think
you
can
just
basically
take
the
output
of
different
yeti
runs
and
then,
once
you
take
the
different
output
of
those
yeti
ones,
then
you're
able
to
just
like
combine
them
together.
Is
it
through
istanbul
or
yeah,
there's
a
tool
that
would
yeah,
I
think
istanbul.
It
should
be
built
into
istanbul,
cool.