►
From YouTube: IPFS Docs & Developer UX Weekly Sync 2019-08-05
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.dgr8wcldbq68
A
B
A
A
Alright,
let
me
know
when
you're
ready
to
go,
you
are
recording
Portia,
okay,
cool
cool.
You
hit
the
button.
Awesome
hello,
everybody
on
the
Internet,
welcome
to
the
documentation
in
developer.
New
UX
task
force
weekly
meeting
today
is
Monday
the
5th
of
August
2019
I'm,
your
wasp
infested
host
Jessica,
and
we
have
lots
of
people
on
the
call.
So
welcome
I'll
take
some
notes,
but
it
doesn't
sound
like
we've
got
any
additional
agenda
items
other
than
the
recurring.
A
A
C
C
C
C
So
this
is
just
places
where
we
can
find
ipfs.
So
we
actually
know
if
we
actually
own
the
page-
and
we
just
have
like
a
record
of
where
we
can
find
ipfs
around
and
about
one
source
of
truth.
And
so
here
are
some
of
my
initial
findings.
I
started
this
today
and
I
didn't
finish
it
so
I'll
be
adding
more
on
this
week.
C
The
basic
concepts
sections
of
ipfs
is
hard
to
find,
and
this
is
a
problem
because
when
a
person
is
trying
to
figure
out
if
they
want
to
contribute
or
if
they
want
to
take
it
into
a
project,
basic
concepts
is
like
a
great
place
for
them
to
figure
out.
If
this
is
a
project,
that
they'll
be
interested
in
I
have
an
example
of
Docs
that
has
a
good
basic
concepts
section,
which
is
that
protocol.
C
There
are
other
documentation
out
there
that
does
a
really
good
job
of
explaining
the
basics
that
I,
like
add
onto
this
list
number
two.
We
have
a
lot
of
out
of
date,
content
and
but
most
of
this
content
has
github
issues
so
that
people
can
see
if
the
content
actually
needs
to
be
updated.
There
are
some
duplicates
in
the
ipfs
documentation
I'm
starting
on
that
list.
C
Now
one
duplicate
is
a
notes
and
a
notes
is
a
place
where
people
are
able
to
make
suggestions
on
future
features
for
ipfs
I'm,
not
sure
if
it
should
end
up
in
a
documentation
twice
community
infos
at
the
bottom
of
Docs.
The
ipfs
I
owe
my
community
info
is
important
and
I
wonder
if
we
can
create
a
page
that
has
like
all
the
community
are
ways
that
the
community
can
help
out
with
the
documentation,
help
out
with
different
features
and
figure
out
how
they
can
and
I
are
channels.
C
Let's
see
five.
This
is
a
conversation
that
we're
going
to
have
soon
assist
ways
for
contributors
and
developers
to
systematically
update
Docs.
While
going
through
this
content
audit,
you
could
tell
that
in
certain
cases
when
there's
a
new
feature,
there
was
an
ad
hoc
way
of
adding
Docs
but
I.
Think
one
of
the
takeaways
of
the
content
audit
is
for
us
to
come
up
with
a
clearer
way
for
contributors
to
find
to
add
to
the
documentation
and
also
for
us
to
have
notes
of
when
the
documentation
was
updated.
C
C
Should
have
thanked
you,
the
green
green
are
I
meant
to
talk
about
this
green
are
references
to
github
repos.
There
are
several
places
in
Doc's
ipfs
data
I/o
like
instead
of
having
regular
documentation
page,
we
have
a
link
to
the
actual
github
page
and
in
the
future,
would
be
nice
for
some
of
these
projects
to
have
their
own
pages
and
Doc's
I.
Think
I,
pfft
IO
red
is
an
external
link.
A
Makes
sense,
I
mean
I.
Think
one
of
the
things
that
you've
identified
here
is
that
if
you
look
at
the
original
menu
structure
of
the
docs
site,
do
I
sort
of
see
it
as
something
that
we
were
linking
out
to
as
many
sources
of
information
as
we
had
available
at
that
point
in
time,
just
as
an
effort
to
get
all
of
that
in
one
place,
I
think
it's
a
sort
of
elaborate
on
what
Porsche
said
you
know.
One
thing:
is
we
start
to
do
a
more
rework?
A
The
docks
content
is
to
see
what
sort
of
additional
scaffolding
we
might
need
to
be
placing
around
some
of
this.
Like
you
know,
it's
absolutely
essential
to
point
somebody
toward
a
github
repo
for
things
that
they
want
to
learn
more
about
or
implement
or
install,
but
we're
in
the
additional
explanatory
content
might
need
to
live
in
regards
to
even
regards
to
that.
A
C
Extra
dock,
great
candidates
for
documenting
documentation,
pages
I,
would
say
would
be
like
ipfs
desktop
an
IPSS
companion.
The
repo
is
pretty
comprehensive,
but
for
those
who
have
like
its
own
home
and
a
documentation,
I
think
would
be
helpful.
Those
are
very
important
projects
and
one
of
the
things
that
we're
going
to
that
we
want
to
do
for
the
content.
Audit
is
to
find
a
very
clear
pathway
for
people
to
create
their
own
documentation.
Yeah.
A
And
and
one
nice
thing
that
you
have
been
doing
in
the
meantime
is
stuff-
that's
just
like
very
that
is
hot
fixable,
either
because
it's
simple
to
fix
or
because
it's
like
a
big
problem
like
a
broken
link
or
something
if
that's
where
you've
been
port,
has
been
adding.
Those
is
github
issues
and
we've
been
hammering
away
on
fixing
those
as
we
go,
which
is
nice
to
be
able
to
fight
at
least
some
of
the
little
tiny
clients
in
the
meantime.
So
we're.
C
Already
starting
to
integrate
some
stuff,
yeah
Molly
and
we've
already
had
new
contributors
used
some
of
the
issues
from
the
content
audit
as
a
way
to
dive
in
into
the
ipfs
documentation
as
a
way
for
them
to
like
start
contributing.
So
well,
if
you
they're
small,
but
they're
great
first
issues
and
are
a
great
gateway
for
people
to
get
more
involved
in
all
contributing
and
we've
been
really
diligent.
A
B
C
B
Okay,
I
think
I,
don't
quite
understand
the
format
you're
using
for
understanding
what's
nested
under
what
I'm
wondering
if
there's
like
a
standard,
a
canonical
like
this
is
how
you
read
it
in
order
to
be
able
to
read
this
and
understand,
actually
how
our
dogs
website
is
organized
you're
like
if
you
look
at
the
tree
on
the
left
of
the
documentation
website
that
doesn't
seem
to
translate
easily
into
the
way
that
you've
translated
this
content
into
our
content
on
it.
Okay,.
A
Can
I
suggest,
maybe
that
we
table
this
discussion
for
we're
gonna
we're
gonna
lose
any
material.
You
think
yeah
we're
gonna
we're
gonna
go
through
the
horse's
findings
in
more
detail
tomorrow
and
see
what
we
can
you
see
what
we
can
settle
on
with
some
some
core
findings
and
go
from
there.
I
just
am
trying
to
be
cognizant
of
time
on
this
meeting.
A
D
Quick
note
before
you
wrap
it
up,
I
was
just
gonna
mention
on
the
community.
Section
part
I
think
we
should
pull
it
out.
The
docs
completely
and
I
had
a
chat
with
Zach
recently
about
creating
a
call
to
action
on
the
end
of
all
of
our
videos
from
camp
and
essentially
using
that
as
a
main
card
to
pull
people
towards
like
a
one-page,
subscribing
involved
with
the
community
and
page
itself
is
not
spectator
yet,
but
I
I.
D
A
A
A
Alright,
we
don't
have
anybody's
updates
on
the
docs
platform
features
inventory
I
know
that
we've
all
been
scrambling
in
our
respective
smaller
parts.
I,
don't
think,
there's
a
whole
lot
to
report
here,
just
because
we've
all
been
working
very
hard
on
other
things.
I
don't
feel
like
that's
blocking
us
in
any
way,
but
does
anybody
feel
otherwise?
At
this
point,
you.
A
Yeah-
and
we
are
definitely
accumulating
some
of
the
some
of
the
features
just
sort
of
on
our
own
I
know:
Eric's
got
those
documents
that
he's
been.
You
you've
got
your
working
afterwards
for
accumulating
those
wish
lists,
as
I
went
through
and
groom
the
entire
Zen
hub
board.
We
also
ran
into
a
couple
of
issues
that
people
had
posted
in
the
past
that
identify
some
features
that
that
community
members
wanted
in
a
wish
list
and
Kris
and
Eric
you're
both
aware
of
those
so.
D
We've
been
trying
to
gather
a
sort
of
prioritize
feature
set
that
will
essentially
how
these
are
the
must-haves
that
we
will
kind
of
hit.
That
will
be
at
least
like
for
like
experience
and
then
all
the
additionals,
because
it's
obviously
just
never
going
to
be
a
1,
a
1
phase
release
in
terms
of
upgrades.
So
if
we
can
road
map
it
all
out
over
the
next
few
weeks
and
that'd,
be
the
best
course
of
action.
D
A
D
I
mean
most
week
most
effort
last
week
was
focused
on
the
homepage
quiz
side
of
things.
So
there's
not
a
whole
lot
to
update
really
from
the
call
on
last
Monday,
which
I
think
he
made
missus
just
that,
essentially,
we
I've
just
been
gathering
together
any
scraps
of
notes.
They
found
from
existing
issues
that
are
out
there
other
things
that
people
have
contributed
and
just
putting
them
into
the
overall
sort
platform
landscape
audit
that
we're
putting
together.
D
So
it's
more
just
a
kind
of
gather
everything
together
and
then
assess
it
as
one
big
chunk
and
a
bit
later
on
so
Eric
and
I
have
been
focusing
on
getting
the
quiz
and
home
page
upgrades,
which
is
slightly
grown
since
the
original
brief.
Just
because
you
know
pulling
the
wallpaper
and
it
goes
around
into
every
room,
so
we've
trying
to
try
and
set
out
intersections
whether
or
not
we
upgrade
certain
parts
of
it.
A
D
F
So,
in
order
to
you
know
with,
and
if
anything
you
put
on
a
sub
page
you're
gonna
lose
some
folks
right
because
like
to
get
there,
and
so
we
want
to
capture
as
many
as
possible
many
eyeballs
and
clicks
as
possible
in
this
quiz,
and
so
we
are
going
to
put
it
right
on
the
homepage
and
that's
not
reflected
here,
but
it
is
and
I've
updated
it
in
the
in
the
sketch.
But
just
one
simple
call
to
action
then,
as
perhaps
get
started,
and
that
would
be
an
anchor
link.
So
it's
in
this
prototype.
F
It
takes
you
to
another
page,
but
it
would
be
an
anchor
link
to
take
you
right
down
to
the
to
the
bottom
of
the
page
where
that
panel
will
be,
and
these
accordions
I'm
considering
doing
the
accordions
instead
of
wide
during
them
to
into
it's.
It
I
think
it
that
users
will
rock
them
better.
That
way
make
expanding
them
becomes
a
little
bit
more
interesting,
because
if
you're,
if
you've
got
two
into
and
you're
expanding
this
one,
that
does,
we
could
do.
Maybe
a
fancy
push
down
or
something
we
have
someone
on
the
call
who's.
D
D
Okay,
so
just
mainly
for
the
benefit
of
Molly
here,
because
I
think-
and
everyone
else
would
be
watching
some
of
the
thinking
behind
the
reasons
why
we
settle
on
primarily
for
segments
it's,
because
we
want
to
categorize
the
audience
into
different
chunks,
that
we
can
measure
primarily
being
that
the
brand
new
people
to
ipfs
or
generally
2d
web
concepts.
You
come
through
now.
What
is
this?
What
is
the
whole
idea?
D
So
we're
thinking
like
if
you,
if
you're
an
independent
or
you
may
be
a
small,
app
developer
or
something
then
maybe
you
must
most
likely
be
looking
for
this
type
of
option
and
manage
large
amounts
of
data
trying
to
funnel
people
towards
more
enterprise
or
maybe
commercial
applications
of
things
and
then
implement
my
code,
which
I
think
that
might
change
the
wording
on
that
yet,
but
basically
build
an
IP.
Fs
application
will
be
more
the
developer
or
dev
experience.
D
There's
some
ideas
around
like
switching
these
switching
the
order
of
this
as
well
I've
written
up
some
more
detailed
notes
here
about
the
seconds
themselves.
But
it's
more
that
we
want
to
I'd
like
to
see
the
funnel
of
people
going
through
from
A
to
B
and
then
start
to
work
out
the
priorities
of
our
audience
by
self-selecting.
So
I
will
intend
to
have
metrics
on
all
the
pieces
and
all
the
clicks
out.
D
So
we
can
actually
see
overall,
as
we
can
get
people
in
from
the
beginning,
through
all
the
way,
to
the
end
that
what
type
of
what
other
content
they're
actually
interested
in
and
where
they
actually
jump
off
to
and
Jessica's
added
some
helpful
notes
of
the
section
and
content
that
we're
actually
gonna
add
into
this.
And
so
we've
got
some
links
out
to
things
and
typically,
obviously,
they're
the
more
commercial
side
of
things
and
more
enterprise
will
be
head
towards
the
cluster
angle,
and
the
implementation
bit
will
be
more
def,
UX
and
stuff.
D
So
implementation
on
how
to
use
install
ipfs
through
my
through
the
command
line,
and
then
that
leads
onto
the
redefined,
which
is
like
a
page
page
B
of
the
whole
flow,
which
is
the
install
idea
first
section
and
because
of
the
development
we've
done
on
ipfs
desktop.
Now
we
can
actually
prioritize
that
as
being
the
main
source
of
inspiration.
So
if
you
saw
like
the
first
desktop
for
most
cases
that
will
install
after
Auto
upgraded
version
of
ipfs
on
your
command
line
that
you
can
use
across
to
develop
your
application
and
I
causes.
I.
D
Think
that
covers
most
like
90%
of
the
use
cases
here
and
then
we're
going
to
break
down
all
the
other
implementations.
So,
instead
of
having
a
separate
section
at
the
top,
that's
kind
of
confusing
it's
kind
of
you
have
to
choose
your
own
way
and
start
to
reorder
this
based
on
your
priorities
of
which
way
which
path
you
came
in
from,
but
for
now
yeah,
it's.
D
D
Once
we
have
some
numbers,
then
we
can
further
tweak
and
refine
this
page,
but
really
we
have
to
start
with
a
best
guess
for
where
we
want
to
guide
people
and
be
helpful
and
then
move
on
to
what
what
will
be
next
and
I
think
we've
kind
of
settled
on
two
primary
actions
at
on
the
homepage,
which
will
be
their
getting
started
and
learn.
More
learn.
More
will
be
dosed,
basically
explaining
or
digging
into
the
current
explanation
content.
D
That's
on
the
homepage
and
will
slightly
reorder
this
to
make
make
the
narrative
sort
of
making
a
bit
more
sense
and
I've
started
working
on
this.
Now
we
haven't
finalized
InDesign,
yet
but
it'll
be
kind
of
a
tandem
efforts,
while
we
while
we
go
through
it-
and
we
can
refine
that
this
week,
there's
some
slight
issues
that
I've
uncovered
with
the
way
the
analytics
current
set
up,
because
we've
got
separate
single
profile
for
across
the
website
and
the
blog
and
other
part.
So
the
analytics
are
slightly
skewed.
D
B
D
D
You
can
also
set
up
profiles
that
they
can
include
a
subdomain
if
we
decide
to
expand
that
out
across
there
other
like
cname
sites
like
blog
or
Docs
in
the
future,
but
realistically
and
from
fighting
the
power,
it's
typically
best
to
keep
each
domain
as
a
separate
profile
so
that
you
can
then
and
get
the
power
of
actually
their
report,
some
tools
and
the
insights
they
work
better.
That
way.
A
So,
just
being
mindful
of
time,
I'm
I'm
gonna
go
ahead
and
skip
it
through
the
percent
in
the
hiring
stuff.
The
hang
stuff
is
progressing
very
well.
It's
not
something
talked
about
in
the
call
anyway,
because
it's
HR,
but
hit
me
up.
If
you
want
more
details,
things
are
things
are
progressing
pretty
well,
we
made
some
hot
fixes.
Those
are
also
progressing,
but
I
want
to
talk
about
the
protis
cool
stuff.
E
E
We
have
still
our
open
one
about
doing
the
three
buttons
on
the
main
type
EFS
website,
I
confess
that
IO,
which
we
just
need
to
kind
of
incorporate
the
feedback
that
we've
gotten
from
that
to
wrap
that
one
up.
But
the
biggest
accomplishment
this
week
is
enabling
multiple
choice:
lesson
tights
on
proto
school
I
put
a
link
there
to
a
live
demo.
A
A
That
was
really
great
just
a
couple
of
things.
The
personae
are,
basically,
the
persona
are
coming
out
of
the
core,
so
the
the
single
question
quiz.
What
do
you
want
to
do
with
ipfs
turned
into
like
six
key
categories
and
then,
like
sort
of
neatly
happened
to
be
pretty
much
exactly
our
goals,
though
so
I'm
starting
on
those
have
some
some
sort
of
measure
in
comparison.
A
A
We
were
able
to
knock
out
a
whole
bunch
of
stuff
things
that
were,
you
know,
I
think
five
things
that
were
specifically
identified
as
topics
as
small
things,
some
of
whom,
which
can
community
members
contributed
to,
but
then
also
just
with
being
able
to
groom
the
repo
and
get
things
that
are
categorized.
Somebody
actually
came
over
the
weekend
and
and
wrote
the
beginnings
of
a
DHT
explainer
has
a
bunch
of
technical
questions
that
I'm
gonna
have
to
get
solved
by
someone.
A
So
if
any
of
you
have
an
idea
as
to
who
I
should
point
this
person
to
to
get
their
technical
questions
solved
for
the
DHT
explainer,
that
would
be
magnificent.
But
but
what
it
does
mean
is
that
you
know
all
of
the
grooming
that
we've
been
doing
has
been
seeing
has
definitely
the
same
effects
with
contributors.
So
awesome
shout.
C
D
B
Had
to
feel
quick
questions
which
are
more
like
kind
of
timing
related,
which
is
one
the
quiz
looks
awesome
when,
when
are
we
kind
of
aiming
to
ship
that
to
the
front
page
and
start
getting
feedback
on
it?
And
two
we
mentioned
in
the
last
call
that,
like
kind
of
looking
to
prototype
on
donkey
soros
and
the
other
one
whose
name
I'm
forgetting
something
else
with
a
doc
word
in
it
and
I
was
curious.
When,
when
we're
kind
of
aiming
to
do
like
a
very,
very
first
round
prototype
on.
D
Asap,
for
both
the
be
the
make
the
quizzes
mainly
this
week
as
effort
I,
think
I
want
to
wrap
up
as
much
as
we
can.
There's
gonna
be
some
collaboration
with
in
terms
of
like
what
the
sine
of
sine
of
a
date
will
be
because
it's
I'm
getting
prototype
ready
and
then
some
design
that's
to
be
done
so,
but
I
reckon
that
can
be
done
this
week
in
terms
of
prototypes,
I
would
say
maybe
the
week
following
or
the
week
after
that,
so
I
would
aim
for
mid
to
end
August.