►
From YouTube: Magento PWA Backlog Grooming, 7 December 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
All
right
well
very
good.
Well,
let's
go
ahead
and
get
started
everybody
so
so
welcome
back
and
we've
had
a
few
misses
on
the
on
the
grooming
recently,
and
so
it's
good
to
see
everybody
to
be
back
especially
around
the
holidays.
As
we
as
we
resume.
You
know
all
the
great
progress
after
2.3,
and
so
thanks
again
for
everybody's
help.
A
You
know:
we've
got
some
some
good
work
coming
up
relative
to
certainly
the
the
venue
storefront
work,
but
also
a
lot
of
those
enablers
that
are
gonna,
help
us
open
the
doors
for
kind
of
bigger
and
bigger
bruins
for
both
the
storefront
and
the
also
the
studio
itself.
So
a
couple
couple
housekeeping
items
I
want
to
cover
before
we
get
started.
So,
as
a
team,
you
know,
we've
got
we're
growing
almost
every
day,
we've
got,
we've
got
folks
like
Tommy,
Andy
and
others
are
joining
us
seemingly
with
every
week.
A
So
we've
done
and
consolidated
that
within
progress-
and
we
also
had
some
I-
would
say
some
ambiguity
and
some
questions
on
the
difference
between
review
and
QA
and
merging
in
progress,
and
so
we've
got
and
consolidated
those
as
well.
If
we
feel
like
we
need
any
level
of
differentiation
we'll
bring
it
back,
but
but
we
really
are
trying
to
stick
more
to
a
Kanban
style
of
things
than
to
know
the
graph
QL
teams
and
others
are
doing
quite
successfully
and
getting
away.
A
A
couple
of
these
here
you
know
get
this.
This
payments,
one
that
Andy's
taking
a
look
at
for
release.
Five,
there
will
be
really
sensitive
release,
so
there
won't
be
released
five
released
for,
if
you
remember
correctly,
those
used
to
align
towards
quarters
right
so
quarter
for
release
four,
but
it
just
wasn't
valuable,
and
so,
as
a
team.
A
We
thought
about
that
and
we
said
that
that
you
know
that
just
wasn't
valuable
for
us
moving
forward,
so
we
so
we're
gonna
trim
those
up
a
little
bit
and
then
also
move
away
from
the
the
sprit
tags
in
favor,
for
maybe
logical
tags
as
well.
A
But
you
know
in
terms
of
what
that
means
week
to
week.
You
know
actually
means
very
little
change
right,
so
we're
gonna
continue
having
our
grooming
sessions.
We
may
have
been
doing
them
more
and
on
an
as-needed
basis.
We
really
need
to
get
deeper
on
some
of
the
dependencies,
especially
for
key
areas
like
like
orders.
My
accounts,
other
areas
that
require
some.
A
You
know
some
sleight
of
hand
and
some
trickery
on
the
API
side
to
get
those
up
and
going
for
that,
and
so
we're
going
to
get
a
little
bit
deep
on
that
and
also
understand
some
of
the
de
Graaff
qaul
work.
So
look
for
that,
but
then
we're
also
gonna
go
keep
our
keep
our
regular
cadence
of
demos.
They
won't.
Let
me
sprint
demos,
you
know
bi-weekly
seems
to
feel
right
if
this,
if
the
velocity
picks
up
quite
a
bit,
we
made
the
move
to
weekly,
but
not
not
anytime.
Soon.
A
We're
just
gonna
match
the
cadence
of
that,
but
we
also
to
be
more
consistent
with
with
other
community
engineering
projects
that
have
a
regular
cadence
like
that.
So
so
anyways,
you
know
again
might
not
be
a
big
change
for
some,
but
for
most
it's
just
a
matter
of
semantics.
So
fewer
columns,
less
labels,
but
they're
really
about
continuous
delivery
and
continuous
releases
that
you're
starting
to
see
already.
You
know
from
from
from
James
Jimmy
Andy
a
team
from
from
from
the
the
recent
work
at
around
2.3.
A
As
everybody
with
us
I
know,
we
had
some-
maybe
issues
just
doing
a
quick
check
on
that
all
right,
very
good.
So,
let's
take
a
look
at
take
a
look
at
kind
of
the
next
path
forward
here,
so
so
now
that
we've
got
the
administrative
pieces
kind
of
taking
in
consideration
what
I
want
to
share
you
with
there's
a
really
quick
graphic
on
the
work
remaining
and
I.
Think
that
helps
us
frame
the
priorities
and
help
helps
us
frame
to
work
left
to
do
now.
A
We'll
come
back
to
the
actual
items
themselves,
but
if
we
can
spend
like
I,
don't
say
60
seconds
kind
of
talking
about
the
work.
That's
that's
remaining
here
for
a
lot
of
folks.
You
know
I,
think
they're,
trying
to
understand
the
work
relative
to
UX
and
development,
and
so
one
of
the
things
that
were
really
I
really
excited
about
is
the
is
the
progress
that
we've
defined
in
prototypes
well
before
a
lot
of
the
development
work
has
been
done
and
really.
A
But
again
you
know
from
a
you
know
from
a
high
level
perspective,
especially
us
coming
out
of
out
of
two
three.
Oh
I
think
it's
really
important
for
us
to
understand
what
we've
done
and
what's
left
from
from
a
kind
of
a
UX
and
development
standpoint.
We
made
a
lot
of
good
progress,
but
people
often
ask
this
question:
hey
that's
great!
What's
left,
you
know,
because
we
have
a
really
solid
MVP
that
will
just
continue
to
iterate,
but
also
optimize
as
well
and
I.
A
Think
that's
going
to
be
the
spirit
of
spirit
of
today's
grooming,
we're
going
to
cover
some
some
some
interesting
topics,
around
accessibility,
documentation
and
kind
of
building
around
the
core
that
we've
got
any
any
questions
about
that.
Does
this
the
does?
This
feel
right?
Any
any
surprises,
any
any
any
questions
or
call
out,
sir.
C
A
A
But
there
are
a
lot
of
areas
where
you
look
at
kind
of
the
one-to-one
relationship
between
lumo
and
then
yeah,
where
the
contact
us
page
and
the
404
page
is
and
those
types
of
things
that
should
be
pretty
straightforward
but
but
but
we've
got
to
get
to
and
they
they
weren't
as
important
as
the
core
functionality,
and
so
those
are
definitely
less
complete
from
UX
development
standpoint.
But
what
you're
not
seeing
here
is
the
weighting.
So
the
big
you
know,
the
big
ticket
item
here
is
gonna,
be
around
my
account.
A
My
account
is
kind
of
this
loaded
item
that
has
the
wishlist
has
a
lot
of
those
authenticated
experiences
that
we
want
to
get
into
and
kind
of
build
around,
which
essentially
has
been
an
MVP
around
open
source
or
MVP
around
unauthenticated.
That
we've
had
a
little
bit
of
a
count
work
today,
so
anyways,
there's
I
thought
it
really,
especially
since
we
have
a
lot
of
a
lot
of
regulars
on
the
call
thought
it'd
be
really
worthwhile
kind
of
talking
through
that,
but
yeah
we,
you
know
these
are
really
directionally
correct.
A
A
So
I
think
I'd
like
to
start
off
with
if
everybody's
okay,
with
some
of
the
accessibility,
improvements
and
so
I,
think
one
of
the
things
that
we
were
most
proud
about
last
week
and
we're
early
again
a
culmination
of
some
of
the
great
work
from
the
barre,
green
folks
that
that
many
others,
like
Jimmy,
James
and
others
had
had
pulled
together
recently
in
time
for
the
release
was.
Was
you
know
how
we
get
to
those
lighthouse
scores?
A
And
so,
if
you
think
about
the
spirit
in
which
we
covered
of
having
a
really
good
core
around
the
MVP
and
starting
to
optimize
and
iterate,
one
of
the
one
of
the
key
needs
that
we
really
wanted
to
address
was
was
this.
It
was
this
idea
around
accessibility,
and
so
we
all
know
that
you
know
by
by
checking
the
less
necessarily
the
accessibility
column
for
these
that
you
know
our
work
won't
be
done,
but
I
think
from
from
a
kind
of
a
general
expectations.
Dan
point
and
Google's
done
a
nice
job
of
this.
A
You
know:
we've
got
a
couple
couple:
low-hanging
fruit
items
that
we
can
take
a
look
at
we've,
actually
gotten
some
good
contribution
from
Gil
over
at
something
digital,
proposing
a
couple
of
improvements
that
I
think
are
worth
worth:
grooming
here
as
a
team,
so
so
in
terms
of
kind
of
the
next
next
item
there.
So
you
know,
one
of
the
items
here
is
is
really
just
to
take
a
look
at
these
improvements,
specifically
around
accessibility
and
now
no,
you
know
from
a
product
standpoint.
A
I
identified
this
as
kind
of
a
general
need,
but
what
I
want
to
do
is
get
some
get
some
insights
from
the
team
here,
because
I
believe
you
know
some
of
the
things
that
we
will
have
to
consider.
Are
you
know
what
aspects
of
this
are
venya
specific?
Which
of
course,
is
the
the
stylized
form
of
a
lot
of
the
work
we've
done,
but
also
what
are
some
of
the
key
components
that
would
go
back
into
Peregrine's,
which
are
UI
components,
and
so
what
is
the
relationship
between
that?
A
So
from
from
a
story
at
stamp
standpoint?
Again
as
a
shopper,
you
want
to
be
able
to
access
to
experience
a
fully
accessible
venue
or
friends
based
on
the
WCAG
guidelines.
Just
did
a
quick
link
to
that
and
the
expected
result.
You
know
from
a
product
standpoint
is
we
want
to
you
know.
You
know
we
want
to
kind
of
shore
things
up
from
from
a
naming
standpoint
from
a
contract
standpoint,
which
is
actually
going
to
be
a
small
thing
for
for
Zambia
and
then
also
the
page
specification.
A
So,
in
theory
these
might
be
straightforward,
but
as
a
product
you
know
from
a
product
standpoint,
these
might
be
a
little
bit
more
involved,
and
so
so
the
idea
is
to
kind
of
take
a
look
at
this.
I
have
looked
at
home,
page
category
and
product
details.
This
is
the
same
trends
for
for
how
we
do
things,
and
so
in
theory
these
could
you
know
the
the
changes
here
could
affect
and
help
those
pretty
quickly,
but
they
might
not.
A
Based
on
the
you
know,
basic
I
know
the
wisdom
of
the
crowd
here,
and
so
the
idea
is
to
it's
essentially
a
a
multi-day
ticket,
a
multi-day
story
that
would
review
analyze
and
address
some
of
these,
in
short
order
to
add
to
to
then
shore
up,
essentially
these.
These
changes
here
on
the
accessibility
column
here
that
that
again,
in
this
case,
that
lighthouse
is
provided
today.
So
most
of
these
are
around
some
of
the
elements
themselves.
The
color
contrast
appears
to
get
it
to
be
specific.
A
Around
balloon
of
all
things
are
our
footer
tag
for
Magento
all
rights
reserved
and
then
some
some
documents
elements
here
around
language
attributes
as
it
relates
to
the
HTML.
So
it
could
be
straightforward,
but
but
you
know
I'd
like
for
you
guys
to
keep
me
honest
on
this.
If
this
is
more
than
just
a
few
days
work
in
the
spirit
of
kind
of
getting
beyond
estimates,
we
can
break
this
up
into
two
separate
pages
or
separate
categories
here
as
well.
I'm
happy
to
do
that.
A
It
looks
like
in
this
particular
report.
It
looks
like
within
venĂa
the
the
very
bottom,
the
the
very
the
footer
here
appears
to
to
be
lower
contrast
than
what
the
guidelines
would
specify.
So
from
your
standpoint,
my
guess
is
that
the
we
might
want
to
take
a
quick
look
at
the
RGB
values
of
I've
got
this
here
at
the
very
bottom.
I
think
it's
this
right
here,
so
you've
basically
got
a
dark
gray
and
a
light
gray.
My
guess
that.
E
B
A
Is
that
the
shirt
you're
wearing
today,
alright,
so
I'm,
so
again,
I
I
spec
this
out
with
it
what
the
means
to
kind
of
shore
this
up,
based
on
this
basic
expectation
from
my
house,
but
I
really
want
to
get
some
some
more
technical
minds
on
this.
Do
we
have
a
sense
of
scoping
on
this?
Are
these
are
these
big-ticket
items?
Do
these
go
against
some
of
the
fundamental
ways
that
we're
doing
components,
or
can
this
be?
A
B
Would
tend
to
think
that
I'm
it
goes
both
ways,
and
so
it's
a
wash
like
I,
don't
know
who
here
in
community
has
a
lot
of
experience
using
the
tools
that
do
these
broad
audits,
I
I
do
not
the
last
time
I
did
like
a
serious
double
hey,
I
got.
It
was
long
long
long
time
ago,
so
I
think
there's
a
lot
of
automation,
that's
going
to
help,
but
then
there's
all
sorts
of
discovery
that
needs
to
be
done.
A
A
A
A
Yeah,
if
you
take
a
look
at
the
the
lighthouse
report
itself,
one
of
the
things
that
they
they
do
again.
You
know
it's
kind
of
acknowledge
that,
but
it's
a
but
it's
a
bit
hidden.
So
if
I
can
find
this,
you
know
they're
not
applicable,
but
also
you
know
additional
items
to
manually
check.
These
are
some
things
to
look
at
in
the
future.
I
would
say
for
the
purposes
of
what
we've
got
here:
I
think
just
addressing
that
again
kind
of
the
bigger
ticket
items
which
hopefully
are
lower
lower
effort
that
work.
A
A
All
right
so
I'm,
gonna,
I'm
gonna
assume
at
least
again,
because
we're
not
gonna
do
the
points
like
we
did
in
the
past.
I
would
assume
that
this
is
straightforward
enough,
that
somebody
could
pick
it
up
internally,
externally
or
otherwise
be
able
to
to
use
this
a
guy
use
lighthouse
against
the
the
three
key
experiences
for
at
least
for
Venga
and
be
able
to
make
you
know,
make
the
necessary
changes.
Invalidate
those
and
in
kind
of
a
single
single
form,
is
that
that
is
this
well
understood
enough,
for
that
is,
are
we
missing
anything?
G
G
There's
some
things
in
there.
That
would
be
easy,
but
there's
some
that
like
reach
too
far,
that
would
probably
make
some
some
planning
and
coordination
yeah,
and
so
as
soon
as
we
get
in
there,
it's
like
we're
dealing
with
the
form
fields
right,
yeah.
You
know,
when
you're
you're,
trying
to
create
a
comment
that
everyone's
gonna
be
using
all
over
the
place.
You
know
it's
not
just
to
get
to
get
it
working.
You
have
to
get
the
API
right,
or
else
we
factor
it
again.
A
Yeah
I'm
almost
envisioning
a
larger
epoch
for
accessibility
in
general,
but
then
my
hopes,
my
again,
my
quickly
informed
hopes
would
be
is:
are
there
lohank
so
when
I'm?
Looking
at
these
three
items
here,
the
elements
seems
to
be
the
one
that
could
imply
some
refactoring
right
so
there
to
be
a
whole
story,
potential
and
just
buttons
alone,
but
which
doesn't
solve
everything
but
like
but
yeah.
So
but
then,
potentially
these
other
two
might
be.
G
A
What
about
this?
What
about
this
last
one
here,
the
page
specifications
is
not
just
a
global
elements,
HTML
elements
with
a
language
attribute,
or
that
is
that
a
potential
refactor
like
light
language
specifications.
A
B
A
One
quick
one
at
a
time
and
I
think
of
the
spirit
of
that
that
might
be
helpful
for
that
one.
So,
instead
of
kind
of
bunching
us
up
happy
to
do
that.
So
basically
what
we'd
be
looking
at
kind
of
reworking
this
into
a
more
holistic
accessibility
effort,
which
I
think
makes
a
lot
of
sense,
but
then
start
to
break
this
into
two
smaller
pieces
around
some
of
some
quick
hits
and
some
other
ones
that
will
be
prioritized,
but
also
could
be
some
simple
ones
that
could
be
tackled
tackled
soon.
A
A
Cool
all
right,
so,
while
we're
on
the
topic,
accessibility
I
want
to
do
it.
Just
a
quick
shout
out
again
to
Gil
it's
something
digital,
and
so
he
made
a
suggestion
here
that
I
think
would
fit
nicely
in
that
epoch.
So
again,
I'm
just
trying
to
look
at
this
as
a
bucket
of
changes
that
that,
while
somebody's
looking
at
accessibility
holistically,
he
has
quite
a
few
details
around
what
essentially
would
be
you
know:
keyboard
controls
right
so
be
able
to
to
get
to
to
use
escape
keys
and
kind
of
go
through
at
a
border.
A
That
makes
sense
relative
to
the
the
sliders
that
we
have
in
the
mini
checkout,
so
I
mean
for
products
standpoint.
That
makes
a
lot
of
sense.
You
know
is
this.
You
know
this
is
an
obviously
lighthouse
dependent,
but
it's
the
right
thing
from
an
accessibility,
standpoint
and
so
I
would
say
I'm
from
a
grooming
standpoint,
though
I
would
ask
to
do
to
this
audience.
Is
this
well-defined
enough
that
we
could
hook
this
into
an
epic
or
should
we
should
we
either
add
details
or
break
this
out
and
some
some
other
other
aspects
so.
B
A
A
G
A
G
G
A
A
Cool
that
makes
sense
so
I
will
I
will
based
on
where
we
just
left
off
with
accessibility.
Prior
to
that
I
will
I
will
hook
this
into
an
accessibility
ethic,
so
I'm
thinking
about
accessibility,
I
think,
but
also
looking
at
just
as
you
know,
offline
ethic
separately.
We'll
look
at
these
experiences
that
kind
of
are
crosscut
against
some
of
those.
Some
of
the
more
traditional
campus
experiences
as
well,
so
so
organize
that
I'll
send
some
some
notes
out
and
which
you
guys
know
one
that's
ready
so
and
I
think
some
of
those.
A
If
I
might
understanding
right,
you
guys
keep
be
honest,
might
be
good
good
first
issues
as
well
like
the
the
footer
or
some
of
those
other
things
as
well
might
be,
might
be
good
ones
as
well
for
folks
are
looking
to
contribute
so
I
work
well,
cool!
All
right!
Thank
you,
everybody
all
right!
So,
let's
switch
gears
then
now
into
to
documentation.
So
we've
got
mr.
mr.
kouchuu
been
here.
One
of
the
epics
that
we
had
a
couple
weeks
ago
was
around
these
developer
tutorials
for
for
canoes
to
do
in
backgrounds.
A
The
idea
here
was,
you
know
now
that
we've
got
a
good
baseline
of
documentation
for
the
you
know
for
the
product
itself.
You
know
between
the
feedback
that
we
know
and
the
feedback
that
we're
hearing.
You
know
people
were
anxious
and
excited
to
get
started.
You
know
creating
kind
of
their
first
components
for
you
know
component
and
applying
that
to
then
yeah
and
or
even
more
so
thinking
about
setting
up
and
extending
vineya
for
themselves
kind
of
for
their
own
purposes.
Right,
and
so
some
of
them
are
probably
much
larger
asks
around.
How
do
we?
A
A
So
I
think,
with
that
in
mind,
I
mean
some
of
the
some
of
the
topics
we
did,
we
did
suggest
is
is
know
an
overview
of
PWA
introductions
to
development
tools,
which
is
more
of
a
lincoln
launch
type
of
scenario,
especially
for
things
like
lighthouse
and
I
d--'s
web
fundamentals,
which
I
guess
some
basics
here-
the
ones
that
I
once
I'm
kind
of
interested
in
some
of
the
basic
exercises
where
you
got
changing
the
color
image.
I
know,
James
has
done
that
demo,
several
times
kind
of
showing
what
you
know:
hot
module
reloading.
A
What
looks
like
and
and
then
begin
to
again
just
point
to
some
resources,
though
you
know,
because
we
didn't
build,
react
reduction
webpack
that
those
those
would
make
sense,
and
so
what's
everybody's
thoughts
on
this
I
would
say
from
a
usefulness
perspective
and
the
kind
of
the
right
level
of
information
that
we
could
help
help
James
get
started.
I
have.
B
To
say,
I'm,
Nigel
reloading
is
still
something
of
a
I.
Don't
know
controversial
topic
in
front
end
in
the
same
way
that,
like
some
of
the
major
projects
have
given
up
on
trying
to
make
service
workers
a
good
development
experience
which
we
are
not
doing,
we
are
getting
it
right.
The
the
community
at
large
I
think
finds
hot
module
reloading
to
be
a
story
that
didn't
ever
stabilize,
but
we
don't.
B
It
doesn't
have
to
be
that
way
that
the
webpack
API,
for
it
is
a
little
strange
and
difficult,
but
it
is
sensible
and
robust
and
we
can
get
there
so
I
guess
what
I'm
saying
is.
Maybe
we
don't
index
too
hard
on
hot
module
reloading
until
the
story
is
better
because
there's
already
some
sort
of
low
NPS
about
it
out
there
separately
I
think
it's
totally
worth
talking
about
what
the
development
experience
is
and
how
it
differs.
Sort
of
technologically
from
the
staging
experience,
because
I
think
people
know
that
you
run
to
different
commands.
B
But
there
is
some
getting
used
to
like
Magento,
it's
known,
that
it
works
differently
in
development
mode,
but
a
lot
of
that
is
kind
of
behind
the
scenes.
Our
servers
also
work
differently
in
development
mode,
and
it's
it's
definitely
worth
having
a
diagram
that
demonstrates
what's
going
on
the
fact
that
you're
doing
incremental
compiles
and
that
helps
to
sort
of
answer,
people's
questions
that
may
come
up
about
why
a
build
takes
a
long
time
in
one
case
and
not
in
another,
though
I
mean
not
talking
too
much
about
hot
module.
C
A
Is
right
in
some
of
them
removing
targets,
right
and
so
I
think
I
think
for
from
my
standpoint,
finding
the
areas
that
would
allow
people
to
make
some
immediate
kind
of
quick
wind
changes,
or
this
trip
to
feel
comfortable
with
that
against
the
things
that
were
probably
the
most
high
is
the
high
it
had
the
highest
confidence
right
in
terms
of
you
know,
you
know
making
sure
that
we
don't
subject
James
to
too
many
changes
after
they
evolve.
So
yeah.
A
I
mean
at
the
highest
level
about
you
know,
imagine
you're
a
new
developer,
who
has
never
touched
us
before
and
not
familiar
with
their
grooming,
all
that
and
maybe
not
even
seen
a
demo
you've
set
up
and
configured
venya
and
you're
ready
to
make
a
and
you're
considering
using
this
for
your
next
project,
not
many
itself
but
maybe
Paragon
build
another
store.
So
almost
the
hello
world
equivalents
of
that
or
play
around
with
it.
So
we
want
to
encourage
experimentation.
G
B
G
C
C
A
G
A
A
G
G
A
And
so
so,
for
this
one,
why
don't
we
do
this
for
that
for
the
for
the
actual
test
themselves?
Let's
do
this
is
because
this
is
to
me
it
feels
like
it
was
it's
more
of
a
more
of
a
research
spike
around
documentation,
because
I
think
there
is.
There
is
a
an
element
of
talking
to
Shane
LM
talking
to
the
team
about
this
one.
So
this
this
alone
could
be
a
couple
days
unless
we
want
to
include
the
research
and,
as
part
of
that,
with
early
adopter.
A
So
these
are
basic,
I,
think
things,
maybe
as
far
as
we
can
get
this
without
without
just
doing
a
little
bit
of
research
ourselves
on
this
one,
so
this
at
least
gets
that
started.
I
do
think
this
at
least
gives
us
something
to
work
from
that
is
higher
priority
than
maybe
some
of
the
overview
and
referential
documentation.
A
We
have
for
the
other
things
and
so
I
think
that's
good
I'm
gonna
sign
this
to
to
add
to
jimothy,
but
then
and
then
work
with
him
on
the
details
and
come
up
with
some
of
them
kind
of
a
list
of
folks
to
kind
of
research.
This
with
too
much
it's
a
bill.
That's
that,
of
course,
you
know
internally
will
validate
that
as
well.
A
B
A
Is
there
any
anything
differently,
we
would
do
for
the
roofer
kind
of
the
plumbing
story,
or
is
it
almost
a
clone
of
this?
That
basically
takes
the
same
idea
and
same
notion
of
of
this,
and
then
then,
checks
in
with
with
folks
have
gotten
ahead
of
this
and
also
discusses
internal?
Is
that
do
you
think
that's
fair
little
yeah.
B
A
A
All
right,
this
is
perfect,
baby
shiet.
We
have
a
shy
group
today,
so
it's
usually
alright.
So
a
couple
other
things,
so
we've
got
quite
a
bit
here
in
terms
of
for
grooming,
I
liked
at
least
tech
take
a
look
at
one,
at
least
as
a
team.
We
may
decide
it's
not
ready
yet,
but
I
did
want
to
talk
a
little
bit
about
this,
so
this
will
be
kind
of
a
you
know.
A
We
would
like
to
do.
Is
parallel
path,
this
from
both
a
technical
in
the
UX
standpoint,
so
so
Paul
had
suggested
this
one
I
thought
was
a
good
one,
and
you've
probably
seen
this
in
some
of
the
demos
where,
if
you're
in
the
middle
of
a
middle
of
kind
of
browsing,
a
Vinny
experience,
there
may
be
situations
where
that
fallback
image
just
isn't
there
isn't?
A
Is
it
ready
and
it's
you
know,
really
we're
leaving
it
to
the
browser
and,
of
course
the
browser
is
doing
its
very
best,
but
it's
it's
just
not
it's
not
elegant
right
and
so
there's
poor
Agusta
in
earrings
that
come
around
at
necklace
is
sitting
there
with
a
broken,
broken
sad
image
that
could
be
very
well
replaced
with
them.
Much
more
robust
background
image
and
possibly
a
better
better
alternative
for
this
offline
state
as
a
whole.
So
I
think
we've
got
some
good
quick
fixes
in
there
for
MVP
there's.
A
Definitely
some
design
work
that
will
queue
up
with
Sammy
moving
forward,
but
I,
don't
want
to
do
is
at
least
bring
this
to
everyone's
attention
in
terms
of
the
detail
here
now
that
we've
got
offline
checked
in
which
is
the
you
know,
the
dependency
that
Paul
had
identified
but
get
anybody's
feedback
about
this.
While
we
then
parallel
path
and
attach
some
UX
work,
which
would
be
that
last
consideration
before
this
actually
gets
get
started.
So
what
does
everybody
think
any
any
thoughts?
Any
questions
any
any
concerns
on
this
one.
B
B
Then,
just
here
I'll
pull
it
up
myself,
I'm
in
sin
hub,
so
493,
yeah,
yeah
yeah.
So
here's
the
thing
it's
already
merged
right,
but
the
broken
images
I
just
commented
on
this.
The
the
the
broken
images
thing
is
actually
it
crosses
with
accessibility
concerns,
I.
Think.
A
lot
of
people's
first
instinct
is
to
simply
not
use
image
tags
since
the
way
that
they
break
is
so
yucky,
and
it's
feels
like
you
have
a
lot
more
control
over
background
images,
so
you
would
style
it
all
as
a
background
image.
B
You
can
first
of
all
not
use
image
tags
directly.
You
can
use
source
sets
so
that
fallback
images
are
data
URLs
and
secondly,
there
are
a
lot
of
pseudo
elements
around
the
image
element
that
you
can
change.
So
we
actually
probably
don't
have
to
write
a
lot
of
weirdo
JavaScript.
To
get
to
this
I
would
say
it's
probably
a
pretty
small
story.
It
just
involves
looking
up
some
cool
CSS
tricks.
A
So,
from
from
your
guys
mind,
it
seems
like
there's,
there's
pretty
good
line
of
sight
on
what
what
could
be
done,
at
least
as
part
of
this.
There
may
not
be
that
dependency
on
assets
that
they
Paul
had
mention,
which
you
think
is
a
good
thing,
but
but
do
we
feel
like
this
is
enough
to
at
least
for
in
the
future,
for
for
someone,
you
know,
like
you
guys
or
someone
else,
to
pick
this
up
and
take
a
look
at.
G
C
C
G
A
Alright,
so
I
just
add,
comment
I,
think
Paul
structured
it
nicely,
but
then
I
just
said:
hey
a
suggestion
from
grooming
to
consider
content
versus
acid
call
back
and
so
I
think.
At
least
this
is
appears
to
be
enough
to
get
started.
Paul
did
a
really
nice
job
at
identifying
what
the
the
situation
is
and
I
think
for
this
one.
We
could
probably
even
mark
it.
You
know
even
market
ready
to
start
so
that
one
doesn't
see.
It
feels
pretty
good,
obviously
be
questions,
probably
for
Jimmy.
I.
A
Understand
me
along
the
way,
but
I
think
we've
clarified
the
and
clarified
the
end.
The
need
here
and-
and
you
know,
they'll
beat
something
and
we'll
track
this.
You
know
track
this
ongoing
for
whoever
picked
this
up
so
cool,
alright,
and
so
those
are
the
bulk
of
things.
I
know
we
just
have
a
couple
minutes
left
there.
There
are
plenty
of
things
to
work
on
you
know.
I
did
want
to
cover
things
like
the
mail
templates
again
for
venya.
A
There
were
some
questions
on
how
that
can
be,
how
that
they
get
done
so
the
idea
that
was
around,
if
you
you
know,
for
confirmation,
emails
and
things
like
that,
as
we
think
about
sample
data
as
a
whole,
you
know
how
do
we
essentially
venue
five,
the
things
that
are
coming
by
way
of
luma,
so
is
that
configuration
thing
a
data
thing
or
otherwise?
So
we
can
take
that
offline.
I
know
that
was
outstanding
for
the
team
to
kind
of
take
a
look
at
so
low
hanging.
A
Fruit,
infinite
finish
there
and
then
we've
also
got
a
few
other
ones
as
well.
One
of
things
we
did
want
to
talk
about
was
the
this
upward
PHP
server,
but
I
think
James
is
looking
at
some
of
the
options
here
internally
as
well,
and
so
when
we
come
back
around
to
that
one
and
groom
as
a
team
next
week,
but
that
was
that
was
one
of
the
ones
we're
looking
at
as
well
as
a
couple
small
venue,
improvements
or
rounds.
A
Now
that
we've
got
a
working,
cart
and
check-out
to
start
thinking
about
how
do
we
show?
How
do
we
consider
items
as
part
of
as
part
of
that,
but
I
think
we
need
to
take
a
look
at
the
UX
a
little
bit
further
on
that
one
before
before
that
one's
ready
to
groom
them
as
well.
So
lots
of
lots
of
things
in
the
hopper
there
other
things
like
sticky
footer
here,
which
we,
which
we
had
a
good
start
on,
that
the
Andrew
that
it
got
up
and
running,
but
I
do
think
again.
A
A
B
I
think
that,
in
the
absence
of
the
PHP
architects,
and
also
in
the
absence
of
an
actual
decision
at
a
cloud,
I
think
I
don't
want
to
use
people's
time
speculating
today.
There's
a
lot
of
there's
a
lot
of
work.
Work
to
push
n,
Jimmy
and
I
are
working
on
merges
as
we
speak,
so
there'll
be
more
to
update.
Soon,
thanks
to
I
mean
thanks
to
everyone
for
bearing
with
us
in
the
holiday
season
right,
yep.
A
That's
coming
up
in
graph
kewal,
and
so
we
knew
that
we
need
to
think
through
there's
a
little
bit
and
so
but
I'm
hoping
we
can
make
some
some
good
progress
on
that
one
grooming
and
get
those
tagged
for
someone
to
take
a
look
at
in
the
next
week
or
so
so
bear
with
us
on
that.
One
obviously
p.m.
any
questions.
Let
us
know
cool
anything
else,
any
other
questions
or
comments
before
we
break.
A
All
right,
well,
very
good,
will
hate.
Thank
you
so
much
again,
everybody
a
good
grooming
session,
and
if
anybody
has
any
questions,
let
me
know
and
they'll
start
working
on
some
of
some
of
my
homework
here
on
accessibility
and
some
of
the
other
items.
So
thank
you
again
for
everybody's
time
and
we'll
talk
soon.
Thank
you.
Yes,
yep.