►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-07-29
Description
Learn more about the work of the IPFS Docs & Developer UX Working Group and how to join our weekly syncs: https://github.com/ipfs/docs
Notes: https://docs.google.com/document/d/1EOD-pJi4GvRmGi9HHocgVV8uVHMFIZlyVgJDkvC3DQ4/edit#heading=h.i9h3fdwsr8q7
B
Can
take
notes
too,
let
us
begin.
A
Okay,
so
I
guess
I
can
jump
straight
into
more
technical
implementations
and
things
I'll
be
looking
at.
We
have
a
an
ever
growing
Docs
sort
of
spreadsheet,
with
some
features
and
lists
and
ideas
that
we
were
trying
to
collect
together.
It
started
off
initially
as
a
sort
of
overview
of
current
documentation
sites
that
we'd
like
and
rather
than
focusing
too
much
on
the
technology
side
of
things,
because
I
think
a
very
important
piece
of
this.
A
So,
yes,
this
kind
of
started
off
with
some
oversight
of
all
the
various
documentation
platforms
and
from
either
from
platform
level
products
or
also
application
level,
stuff
and
language
orientation.
So
we've
looking
at
all
these
different
websites
and
trying
to
figure
out
what
some
common
ground
between
them,
what
we
think
would
be
actually
successful
for
for
verax
documentation.
Some
of
it
is
very
simple
and
actually
I
think
a
lot
of
the
problem.
A
Space
is
more
about
the
navigation
from
the
get-go
to
getting
started
kind
of
orientating
people
to
go
to
the
right
parts
and
documentation,
but
then
of
he
went
further
into
current
existing
solutions
out
there
that
we
could
use
that.
Maybe
would
help
us
bootstrap
some
of
this.
These
options
and
really
the
feature
set
list-
was
this
one
here.
A
A
Customization
is
quite
important
for
us,
so
we
can
embed
different,
different
widgets
and
things
that
we
want
to
use
for
various
analytics
and
tracking
internationalization
for
obviously
translation
and
see
where
to
get
up
to
work
with
transifex
we've
currently
got
and
then
there's
there's
a
various
like
lower-level
things
like
all
the
way
down
to
how
we
edit
things
like
with
markdown
MDX,
making
it
most
accessible
and
then
search
being
hurry.
A
big
priority,
because
I've
seen
discoverability
is
the
main
issue
right
now.
A
So
I
think
Search
Search
for
me
is
gonna,
be
like
the
main
focus
for
a
lot
of
this,
because
we
can
never
completely
create
a
navigation
or
an
architecture
of
where
we
will.
You
know,
have
a
narrative
from
A
to
D
for
every
poem,
every
particular
audience
so
yeah,
so
search
can
be
a
big
focus
and
their
goal
is
actually
one
of
the
things
is
using
a
lot
of
products
right
now,
but
it's
it
kind
of
bells
down
to
two
overall
directions.
A
From
my
perspective,
which
is
essentially
either
gasp,
you
are
into
product
something
that
we've
got
enough
resource
and
development
inside
a
PL
to
help
build
this,
but
also
it's
quite
accessible,
the
Zoological
platform
and
then
potentially
a
an
alternative
which
would
be
using
something
like
docker
source,
which
is
very
heavily
inspired
by
Gatsby,
but
also
Jess
open
source
project.
That
is
evolving
quite
rapidly.
But
it's
also
got
some
very
big
limitations
right
now
with
terms
of
steam
ability
and
customization
and
to
see
hem
from
Mali.
C
My
question
was:
how
do
these
things
fit
into
the
development
process?
So
one
of
the
big
things
is,
we
haven't
done
a
great
job
at
keeping
our
documentation
up
to
date,
and
part
of
that
is
engineers
who
are
updating
should
be
updating
the
documentation,
don't
know
where
the
documentation
that
they're
supposed
to
be
updating
lives
and
some
of
it.
C
It's
just
it
atrophies,
because
there
are
pieces
of
this,
that
we
haven't
automated,
that
maybe
we
could
have,
or
at
the
very
least
we
haven't
tested
that
we
could
have
so
that
we
would
have
a
feedback
loop
of
when
we
are
and
aren't
doing
as
effectively.
So
what
are
the
options
for
these
two
platforms
around
hooking
this
into
things
like
CI
running
tests
over
our
Doc's
coverage,
things
along
those
lines
that
are
going
to
help
us
make
sure
it
stays
accurate,
yeah.
A
On
top
of
it
maybe
highlight
problems,
or
at
least
when
we
publish
new
versions
of
the
API
that
will
say
like
have
you
reviewed
this
documentation,
or
this
was
this,
because
if
we,
if
we
flag
certain
Doc's
in
in
the
platform
as
be
in
version
specific,
then
we
can
run
tests
against
that
to
say
that
and
make
sure
that
this
version
was
current
with
the
the
API
changes
and
right
now,
there's
only
really
that
has
versioning
baked-in
off
the
bat
is
actually
docu.
Saurus.
A
Yeah,
so
we
we
can
do
sort
of
version
level,
API
Doc's
for
individual
platforms
and
that'll.
Allow
us
then
dig
into
and
see
how
change
logs
for
things
it's
just
really
really
nice
and
very
flexible.
The
potential
downside
is
that
we
would
then
have
multiple
websites
for
each
implementation,
which
is
kind
of
what
we
have
right
now
and
we'd
have
various
different
layers.
A
That
I
represent
that
so
I
want
to
make
sure
that
we
can
be
consistent
with
all
the
representation
that
exists,
Eiling,
the
navigation
between
it
between
them
all
the
search
engine
can
like
jump
you
off
towards.
If
you
want,
if
you're
looking
at
a
go
level,
implementation
or
jeaious
level
one,
but
from
what
I
seen
from
various
other
product
right
now,
they're
kind
of
keeping
that
lots
the
very
separate
anyway,
so
I
reckon
we'd
end
up.
We
just
have
having
like
a
you
know:
core
go
implementation
site.
A
A
So
yes
and
the
next
steps
really
for
me
and
I
was
talking
with
Eric
last
week
about
this.
So
it's
just
more
about
now
I've
kind
of
come
to
this
potential
crossroad.
It's
like
figuring
out.
What
are
the
limitations
of
these
two
routes?
How
much
development
time
do
we
want
to
put
into
into
some
of
these
directions
or
whether
or
not
we
want
to
whether
are
any
limitations
with
some
of
the
options
we
want
to
actually
deploy?
Some
of
this
work
so
I
think
hosting
an
idea.
A
A
That's
we
can
contribute
back
to
and
essentially
does
help
the
whole
ecosystem
rather
than
building
a
complete
respect
solution
for
ourselves
and
but
then
a
Gatsby
approach
might
give
us
some
some
of
that
greater
flexibility
longer
term,
and
then
we
could
also
that
could
potentially
build
into
like
a
documentation
platform
for
the
entirety
of
PL
and
all
the
projects
of
people
that
we
use
like
a
female
way.
So
that's
roughly,
where
I'm
at
with
this
piece
that
I'll
just
jump
ahead
to
what
I'm
currently
doing
with
the
quiz
as
well.
A
So
Eric
is
also
we're
working
this
together
to
kind
of
give
people
some
guidance
into
IB
FS
and
understand
the
current
limitations
from
when
you
come
on
to
the
homepage
like
why
what
I'm
going
to
do
with
this?
How
can
I
get
started
so
I
was
kind
of
looking
at
some
potential
ideas
of
just
simplifying
the
homepage
and
changing
the
terminology
around
this
as
well.
So,
instead
of
being
like
try
it
and
making
it
feel,
like
you
know,
you're
experimenting
with
things.
A
That
will
give
a
very
broad
overview,
and
there
actually
are
some
good
community
ones
out
there
that
maybe
we
could
just
piggyback
on
in
the
mean
time
and
use
as
our
highlight
features
and
then
yeah
things
like
trying
it
rather
than
saying.
Let's
guess,
let's
get
started,
I'll
push
them
into
the
quiz
funnel
and
essentially
say
that
I
am
a
developer
or
I'm
a
and
a
server
manager
or
working
in
enterprise
or
I
am
contributor.
A
I
want
to
help
out
with
the
project
and
then
given
people
some
various
different
options
of
what
they
can
do
when
they
go
down
those
steps
and
yeah,
then
just
basically
trying
to
do
a
little
bit
of
an
audit
over
current,
the
current
language
were
using
where
it
says,
like
install
implementations,
getting
started
whatever
I
just
try
and
simplify
it.
So
we've
always
got
the
same
sort
of
approach,
and
this
is
something
I
need
to
discuss
with
Eric
he's
not
on
a
call
right
now,
but
I'll
catch
up
with
him
afterwards.
A
So
we
can
sort
of
assumes
oh
there.
He
is
hiding
out
there
now,
okay,
because
I
just
noticed
that
you've
also
been
looking
or
working
on
this
mock-up
side.
So
we
need
to
kind
of
join
forces
on
how
we're
going
to
connect
those
dots
together
and
get
a
verse
draft
draft
in
place.
So
my
aim
this
week
is
to
basically
implement
this
piece,
so
I'd
like
to
summarize
the
documentation
platform
ideas
and
let
that
stew
for
a
while,
while
I
can
get
the
get
some
basic
implementations,
and
so
this
one
is
a
good
option.
A
C
The
the
doing
a
prototype
makes
a
lot
of
sense
to
me
because
we're
not
going
to
necessarily
know
all
of
the
edges
will
run
into
until
we
start
trying
to
to
use
one
of
these
things.
What
what
is
the
scope
of
that?
In
your
view,
like
how
long
of
a
spike
on
that?
Do
you
think
it
takes?
How
much
what
sort
of
content
do
we
want
to
try
pouring
into
things
like?
What
are
you
envisioning
in
terms
of
what
that
roadmap
of
prototyping
age.
A
Looks
like
I
think
I'll
keep
it
as
simple
as
possible,
so
no
more
than
a
week
for
both
of
those
projects
and
basically
just
take
the
same
subset
of
information
and
see
how
easy
it
is.
If
I
cannot
achieve
much
in
a
week's
worth
of
time,
then
actually
we
gonna
have
our
own
issues
anyway,
so
I
think
a
protic
like
the
the
HTTP
API
level
Docs,
because
they're
pretty
thorough
and
they're.
A
Also
it's
a
very
long
page
and
it'd
be
great
to
test
that
searching
against
so
yeah
I
think
the
primary
limitations
is
because
all
of
these
are
react
or
into
products
that
often
run
into
the
same
sort
of
problems
that
are
happening
in
the
ecosystem
right
now,
which
is
all
the
relative
path
issues
where
things
need
to
be
deployed
at
different
paths.
Depths,
and
if
you
put
on
an
idea
first,
then
you've
got
the
object
and
it
loads
via
IP
NS,
and
they
end
up
with
different
path
issues.
A
So
I,
don't
think
I
think
we've
kind
of
handled
that
and
gaps
for
using
a
plugin
in
the
past.
But
it
was
it's
not
ideal,
because
it's
doing
lots
of
rewrites
and
the
output,
so
it'd
be
nicer
to
have
a
better
solution
for
that,
but
it
could
be
the
docq
source
actually
handles
relative
path.
Better
and
I
will
well.
You
know
that
would
be
a
double
win
for
us
and
have
to
ask
you
a
question.
A
B
Terry,
you
said
that
you
have
to
leave
soon.
Do
you
mind
quickly
presenting
sure
I'd
be
happy
to.
D
D
D
Nursin
essentially
like
tutorials,
that's
it
right!
On
top
of
the
page,
we
worked
together
and
figured
out
how
to
get
this
bad
boy
linked
up
here.
We
also
I
think
in
the
same.
No,
it's
a
different
PR
that
we
worked
on
a
footer
update
for
this
is
Jaso
I,
think
FSI,
oh,
that's,
just
a
simple
tweak
to
get.
D
She
get
proto
school
highlighted
there
and
then
there's
a
first
one.
That's
in
progress
here
on
the
main
ipfs
tayo
website
and
the
biggest
thing
we
were
doing.
There
is
a
section
that
was
like
take
closer
look.
It
basically
just
says:
read
white
paper
as
an
option
that
white
paper
is
like
very
technical,
but
not
in
a
I'm
a
to
code
way
in
a
lake.
I
went
to
university
anyway
like
how
to
describe
it.
D
D
Diago
and
I
just
merged
an
update
that
will
be
hopefully,
unless
we've
messed
something
up
it
mostly
invisible
to
the
user,
but
it
refactor
is
a
bunch
of
stuff
under
the
hood
in
front
of
school.
That
makes
the
code
cleaner
and
easier
to
work
with,
and
that's
gonna
enable
us
to
do
our
next
step,
which
is
finishing
up
that
PR
on
enabling
multiple
choice
as
a
lesson
type.
There
you
go.
What
have
I
missed
that
we've
been
working
on.
E
E
Super
good,
I
think
we
have
a
lot
of
lots
of
issues
when
you
upload
files
and
then
you
came
back
to
license
and
there
were
no
cached
files
on
the
browser
and
everything
the
things
were
not
coherent
because
you
tried
to
submit
forth,
then
you
had
no
files,
but
the
lesson
was
best
lots
of
issues
like
that.
Now
everything
is
solved
and
it's
so
much
clearer
to
the
user.
What
he
can
do
so
yeah
I
think
there
were
some
questions.
Alan,
maybe.
B
Thanks
Eric,
would
you
like
to
go
next.