►
From YouTube: Magento PWA Backlog Grooming, 12 October 2018
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
Let's
do
it
so
let's
go
ahead
and
get
started
I
and
so
for
today.
We've
got
three
stories
to
cover
I
think
I
mentioned
that
in
in
both
slack
and
Twitter.
So
some
really
good
progress
to
date,
certainly
on
upward
so
again,
special
shout
out
to
at
the
martin
hands
and
another's
been
helping
james
on
things
really
really
identifying
answering
questions
helping
with
set
up
configuration.
A
A
So
the
link
itself,
of
course,
is
gonna,
be
more
informative,
but
I've
just
added
some
thumbnails
in
here
just
to
help
with
folks
on
this
one.
But
this
is
the
interactive
version.
This
is
all
for
those
who
want
to
play
around
with
it.
That
is
the
link
love
it
when
back
buttons
are
overridden
so
give
us
a
second.
B
A
And
so
with
order
details,
this
is
really
what
we're
trying
to
do
and
in
terms
of
the
story
again
from
a
shopper
standpoint
shopper,
one
of
you
details
from
an
order
placed
on
venue,
so
you
can
buy
again
share
or
review
item
in
the
future.
So
the
types
of
information
that
you
would
expect
to
see
here
all
products
themselves
will
be.
A
It's
just
under
the
chain
and
so
on,
yeah.
So
as
a
shopper,
when
you
details
from
an
order
placed
on
vineya,
so
they
can
buy
again
share
or
view
item
in
the
future,
and
so
with
this
one,
you
would
expect
things
like
an
order.
Id
number
product
details,
of
course
names,
details,
quantity
and
price.
Some
actions
on
this
one
explicitly
have
I
again
and
share
sure
made
may
be
a
stretch
goal.
A
We
can
certainly
think
about
that
in
the
future,
but
I,
but
I
think
we
discussed
very
early
on
that
reviews
are
probably
out
of
questions,
so
we
might
want
to
have
that
as
a
placeholder.
We
can
certainly
discuss
because
the
API,
as
as
Alex
would
say,
is
it's
not
quite
ready
for
that
one
in
terms
of
the
ratings
and
reviews
coverage
on
that
one.
So
for
this
one
I
think
we
would
just
look
at
making
these
parts
functional,
and
we
can
talk
about
what
all
that
looks
like
on
that.
A
One
of
course
assumptions
it's
good
to
be
dependent
on
purchase
history
when
that's
out
what
that's
complete,
although
there
are
some
cases
where
you
can
come
into
here
with
I
believe
a
order
number
and
a
zip
code
so
interested
in
possibilities
there
that
might
be
independent.
That
would
be
certainly
more
agile
and,
of
course
again,
we
just
mentioned
reviews
themselves
would
be
considered
in
the
future.
So
here
are
the
tasks
again.
I
am
I
kind
of
put
these
together
fairly
quickly,
but
I
want
to
get
your
feedback
on
this
one.
A
So
the
idea
here
would
be
to
create
an
order,
details
and
a
summary
and
a
very
authentic
unauthenticated
state.
That's
certainly
simple,
more
simple
and
again
based
on
how
things
typically
work
in
in
luma,
you
can
do
so
with
the
ID
number
and
a
believing
nd,
as
it
zip
code,
so
coming
to
this
with
those
two
parameters
would
be
kind
of
step.
One
step
two
then
gets
into
a
more
authenticated
experience
when
you
start
getting
into
things
that
would
be
linked
from,
of
course,
in
the
counter
of
Veronica
Costello's
and
sessions
so
kind
of
one.
A
At
a
time.
Looking
at
the
orders
and
the
groupings
once
those
are
complete,
then
looking
at
the
actions,
you
know
not
as
important
as
the
details
themselves,
once
that's
complete
and,
of
course,
the
shipments
and
the
payment
details
which
should
just
be
read,
read:
versions
of
what
we've
already
accomplished
here
in
check
out
today,
so
anyways.
That
is
that
again
in
terms
of
of
eight
basic
order,
details
page-
this
is
what
we
have.
A
B
A
C
A
Correct
and
in
theory,
we
should
be
able
to
actually
get
to
this
page
without
it
just
as
a
test.
If
we
make
independent
without
purchase
history,
ideally
you'd
have
it
link,
we
can
actually
come
in
via
ID
number
and
I
get
a
believe.
A
zip
code
I'd
have
to
verify
that
which
is
having
myself.
That
would
be
simpler
technically
than
an
authenticated,
but
it
wouldn't
get
authenticated
right
off
the
bathroom
right.
So
there.
C
A
For
the
purposes
of
a
demo,
I
think
we
can
show
we
can
enter
the
data
in
fairly
manually
even
by
a
URL
that
could
be
received
upon,
say,
form,
but
then
again
for
extra
credit.
If
it's
fairly
easy
to
do
this
and
as
authentic
Aidid
way,
since
you
know
purchase,
history
is
already
in
flight.
That's
great!
So
again,
this
is.
C
A
C
Though,
on
the
shipment
details
I
just
wanted
to
discuss
the
track
on
a
button
now
I've
seen
that
even
if
an
order
has
been
delivered
for
a
while
for
a
certain
period
of
time,
the
shipping
service
or
whatever
it
is.
It
still
allows
you
to
go
to
that
page
and
it
tells
you
that
the
orders
been
delivered
and
after
a
while
you
go,
you
can
I
mean
the
button
exists
in
order
history.
But
if
you
go
gives
you
a
404
or
it
says
you
know
the
deli
delivery.
C
Could
not
be
found
or
something
a
UPS
website,
or
you
idea
whatever
it
is
so
I
wanted
to
discuss.
If
we
should
follow
that
model,
where
we
always
show
track
order,
and
it
you
know,
based
on
what
that
end
point,
is
it
goes
to
that
or
do
we
remove
it
after
you
know,
let's
say
a
week
after
delivery
or
something
like
that,
I
mean
do
we
do
we
set
a
timer
on
it
and
say
you
know
this
is
not
trackable
technically
anymore.
So
do
you
think
about
not
disable
it
or
whatever?
A
The
briefs
I've
actually
maybe
even
a
deeper
question,
which
is
I'm.
You
know
for
the
first
pass
at
MVP.
Do
we
maybe
even
have
this
right
and
so
I
think
about
the
whole
process
for
MVP
I?
Think
in
that
ideal
world,
where
I
have
a
fully
functional
set
of
shipping,
and
no
at
this
point
this
would
be
a
manual
transaction.
Let
you
know
someone
from
zenia's
typing
in
you
know
that
UPS
number
that
the
HDL
number
behind
the
scenes
during
cooked
on
one
of
this,
and
so
theoretically
it
is
fairly
manual.
B
A
C
Particularly
helps
you've
been
lost,
your
order
and
the
link
is
still
active
after
it.
They
said
it
was
deliver,
but
it
wasn't.
But
to
you
this
happens
to
me
a
few
times
yeah,
so
you're
able
to
kind
of
say,
hey
it
helps
me,
you
delivered
it
here,
that's
not
very
live
and
so
on,
or
where
did
you
get
this
address
wrong?
A
A
Basically,
that's
just
an
additive
experience
once
that's
ready
or
that
much
like
reviews
for
those
I'm.
Actually,
okay,
with
relaxing
that
the
traffic
order
for
the
purposes
of
an
example
storefront
but
lift
again
and
see
where
that
goes.
We
might
want
to
come
back
as
maybe
a
short
no.12
three-pointer
after
this
one.
Once
once,
we
have
a
little
bit
more
information
about
that
did.
C
A
Would
be
insensitive
to
every
little
change
on
some
of
these
I
would
be
okay
with
just
making
it
a
notation
like
this,
and
so
as
far
as
our
acceptance
criteria,
that
wouldn't
accept
wouldn't
expect
this
and
then
who
knows,
maybe
somebody
will
surprise
this
in
the
process,
but
I
would
like
to
handle
it
separately,
based
on
some
of
those
conditions
again
just
trying
to
keep
this
an
ideal
world
we'd
be
looking
at
like
one
three
five
pointers.
This
one
may
be
a
little
bit
more
sizeable
potentially
I'll.
A
Leave
it
up
to
you
to
the
audience
here,
but
then
track
order.
I
think
is
just
kind
of
on
its
own,
something
that
could
be
added
afterwards,
but
not
I'd.
Rather
in
for
the
purposes
of
not
having
multiple
arcs
on
our
prototype,
we
would
come
back
around
and
just
make
notations
on
the
things
that
might
be
stretch
goals
for
that.
So,
okay,.
C
A
B
C
Of
course,
so
this
isn't
applied
to
a
fashion,
or
maybe
it
does
I
don't
know,
but
it
certainly
does
my
household
mm-hmm,
where
you
may
want
to
place
an
order
in
its
entirety
again
right
now,
all
we're
doing
is
we're
allowing
an
item-by-item
by
again.
What
do
we
need
to
consider
the
an
affordance
for
purchases
if
entire
order
again
for.
A
The
purposes
of
an
MVP,
storefront
I
think
no
I
personally,
think
that
that's,
even
even
as
a
an
item-by-item
situation
that
that's
a
fairly
low
use
case
it
certainly
in
terms
of
demonstrating
@p.
Do
you
a
and
so
I
think,
yeah
I,
think
I
think
it's
helpful
when
that's
not
it's
a
nice
to
have
but
I
think
for
the
purposes
of
this
one
I.
Don't
think
we
need
to
worry
too
much
about
that,
but
it's.
B
A
A
Excellent
sorry,
I
guess
I'm,
just
as
you
can
see
I'm
just
adding
some
notation,
so
we
don't
forget
so
all
right.
Well,
you
get
to
know
what
the
the
next
question
is
going
to
be,
which
is
estimate.
So
we
update
the
add
the
notes
on
this
one.
How
do
we
how
we
feel
about
this
and
what
what's
there
was
the
size?
What
do
we?
What
are
we
thinking
about
this?
One.
A
A
Down
the
gavel
there
we
go
done
five
perfect
sorted
then
thank
you,
everybody
that
was
easy,
alright,
so
let's
switch
gears.
This
one
should
be
equally
as
straight
forth,
I
hope.
And
so
again
you
guys
keep
me
honest
on
this.
One
I've
been
been
away
for
a
couple
days,
but
as
I'm
looking
at
what's
what's
being
built,
one
of
my
personal
desires
is
to
be
able
to
sign
out
and
potentially
link
to
other
areas
of
the
vineyard
storefront,
so
I
put
together
again
based
on
the
prototype.
A
That's
a
little
bit
further
ahead
from
samya
the
ability
to
do
to
access
an
account
venue
or
venue.
So
it's
part
of
the
larger
menuing
jewelry
per
se,
but
when
I
think
about
what
what
needs
to
happen
around
here,
clearly
there
going
to
be
some
stretch,
goals
here
around
rewards,
potentially
even
notifications
at
this
point-
maybe
even
lists.
So
we
can
have
those
petitions
as
placeholders,
but
now
we've
got
the
beginnings
of
purchase.
History
profile
is
gonna,
come
at
some
point.
A
That
might
be
something
that
grew
next
week,
but
certainly
a
sign
out
purely
just
for
from
a
testing
standpoint.
I
think
we
need
to
have
that
kinda
go
between
authenticated
and
unauthenticated
modes
for
for
things
and
so
I'm
hoping
this
is
a
pretty
straightforward
one,
but
it's
an
important
one
as
we
as
we
start
to
flesh
out
some
real
scenarios
and
again
testing
to
identify
some
of
those
future
scenarios.
A
So
this
one
again
is
just
extension
of
the
menuing
and
navigation
for
benya
to
build
upon
some
the
great
work
from
Pawlenty
Matt
Barber
II,
where
we
have
that
existing
set
up
there,
but
then
making
this
a
little
bit
more,
a
little
bit
more
robust
with
giving
us
a
sign
out
as
part
of
things.
So
that's
the
that's
the
overview
and
again
this
is
a
snapshot
of
the
of
the
prototype.
A
If
you
click
here,
you'll
see
the
interact
form
of
the
exact
same
thing
and
then
from
from
a
pure
story
standpoint
and
the
shopper
I
want
to
be
able
to
access
profile,
purchase,
wishlist
and
settings
from
venya,
including
Scion,
so
that
I
can
manage
my
accountant
future
again.
Basics
will
include
customer
name,
email
address,
which
we've
already
got
currently
in
in
our
example,
but
also
access
to
these
things.
Like
certainly
Purchase,
History
and,
of
course,
sign
out
as
well
so
assumptions
themselves,
we
assume
that
you
have
an
account
created.
That's
done!
That's
good!
A
We're
also
going
to
assume
things
like
rewards
and
points
again.
If
you
remember
we're
phasing
here,
Feifei
thing
is
I
would
love
yep,
of
course,
that
would
be
great
to
have
from
from
day
one,
but
those
won't
be
available
for
quite
some
time,
so
we
want
to
stuff
those
out,
but
that's.
This
is
where
they
will
exist
from
that,
so
those
would
just
be
either
we
can
decide
to
either
remove
them
entirely
or
just
kind
of
stuff
them
out
for
future
consideration.
C
F
C
Would
be
more,
you
know,
preferences,
and
you
know
that
kind
of
thing
in
their
name
and
we
can
have
some
basic
information
in
there,
but
so
I
feel
like
security
settings
because
we're
doing
the
create
account
and
the
sign-in
and
the
password
right.
It
could
be
more
important.
Potentially
then
I
agree.
A
Actually,
let's
say
you
know
so
I
know
one
of
the
things
we're
working
on
to
some
validation
of
this
with
some
some
feedback.
My
guess
is
that
if
we
were
to
ask
five
people
in
security
settings,
we
might
get
several
different
answers
terms
of
what
their
expectations
are
now
instructors
say
this
is
where
passwords
and
other
aspects
are
covered.
C
A
E
A
A
C
A
Then
I'll
do
the
same
thing:
I
think
I,
overlooked
notifications.
Of
course,
I
haven't
loved
the
seed,
notifications
and
I
think
that's
a
stretch
goal
to
get
it
done,
but
I'm
not
sure
if
we're.
If
we
will
have
that
for
something
that
we
could
reference
inside
of
this
fervor
for
the
first
first
iteration
we'll
get
there
pretty
good.
So
these
are
again.
These
are
the
assumptions
that's
dependent,
of
course,
on
it
kind
of
created
creation,
the
worst
part
about
notifications,
not
part
of
every
tea.
A
So
we've
now
basically
called
profile
channel
settings
and
then,
within
this
process,
being
able
to
identify
considerations
for
rewards,
certifications,
listen
settings
so
I,
don't
know
if
that's
as
important,
but
for
this
story
to
be
mindful
of
those
when
those
come
around
in
the
future
and
so
and
that
that's
more
of
just
a
a
hope
than
a
task
and
then
of
course,
looking
out
for
mister
Cal
cabanas,
always
testing
and
documentation,
that's
purple.
So
we
go
any
other.
Any
other
questions
comments
or
concerns
of
this
one.
No.
B
D
A
D
A
Second,
that
third,
three
excellent,
no
I,
think
so
yeah.
If
we
can
do
this
more,
you
know
quicker
than
the
three
I
think.
That's
fine,
that's
good
again!
What's
the
hood
is
open
on
this
one?
There
may
be
some
funniness
with
the
token
a
little
bit
of
layout,
maybe
here
with
the
the
branding
but
yeah
I,
think
I'm,
hoping
that's
the
intent
for
this
one
was
to
be
a
really
a
quick
quick
when
to
stitch
together.
Some
things,
that's
also
good,
excellent.
All
right
this
one
is
sorted.
Thank
you.
Everybody
great.
A
B
A
Ceremony,
let's
actually
make
sure
that
these
are
ready
for
starting
fighting
all
right
so
on
its
own
last
but
not
least,
and
so
we've
we've
we've
had
some
some
initial
work
here
on
search,
and
so
this
one
is
about-
and
this
will
probably
take
a
little
bit
more
time,
but
the
idea
here
is
that,
once
you
have
a
very
basic
search,
of
course,
you'll
know
that
that
filtering
and
sorting
would
come
next
beyond
that.
But
the
idea
of
creating
a
story
around
autocomplete
is
it
is
going
to
be
interesting
right.
A
You've
seen
this
in
some
of
the
prototypes.
This
is
a
fairly
traditional
search
experience.
So
within
this
one
the
idea
is
as
a
as
a
shopper.
You
want
to
be
able
to
preview
search
results
to
help
browse
the
products
on
the
inventive
storefront,
using
basic
keywords
like
hoodie
that
you
can
make
an
informed
purchase
the
idea.
A
Of
course
you
would
get
a
series
of
suggestions
and
then
be
able
to
go
from
that,
and
so
this
one
of
course,
is
going
to
be
dependent
on
any
search
and
so
I've
blocked
this
one
on
the
search
results
itself.
That
needs
to
be
done
first,
but
then
from
there
was
the
idea
that
you
would
click
on
a
magnifying
glass
like
so,
and
that
you'd
be
able
to
start
a
search
for
something
like
pants.
So
pants
would
then
give
you
a
series
of
suggestions
from
those
suggestions
and.
C
A
A
The
very
least
this
just
the
top
half
itself
would
be
great
I
mean
if
somebody
wants
to
get
us
into
suggestions,
that's
fine
as
well,
but
we
might
be
able
to
split
that
into
two
two
iterations
or
at
the
very
least
being
when
I
have
just
a
text,
only
view
to
begin
that
and
then,
which
would
again
basically
show
you
the
query
inside
of
a
category
but
then
being
able
to
allow
you
to
select
quickly
into
that
search,
result
page,
which
is
a
key
dependency.
I.
B
A
Sound
me,
a
real-time
makes
that
it's
based
on
some
let's
go
for
talking
about
here,
so
but
that's
what
we're
thinking
so
I'm.
Let
me
take
a
look
at
the
the
details
itself
on
the
story,
as
we
look
through
that
again
for
this
one
they're
making
assumptions
that
product
suggestions
will
be
covered
in
a
future
sprint.
So
I
didn't
note
that
Sando
ratings
or
reviews
results
themselves
would
continue
to
update
with
every
keystrokes.
So
there
are
key
keyboard
considerations.
A
The
shopper
would
be
directed
to
results
with
the
selected
phrase
in
category
and,
of
course,
those
tasks
themselves
would
be
the
discover,
basically
discovery
to
understand
the
real-time
products
from
API,
with
keyboard
implement
autocomplete,
with
the
guidelines
for
the
prototype,
which
we've
got
there
and
then
and
then
be
able
to
link
to
the
after
mentioned
search
results
which
would
be
ready
on
completion
of
this.
This
is
a
blocked
by
that,
but
this
is
the
idea
around
them.
Of
course,
we've
added
testing
and
documentation
to
this
one.
A
A
E
E
Well,
I'll
put
it
in
order
because
they
first
pose
the
problem.
It's
unclear
how
to
differentiate
between
missing
the
search
results
and
clearing
the
search
box,
and
we
talked
about
it
and
raised
the
issue
of
the
vocabulary,
objectors
that
you
can
have,
and
it
was
a
you
know.
It
was
observed
that
we've
we
talked
about
sort
of
discouraging
use
of
gestures
at
this
early
stage
and
that
kind
of
that
does
kind
of
limit
us
and
I
think.
Originally
it
was
Jimmy
who
is
gonna,
be
absent
for
a
little
while
we
talked
about
of
it.
E
We
want
to
make
sure
that
gestures
do
make
it
into
the
product,
and
so
at
some
point
we
will
have
use
of
that
vocabulary.
So
we
should
keep
that
in
mind
as
we
as
we
design
that
stuff
separately.
There's
definitely
some
inconsistencies
in
the
available
api's
that
make
this
potentially
inexpensive
query.
So
you
know
there
might
be
some
optimization
work
to
do
and
I
would
factor
that
into
the
estimate
got.
A
It
what's
your
James,
what's
your
what's
your
best
take
on
how
much
of
this
is
covered
via
graph
QL
versus
something
they
would
have
to
be
rest
at
this
point,
what
do
we
have
a
good
sense?
That's.
E
Actually,
that's
actually
a
good
question
for
the
bargaining
folks,
if
you're
doing
pure
product
search
I
know
that
graph
QL
can
do
some
amazing
stuff.
The
trouble
is
that,
right
now
the
schema
does
not
allow
you
to
supply
all
the
variables
that
you
want
to
have.
So
you
know,
I,
don't
know
what
you
guys
have
experienced
so
far
at
bargaining,
but
you
know
the
search
string
works,
okay,
right.
E
Right
no
worries
well
bottom
line
is
that
the
product
details
query
the
same
one
that
we
use
to
actually
fetch
product
detail.
We
do
that
by
narrowing
a
query
result
down
to
one
field.
So
all
you
do
is
just
not
do
that.
There's
a
search
string
option
then
there's
a
filter
option
for
more
advanced
stuff
that
right
now,
I,
don't
think
it's
ready
for
prime
time
so
MVP
would
just
be
using
the
search
string.
It's
pretty
straightforward,
but
I,
don't
know
how
performant
it's
going
to
be.
A
Yeah
this
one
will
just
have
to
factor
in
a
little
bit
of
ambiguity
on
it.
This
is
clearly
I'm
gonna
go
out
on
a
limb
and
say
that's,
probably
not
a
one
pointer.
Why
that
one,
but
yeah
search
is
always
getting
a
little
bit
tricky
and
also
just
yeah
just
to
be
doing
full
disclosure
in
terms
of
priorities.
I
think
my
intent
for
putting
and
putting
this
one
in
today's
grooming
was
to
start
bundling
a
more
complete
search
experience.
A
But,
to
be
honest,
you
know,
as
we
look
at
assignments
for
these
there's
other
areas,
that
we
would
definitely
want
before
hand.
So
it's
just
this
one's
more
about
logical
grouping
with
the
existing
search
work.
Of
course,
this
is
great
beyond
that,
but
you
know
that,
but
also
the
assumption
I'm
making
is.
This
could
be
bundle
in
with
the
existing
search
work
as
well.
But
again
the
push
comes
to
shove,
not
that
we're
pushing
or
shoving
it
anyways.
We
want
to
make
sure
that
we
can.
A
There
are
other
areas
to
tackle
first,
for
that
one
I
just
want
to
note
that
one
Zen
hub
doesn't
do
a
great
job
at
prioritization
per
se,
but
I
just
want
to
note
that
as
we're
booking
two
assignments
for
this
one,
so
sure
cool
all
right.
So
I
made
I
made
an
update
James
on
gestures
to
be
considered
in
the
future.
So
I
think
we'll
have
that
we'll
have
that
one
and
just
make
that
noted.
A
A
E
D
A
Right
all
right,
I
agree
relative
to
those
or
other
ones.
Here
we
generally
look
at
things
that
are
broken
down
in
the
threes
and
five.
This
is
gonna,
be
a
bigger
one,
and
that's
that's
fine.
So
this
is
recited
one.
So
let's
mark
designate
them
perfect
all
right,
and
then
this
one
has
an
offline
item.
I'll
follow
up
with
Sammy
as
you
as
the
update
yeah.
The
concept
in
this
I
think
this
one's
okay
but
I
think
we're
gonna,
replace
the
other
one
with
what
she
was
working
on
behind
the
scenes.
A
So
making
that
assumption
we'll
clean
that
up
and
then
this
one
also
will
be
ready
for
ready
for
start.
So
perfect,
that's
three
done
so
that's
art!
That's
our
intent
for
today!
So
I
had
those
this
refree
groom.
You
know:
we've
got
gosh.
We've
got
roughly
a
half
hour
ahead
of
us
here.
If
we
want
to
cover
anything
else,
there
are
always
things
to
cover
in
James,
not
sure.
E
E
Need
to
preach
I
mean
we
need
a
pre,
groom,
I
think
before
we
can
talk
about
this
productively,
but
I
think
we
definitely
want
yeah
I
think
we
definitely
want
to
continue
to
iterate
on
upward
documentation
and
I.
Also
think
that
we
should
record
some
work
that
James
Calculon
did
and
is
continuing
to
do
which
I
guess
we
can
back
like
we
can
backdate
into
a
story
that
was
being
done
is
is
is
jimothy
here.
F
E
We
should
have
a
story
for
all
the
cool
stuff
you're
doing
with
the
rest
api
scheme,
so
Eric
yeah
I
mean
the
rest.
Api
is
are
necessary
to
fill
in
the
gap,
but
the
story
for
gaining
access
to
full
REST
API
documentation
in
Magento
is
very
strange
for
the
uninitiated
and
it
you
require
an
instance,
and
it's
it's
not
great
and
right
now
it's
it's
a
cool.
A
I
think
it's
a
good
suggestion.
James
we
often
overlook
documentation
on
this
and,
if
you
guys
wanted
to
put
together
a
just
a
quick,
Strom
and
James,
just
at
least
to
cover
the
intention
of
that
one,
and
then
we
can
review
a
quickly
on
slack
and
get
an
estimate
around
that
yeah
I
agree
with
this
large
enough
large
enough.
That
needs
to
be
considered
but
I
think
also,
as
part
of
this
larger
form.
F
A
F
F
Guys
see
my
screen:
okay,
so
I
have
some
documentation
guidelines
when
you
know
when
Eric
says
testing
documentation,
and
then
this
is
a
good
set
of
guideline
matter
or
generating
documentation.
You
know
what,
where
I
expect
them
to
go
and
what
kind
documentation
I
expect,
whether
it's
a
UI
component
or
a
feature
or
implementation.
I
think
this
would
be
a
good
place
to
look
at
to
see
what
that
means.
When
there
it
says
destiny,
documentation.
A
A
D
A
Okay,
well,
very
good.
Well,
hey!
Thank
you!
So
much
everybody
great
to
be
back
I.
Thank
you
again
for
joining
us
and
for
knocking
out
three
story,
even
in
rapid-fire,
so
we'll
law
will
have
a
bigger
bigger
list
for
next
week,
based
on
the
progress
I
made
this
time
around
and
again,
as
always,
we
she
everybody
support,
have
a
great
rest
of
your
day
and
in
evening
and
we'll
talk
soon.
Thank
you.
I'll
see
you
soon
all
right
take
care.
Alright,.