►
From YouTube: MDN Web Docs and frameworks - What makes sense in 2019?
Description
OpenJS Foundation Collaborator Summit, Berlin, 2019
MDN Web Docs and frameworks content — what makes sense in 2019?
A
First,
a
little
bit
about
me:
I
am
Chris
Mills
and
I'm.
The
manager
of
the
content,
writers,
team
on
Mozilla's,
mdn
site
and
I
also
do
our
content
lead
work.
So
I
spend
most
of
my
time
kind
of
looking
at
what's
coming
out
in
the
web
platform
now
in
the
near
and
further
future.
Just
so
I
can
inform
my
team
about
what
we
need
to
document
and
when,
and
so
we
can
prioritize
and
have
a
hope
of
getting
the
stuff
documented
by
the
time
it
comes
on
browsers.
A
I
thought
we
made
this
my
mistake
so
when
I
find
the
time,
I
also
write
lots
of
documentation
about
HTML,
CSS,
JavaScript
and
any
other
web
tech
that
is
useful
to
people
and
I'm
a
total
accessibility
windbag
as
I
believe
everybody
should
be
so
that
kind
of
informs
and
is
a
central
theme
through
all
the
work
I
do
and
then
outside
work
I'm,
also
a
heavy
metal
drummer.
So
if
you
come
and
speak
to
me
afterwards,
please
speak
slowly.
B
C
B
A
Old,
so
why
am
I
here
then
so
I've
been
having
some
thoughts
about
how
we
could
make
mdn
more
useful
to
train
work
using
web
developers,
which
is
I,
suspect,
probably
most
web
developers
these
days.
You
know
because
then,
on
mdn
we
we
document
basically
the
whole
of
the
web
platform.
That's
our
remit,
you
know
just
little
tiny
thing
and
I
just
wanted
to
I
kind
of
think.
Well,
you
know
more
people
in
the
real
world.
A
These
days
are
using
frameworks
of
some
kind
than
are
just
writing
stuff
raw
JavaScript,
so
I'd
like
to
make
the
site
more
useful
to
these
people,
and
so
I
want
to
outline
the
plan
of
what
I've
got
in
my
head
and
and
just
get
some
ideas
and
talk
about
how
folks
could
help
if
they
want
to
get
involved.
Basically-
and
you
know,
because
I
traditionally
MD
ends
position
on
documenting
things
like
and
frameworks
has
always
been.
A
A
You
guys
just
document
react.
What
are
you
guys
just
document
angular
and
we're
just
like?
Do
you
realize
how
much
work
that
is
just
go
away?
Please
and
another
big
deal
that
we
have
on
Indiana's
accusations
of
bias.
You
know
where
were
seen
as
this
kind
of
platform
neutral
source
of
truth
of
a
lot
of
different
parts
of
the
web
platform.
So-
and
you
know
we've
had
this
in
the
past
like
that-
was
that
there
was
a
time
and
I
was
writing
some
MVC
articles,
basically
to
say
you
know.
A
This
is
basically
what
my
MVC
looks
on
the
client
side
and
I
thought.
Well,
we
need
to
use
one
framework
of
some
kind
to
demonstrate
it.
So
I
chose
ender
because
it
was
popular
at
the
time
and
even
though
I
stated
very
clearly
in
the
front
of
the
documentation
resource,
you
know
we've
only
chosen
em
but
because
it's
a
framework
that
works
right
now,
it's
not
our
favorite,
we're
not
advocating.
This
is
better
than
anybody
else.
A
A
Just
wish
it
was
a
little
bit
less
rough
around
the
edges,
but
people
seem
to
like
em,
so
there's
kind
of
three
things
that
I
would
like
to
add
to
end
the
end.
There
I
mean
for
a
start.
We
have
a
complete
beginners
documentation
section.
You
know
just
to
I.
I
wrote
most
of
that
stuff
I
like
to
think
that
it
takes
people
not
from
beginner
to
expert
the
kind
of
beginner
too
comfortable.
A
You
know
and
then
people
to
have
the
ability
to
then
go
and
use
the
rest
of
em
the
end,
because
we
were
getting
loads
of
people
saying
hey,
I'm,
a
beginner
and
in
the
end,
just
sucks,
because
it's
just
too
hard
for
beginners
and
I
was
like
right.
We
need
to
do
something
about
that.
So
I
did
but
I'd
also
like
to
add
some
information
in
the
beginner
section.
That,
though
modern
taught
them,
because
you
know
I
still
think
it's
the
best
way
to
start.
A
If
you're
a
complete
beginner,
you
should
learn
the
raw
technologies
first
before
you
go
on
to
using
all
of
the
tooling,
but
at
the
same
time,
people
are
going
to
meet
the
tools
as
they
start
to
progress
towards
working
in
the
web
industry.
So
it's
pointless
to
kind
of
at
the
moment.
I
dogs
kind
of
protect,
pretend
that
also
exists
for
the
most
part,
which
is
just
silly
so
I
want
to
have
some
kind
of
beginners.
This
is
you
know
this
is
modern
web
tool,
women.
A
What
you
need
to
know
where
you
need
to
use
different
things,
that
kind
of
section.
Of
course,
I
haven't
I've,
had
the
idea
in
my
head
for
about
four
years,
but
I
haven't
written
it
simply
because
I'm
kind
of
terrified
about
trying
to
write
it.
You
know
how
do
I
say
to
complete
beginners.
This
is
all
of
JavaScript,
tooling
and
how
you
should
use
it
when
you
should
use
it,
and
it's
just
going
to
be
a
very
hard
thing
to
rice.
A
What
boy
did
it
and
I
probably
want
to
I,
probably
want
to
have
something
that
just
says:
here's
the
high
level
concepts
of
the
different
tools
that
you'll
want
to
use,
what
they
are,
what
they
do
when
to
use
them
and
then
for
actual
low
level.
Details,
like
actual
examples,
just
point
them
to
where
different
tool,
vendors
and
documentation
instead
or
something
like
that,
and
the
second
thing
that
we
have
on
Indian
that
might
be
interesting
is,
as
I've
said
before.
A
I
remit
is
basically
web
platform
stuff,
but
we
actually
have
a
definition
of
what
that
is.
You
know
explicitly
what
we
have
on
in
the
end
written
written
down
on
the
site
somewhere
and
it's
basically
stuff
this
part
of
the
web
platform.
It
has
been
demented
in
browsers
now
the
trouble
was
we
started
getting
a
whole
load
of
folks
coming
to
a
saying,
but
how
about
things
like
epub?
A
Three,
it's
a
standard,
it's
used
in
browsers,
but
it's
not
really
neat
well,
some
browsers
have
actually
natively
put
support
3
pub
3,
but
at
the
time
it
wasn't
and
it's
like.
Well,
how
do
you
deal
with
that
lots?
People
know
about
it,
but
strictly
according
to
MTN's
remit,
it's
just
no
we're
not
going
to
document
it
and
the
same
thing
for
IMS.
A
See
if
you
folks
know
what
IMS
see
is
it's
like
a
sort
of
it's
sort
of
a
sort
of
an
alternative
to
webvtt,
so
it
does
subtitling
and
captions
and
that
kind
of
stuff,
except
apparently
it's
more
popular
in
the
main
industries
that
use
that
stuff,
like
TV
in
TV
companies
and
stuff
that
want
to
put
content
on
the
web
or
use
IMS
they
just
because
it's
more
powerful
and
buried
than
vtt
and
it's
a
bit
more
robust.
But
no
browser
has
a
native
implementation
of
it.
A
C
A
C
A
Yeah
I
think
yeah,
yeah
I,
think
that's
fair.
To
say:
I
mean
you
know,
there's
some
parts
of
it
are
natively
implemented
as
well.
It's
just
there's
a
lot
of
stuff
that
still
isn't
so,
but
yeah
we're
trying
to
get
an
X
across
again.
That's
another
huge
thing
to
document,
but
we're
getting
there
and
so
in
long
story,
short
cuz
I
have
started
to
ramble
and
I
would
also
be
interested
in
talking
to
people
from
smaller
frameworks
or
libraries.
A
So
you
know
first
and
we
could
maybe
nest
nestled,
those
in
context
inside
our
existing
reference
pages.
So
you
could
maybe
have
something
along
the
lines
of
you
know.
You
go
to
a
particular
JavaScript
method,
page,
and
maybe
it
could
say
something
like
you
know,
blah
blah
blah.
Oh,
oh,
by
the
way
this
doesn't
play
nicely
inside
react
because
of
the
way
react
is
it
is
created.
You
know
just
as
a
sort
of
a
the
vein
example
off
the
top
of
my
head,
so
therefore
to
work
around
this
problem.
You
should
do
this.
A
You
know
useful
little
pieces
of
information
in
context
and
MVM
are
sort
of
the
main
thing
I'm
looking
to
do,
and
that's
kind
of
a
bit
of
a
challenge
again,
because
obviously
there's
loads
of
information
that
could
be
represented
in
these
different
best
practices,
and
so
I'd
want
to
talk
to
some
of
the
framework
vendors
about.
You
know
what
you
know:
what
are
their
most
common
pain
points
of
people
trying
to
learn
their
framework?
What
are
the
most
common
FA
cues
that
come
up
and
they
have
to
answer
them
all
the
time.
A
This
is
a
project.
I'd
hope
would
be
able
to
provide
definitive
answers
for
those
kind
of
questions,
and
you
know
from
Indians
point
of
view.
It
would
allow
us
to
get
more
readers
and
more
readers
means
executives,
are
happy,
etc,
etc,
but
from
their
point
of
view,
it
would
be
more
of
a
kind
of
you
know.
A
This
is
friend
of
mine
called
Eric
Bailey
who
lives
in
Boston,
went
around
and
basically
added
an
accessibility
concerns
section
to
all
of
the
HTML
CSS
reference
pages,
so
for
every
single
HTML
and
CSS
property.
Now,
there's
a
little
accessibility
concerns
thing
that
says
you
know,
for
example,
for
that
ground
color.
Oh,
you
need
to
be
careful
of
making
sure
your
color
contrast
is
hi
enough
sober.
This
is
an
accessibility
problem.
A
For
what
I'd
like
to
do
is
something
more
like
to
have
a
set
of
structured
data
which
would
contain
all
of
these
different
best
practices
in
the
same
way
that
we
do
for
our
browser
compact,
a
tree
and
in
the
end
you
know
we
have
all
of
our
browser
compact
data
set
in
a
repo
which
is
github.com,
slash,
md,
n
slash
rather
compact
data
browser
comp
that
data
separated
by
hash
and
those
lying
things
yeah.
My
brain
has
just
gone:
you're
40
now
you're
having
a
senile.
A
So
we
have
all
that
information
in
structured,
JSON
files,
and
then
we
just
use
a
macro
to
splurge
io
into
the
different
MDM
pages.
I
probably
want
to
do
something
more
like
that
for
this
set
up
as
well
and
first
of
all,
because
it
would
be
a
lot
easy
to
do.
Math
updates
and
things
to
the
information,
then,
if
it's
instructive
data.
Secondly,
because
it
could
then
be
used
in
all
sorts
of
different
places,
you
know
as
well
as
it
just
being
useful
at
the
end.
You
know,
for
example,
again
taking
reactors.
In
example.
A
A
E
A
Would
be
fine
if
it
will
be
imported
yeah
if
they
wanted
some,
you
know,
maybe
maybe
if
they
have
their
documentation
somewhere,
but
it's
not
looking
so
good
and
they
just
want
to
use
kind
of
in
the
end
structure
and
stuff
to
make
it
look
better
and
make
more
sense
that
I
would
also
be
ok,
but
I
do
want
to
make
sure
what
we
don't
get.
You
know
documentation
updated
in
two
places,
but
yeah,
ok
at.
B
A
A
That
would
definitely
be
very
clearly
stated,
you
know,
or
all
the
beginners
information
I
write
has
a
kind
of
you
know
when
you
first
get
to
it
very
clearly
says
you
know.
This
is
what
you
should
these
your
prerequisites
for
reading
these
docs
and
you
know,
please
go
back
and
read
these
bits.
First,
if
you're
not
really
clear
on
them,
just
to
make
sure
that
you
understand
the
whole
kind
of
situation
so
but
yeah
you're,
absolutely
right.
Is
there
a
serious
concern.
C
So
since
we're
at
the
historically
nodejs
clapper
or
something
I'm
wondering
the
kind
of
framework
like
for
things
right
guys
that
are
in
common
between
node
and
the
web,
there
aren't
just
JavaScript
like
set
timeout,
or
it's
kind
of
in
common
I,
just
checked
I
know
I
mean
it's
great
to
have
node
competitive
the
year.
For
that
one
there's
there.
If
we
wanted
to
document
it,
then
we
might
have
a
section
that
knows
differences.
Do
you
think
this
kind
of
stuff
would
be
good
for
Indian
yeah.
A
C
A
This
this
is
the
thing
I've
I
haven't
really
played
so
much
of
the
scope,
yet
I'm,
just
kind
of
at
the
moment,
sore
casting
they're
as
wide
as
I
can
just
to
see
what
might
make
sense
kind
of
thing.
And
then
you
know
before
tool,
I'm,
probably
going
to
arrive
on
some
sort
of
sensible
scoping,
which
will
only
just
true
to
remain
sane,
while
I'm
trying
to
kind
of
Shepherd
all
of
this
stuff,
yeah.
D
A
D
B
B
A
A
A
lot
of
interest
in
this
nicely,
thank
you,
I
mean
I,
suspect
I'd,
probably
put
that
kind
of
article
as
part
of
the
beginners
tool
in
kind
of
yes
of
module
Docs,
you
know
just
like
you
know.
This
is
frameworks
and
by
the
way,
you'll
come
across
a
whole
ton
of
them
and
here's
the
advantages
and
disadvantages,
and
we
could
just
sort
of
make
an
effort
to
keep
that
up
to
date,
and
you
know
cuz
like
this.
This
is
another
thing
I've
started
this
year.
Is
the
idea
of
the
M
this.
B
B
A
Do
contribute
in
different
ways
of
suppose,
like
I
think,
with
with
the
beginners
tutorials,
people
tend
to
contribute
a
lot
in
kind
of
just
fixing
grammatical
errors,
reporting
things
that
don't
make
as
much
sense
as
they
should
you
know
just
so.
That's
that's
also
really
useful.
You
know
the
idea
that
we
we
try
and
write
a
stuff,
those
free
of
idioms
or
slang
and
things
as
possible
just
to
make
sure
that
it's
understandable
for
people
who
perhaps
English
isn't
their
first
language.
So
that's
always
useful
feedback
to
get.
A
A
What
point
the
critical
mass
right
people
actually
start,
looking
on
the
damn
thing:
yeah,
because
they,
you
know
and
I
was
saying
this
is
somebody
else
earlier,
like
II
the
problem
you
tend
to
find
in
terms
of
contributing
to
something
like
mdn.
Is
you
know
that
the
site
has
a
lot
of
gravitas
in
the
industry?
Therefore
you
get
a
lot
of
people.
A
You
know
know
next,
I've,
known
kind
of
known
experts
in
various
subjects
but
I
know,
would
have
a
very
authoritative
voice
and
be
great
to
edit
thing
a
or
thing
they
come
to
me
and
say:
well,
I've
noticed
this
problem,
but
I
don't
feel
like
I
should
really
edit
it
because
I
don't
know
if
I'm
really
supposed
to
or
whatever
and
I'm.
Just
like.
D
E
Somehow
I
don't
know
how
they
pull
issues
and
like
into
the
in
line,
which
is
a
nice
thing
of
like
here's,
a
way
to
kind
of
go,
see
what's
happening
on
get
over
on
whatever
platform
you're
using
inside
of
this,
and
like
kind
of
have
as
your
comment
section
except
have
it
be
in
a
useful
way.
That's
like
issues
mm-hmm,
so
that
might
be
something.
E
A
A
Can
you
imagine
the
amount
of
stuff
extra
maintenance
that
would
open
up
yeah
in
actual
fact
having
it
regulated
in
some
way,
like
it
of
issues
attached
to
pages
or
something
I'd,
be
quite
interesting
in
fact,
worth
long
term,
we're
aiming
to
move
like
the
whole
of
mdn
just
over
to
get
up
completely,
just
as
a
huge
set
of
structured
data,
because
it
will
be
so
much
more
useful
in
so
many
ways,
but
there
for
the
moment
we're
stuck
on
the
archaic,
wiki's
that
work
again
like
we.
Could
you
give
the
we
could.
F
F
Now
I
can
I
have
this
49er
flight
and
I'm
disconnected
I
can
still
accept
I
realize
it.
You
know
that
actual
library,
I
don't
have
to
das
board,
because
I
forgot
to
create
no
J's
directory
and
like
try
to
peek
into
the
the
no
modules
border
and
like
scrape
the
information
out
of
the
park,
now
readme
files,
and
so
I
was
like
yeah
I'm,
just
gonna
make
a
making
package
for
this,
so
it
can
be
installed
actually
and
it
can
be
used
on
flying
like
a
documentation
of
this
particular
package.
F
The
next
time
I
use
this.
They
realized
that
the
format
is
super
complicated
for
for
making
this
like
scrapers.
It
monitors
tripping
all
the
information
out
which
actually
comes
back
to
you.
If
we
would
start
pulling
in
the
information
like
what
they
would
probably
want,
freiburg
offers
itself
to
contribute
that
documentation
in
Kiev,
which
kind
of
raises
the
question:
is
there
going
to
be
like
Andean
format
or
like?
How
are
you
gonna,
try
to
like
it
is
raised?
I
was
trying
to
standardize
some
of
that.
A
Then
the
idea
would
definitely
be
to
keep
these
different
best
practices
fairly
short
and,
if
there's
more
information,
if
as
if
there's
a
whole
ton
more
information
about
a
particular
thing
that
you
want
to
get
across,
you
probably
just
want
to
summarize
it
in
the
actual
best
practice
and
then
just
link
out
to
a
separate
blog
post
somewhere,
because
otherwise
the
pages
that
just
become
chaos.
So
we
need
to
think
about.
B
B
Whatever
right,
they
all
have
changing.
Others
like
constant
core
questions
like
it
means
like
the
rapid
speeds,
like
reverberation,
is
kind
of
like
it's
at
a
conflict
with
a
pace
that
you
know,
but
the
peace
I
think
in
bandwidth
for
your
team
inside
I'm
curious,
like
I,
just
I
really
introduced
to
cut
the
driving
factors
were
her
like
you
wanted
me,
because
I
think
there
was
public
there
I'm
sure
there
are
lots
of
clear
driving
factors
and
I'm
curious.
It
kind
of
shift
your
driving
factors
off
of
them.
Vienna.
A
It's
it's
totally
reasonable
opinion
there
yeah
I
mean
this
this.
This
is
why
I'm
talking
about
it
being
some
sort
of
a
separate
structured
data,
things
that
we
can,
you
know
kind
of,
create
whatever
we
want
out
of
it
and
have
it,
maybe
in
some
sort
of
standardized
format
and
would
also
be
a
bonus
side-effect
of
that
as
well
and
I'd,
quite
like
it
to
still
that,
we
could
still
have
it
in
a
way
that
would
allow
me
to
kind
of
just
take
useful
snippets
out
and
put
them
in
place
as
an
NBN.
C
What
I
see
from
your
document
is
that
what
I
hear
from
you
as
well
is
that
keeping
with
the
spirit
of
Indian
and
helping
people
really
learn
and
understand
where
the
eyes
want
to
be
able
to
give
them
the
relevant
information
that
might
be
information
that
might
be
relevant
to
the
frameworks
were
already
using,
so
that
they
can
better
utilize.
They,
yes,
they're,
seeing
and
using
and
when
I
think
about.
In
the
end,
one
of
the
most
unequal
type
Indians
might
preferred.
E
C
True
and
the
way
that
I
encounter
Indian
documentation
is
typically
when
I'm
stuck
I'm
searching,
because
you
guys
have
any
rentable
domain
authority.
You
know
you're
at
a
very
top
of
the
results
page
typically
and
so
I
agree
that
specifically,
if
you
already
said
it
yourself,
but
you
know
it
would
be
duplicating
where
try
to
have
documentation
for
frameworks
maintained
in
two
places,
which
is
basically
a
magnetic.
D
C
Also
puts
it
in
a
place
where
people
are
useful
or
is
useful
for
people
and
that
you're
stuck
on
the
wiki
style,
so
that
can't
directly
change
but
I
think
one
of
the
most
useful
things
that
you
have
is
links
link
ability
within
Indian.
You
know,
I
everyone's
gonna
fall
down
a
hole,
right,
learn
so
much
I
didn't
know
it's
there
by
following
links
on
your
site,
so
I
I
would
be
I
really
liked.
C
We're
talking
about
full
reviews
and
being
useful
to
people
at
all
different
levels,
essentially
so
I
think
something
like
an
article
where
the
difference
between
JavaScript
and
ojs.
That
would
be
one
super
helpful
to
a
lot
of
people
and
to
with
your
domain
authority.
It
would
be
very
discoverable,
so
I
think
that,
and
also
specifically
it
ages.
Well,
in
that,
that's
not
going
to
change
as
rapidly
as
you
know,
like
react,
coming
out
with
a
new
version,
etc,
etc.
So
I
think
maybe
it
would
be
a
good
place
to
start,
might
be.
C
Having
like
a
landing
page
for
a
specific
framework
like
say,
Indians
react
tips
or
whatever,
and
maybe
that
would
be
where
the
structured
data
would
initially
live.
It
was
like
you
know:
here's
a
bunch
of
tips
that
have
been
contributed
at
cetera
and
they
can
link
you
out
to
other
parts
of
the
website
and
then
maybe,
potentially,
once
you
get
it
figured
out,
you
can
pull
in
those
those
tips
into
those
relevant
link,
pages
and
I
feel
like
that
kind
of
content
with
age
really.
C
Well,
especially
what
you
were
saying:
the
differences
between
different
frameworks,
because
the
domain
Authority
Indian
has
that
would
be
I
can
don't
have
a
lot
of
people
and
it
doesn't
change
nearly
as
fast
as
the
actual
API
frameworks
and
most
of
these
maintainer
zone.
These
smaller
frameworks,
they
likely
don't
have
the
time
or
desire
to
maintain
Docs
in
two
different
places.
So
you.
E
C
The
entire
point
of
it
so
like
having
a
single
page,
eventually,
there's
no
real
point
in
having
it
be
on
Indian.
The
point
of
being
on
and
being
is
that
it
speaks
to
two
different
articles
and
the
JSON
I
thought.
The
tooling
that
you
described
sounded
like
a
great
idea.
I
think
it's
something
a
great
idea
to
it's.
Just
until
that
is
set
up
and
in
place,
I
think
that
it
would,
it
would
be
easier
to
maintain
for
the
people
contributing
the
stuff,
as
well
as
the
Indian
team,
if
they
were
I
mean.
B
A
It's
certainly
a
reasonable
concern.
What
you're,
saying
and
I
you
know,
part
of
me
sort
of
sits
there
and
things
yeah
be
a
hell
of
a
lot
less
effort
just
to
do
on
your
say,
I,
quite
like
both
approaches
that
I
could
see
what
the
sort
stuff
you're
saying
would
actually
live
very
well
in
this
kind
of
beginners
to
wing
kind
of
thing.
I'm
talking
about
creating
and,
and
it
might
be,
like
a
lower
maintenance
place
to
start.
While
we
do
get
some
of
the
tooling
set
up
so
I
think
both
approaches
could
potentially
work.
A
I
mean
another
thing
that
you've
kind
of
alluded
to
and
what
you
said
is,
like
I
talked
about
having
these
little
tidbits
away,
we're
going
to
call
them
strictly
speaking
in
in
context
in
appropriate
places,
but
things
don't
necessarily
have
to
be
on
exactly
the
right
pages
for
people
to
just
go
and
find
them,
because
this
is
the
web.
You
know.