►
From YouTube: PWA Studio, community demo, July 17, 2018
Description
Joined sprint demo of on PWA studio by the community and Magento core teams.
A
Of
our
agenda,
we've
got
to
met
again
a
lot
to
cover,
so
we're
gonna
start
off
with
the
beginnings
of
a
merge
and
some
of
the
work
that
we've
done
on
on
the
cart
and
checkout
experience.
I
hear
that
both
Jimmy
and
James
have
been
working
on
and
so
bit
of
a
carryover
from
that,
and
so
we'll
start
there
and
then
we'll
then
we'll
switch
gears.
I
definitely
want
to
have
art
share
some
of
the
working
progress
on
the
shop
by
category
experience
and
then
we'll
go
through
a
couple,
quick
items.
A
We
had
some
things
relative
to
github
in
some
some
sample
data
that
we're
tracking
down
to
us
to
make
all
of
this
make
all
of
this
right
and
then
and
then
we've
got
some
UX
and
documentation
items
as
well,
so
pretty
full
agenda.
We've
actually
expanded
a
time
to
60
minutes
versus
you
can
45
just
so
that
we
can
make
sure
we
cover
everything.
So
so
any
any
questions
before
we
get
started,
no
okay,
very
good,
so
that
might
I'm
going
to
turn
it
over
to
a
to
James
and
Jimmy.
B
B
B
C
We're
gonna
install
the
fantasies
here.
Great
thing
about
this:
is
the
developer
experience
part
of
running
TW
a
studio,
the
mono
repo
is
on
display
here,
which
might
be
noticing
people.
You
have
the
the
original
setup
of
multiple
repositories
that
we
had
to
try
and
convince
a
with
each
other
had
a
lot
of
overhead
to
the
process.
That's
replaced
with
the
learning
utility,
which
was
invented
for
the
situation
used
by
some
of
the
larger
JavaScript
projects
like
Jess,
and
it's
just
builds
Paragon
build
pack
and
renting
out
all
the
ones.
B
C
You
can
see,
we've
got
live
data,
you
can't
mock
up
every
single
and
I
think
in
the
last
time,
I
could
show
that
there
was
graph
QL
powering
that,
but
the
new
thing
is,
you
can
add
to
the
cart
or
you
should
be
able
to
unless
you've
got
bunch
of
roping
stuff.
Okay,
well,
I
mean
broken-bat
state.
We
are
okay.
C
D
C
A
E
E
E
E
D
E
F
E
E
A
A
This
is,
this
is
a
fantastic
start
and
you
can
took
some
things
that
are
in
progress
and
just
I.
Think
for
the
purpose
of
this.
It's
just
a
really
good
preview,
and
what
we
can
do
is
a
sync
up
afterwards
and
kind
of
help.
You
walk
through
ready
any
questions
you
have
and
and
and
figure
out
how
we
can
continue
making
some
progress
on
this.
So
this
is
a
really
good
start.
A
A
C
C
Just
to
reiterate:
that's
it
places
one
SQL
up
go
ahead
and
zoom
this
out.
It
places
one
Greg
Oh
watch
the
responsive
design.
Oh
goodness,
places
one
graph
QL
call
in
order
to
resolve
which
it
does
so
via
the
SEO.
You
are
element,
oh
there's,
a
number
of
different
ways:
our
URLs.
All
the
service
will
expand
to
do
that,
pulls
up
the
routes,
components
to
understand
what's
capable
of,
and
then
it
it
used
graph
QL
to
fetch
the
product
detail.
C
Now
it
also
ran
a
different
call,
my
recognises
being
to
rest
API
in
order
to
get
the
guest
cart,
that
we
have
in
our
local
storage
and
confirm
its
totals
put
those
together
into
an
object,
that's
available
in
the
redux
tree.
If
you'll
see
I,
try
to
add
another
one
of
these
two
cars
party
and
to
so
oh
no
I
guess
I
cleared
it
because
I
checked
out,
but
you.
C
Anything
more,
it
comes
back
and
you
can
see
those
calls
as
they
go
past,
which
you
might
observe
is
that's
also
they're,
not
graph
QL.
They
they're
still
running
through
the
duct
system
and
they're
still
causing
full
updates
to
Louie.
Actually,
so
this
demonstration
of
the
simplest
kind
of
integration
possible
between
the
the
REST
API
and
a
small
abstraction
there
too,
and
the
the
graph
QL
parts
that
Anil
catalog
and
then
the
final
part.
The
integration
is
that
this
Add
to
Cart
business.
C
You
can
see
that
because
if
we
now
go
and
add
something
else
to
the
cart,
we're
back
to
the
three
that
we
just
added
you're,
not
added
more
I
can
proceed
to
checkout
again,
six,
please
so.
This
demonstrates
an
example
of
Awesome
parts
of
the
state
that
are
not
the
checkout
slice
reacting
to
the
checkout
slice
and
modifying
their
own
State
I'm
gonna
go
now
to
the
joust
duffel
bag.
C
Again
this
to
demonstrate
that
it's
so
strange
that
that
happens
ago,
we're
bugging
this
chrome
and
so
I'm
going
to
add
this
thing
to
carts,
find
that
there's
a
new
cards
there
and
it's
checkout,
and
now,
if
I
try
to
summon
the
card
again,
which
I
can't
do
because
of
the
usual
thing.
Where
this
is,
and
you
find
that
there's
still
nothing
there,
why
click
continue
shopping
still
tweak
as
cards
check
out?
C
Joins
the
party
and
subscribes
all
of
the
necessary
parts
of
the
react
lifecycle.
It
does
so
in
a
way
where
it's
adds
its
own
logic,
that
understands
cart
and
checkout
to
the
store
itself
and
reducer
sort
of
prototype
extension
mechanism,
and
that
adds
logic
that
adds
logic
that
understands
how
to
react,
checkout
actions
and
how
to
react
card
actions.
In
this
case,
it's
actually
synchronously
building
a
reducer,
because
the
cart
reducer
is
built
to
rely
on
some
asynchronous
storage
logic
they
think
about
it.
C
Is
that
the
carts
and
check-out,
even
though
they
are
entirely
separate
slices
that
add
different
elements
to
the
readout
store,
can
still
subscribe
to
each
other's
actions.
There's
arts
user
for
the
cart,
responds
to
all
of
these
card
actions
and
those
how
to
handle
it
and
return
some
state,
but
it
also
subscribes
to
an
order
action
when
the
owner
is
accepted,
it
really
guest
card
ID
and
that's
how
these
things
work
and
that's
how
integrating
between
slices
can
be
very
easy
to
accomplish
and
still
quite
decoupled,
and
that's
that's
the
full
integration
demo.
C
A
D
A
Some
excellent
so
lets
us
switch
gears
here
we
got
a
couple
verbal
updates.
These
are,
these
will
go
quick,
and
so
these
are
from
james
just
a
you
know,
just
for
the
benefit
of
the
audience
on
kind
of
what
we're
doing
for
and
what
we
did
for
opening
things
to
the
public
with
regard
to
magenta
research
and
then
some
of
the
working
some
shell
miller's
team,
onion
sample
data,
so
we
provide
an
update
on
them.
C
I
would
love
to
the
magenta
research
organization
originally
had
private
repositories,
and
this
is
because
we
were
beginning
a
Magento
research
initiative
inside
the
company
and
you
figure
out
how
to
have
a
separate
organization
that
had
a
slightly
different
missions
from
community
engineer.
The
great
news
is
community
engineering
and
us
and
our
Magento
research
people
have
been
talking
a
great
deal
attending
contribution
days
together,
and
we
agreed
that
our
missions
are
not
so
different
as
to
need
those
efforts,
privates
workflows,
so
beginning
a
process
in
British.
C
The
gentle
researches
mission
is
to
contribute
back
to
the
external
ecosystem
of
the
PHP
and
JavaScript
and
any
other
technologies
that
we've
use,
like
any
other
open-source
company,
does
Adobe's
committed
to
this
as
well.
So
as
this
works
really
well
with
the
way
we're
going
to
integrate
future.
So
to
that
end,
we
got
rid
of
all
the
private
repositories
that
were
just
maintaining
some
back
office
stuff
and
some
sort
of
initial
experiments
in
the
Magento
research
organization
to
make
it
completely
public,
in
the
spirit
of
our
completely
open
development
process.
C
For
this
one,
nice
side
effect
of
that
is
that
now
we
no
longer
pay
for
the
seats
right
and
we
are
no
longer
limited
in
to.
However
many
seats
we
have
paid
for
so
those
of
you,
who've,
been
treated
can
now
find
yourselves
invited
to
be
members
of
the
organization.
This
took
some
a
little
more
doing
than
it
should
have,
because,
as
you've
made,
the
transitions
between.
D
C
C
About
the
the
venía
sample
data,
you
might
notice,
in
your
own
work
and
in
ours
that
we're
still
showing
off
yoga
mats
and
backpacks
inside
the
the
many
experiment
experience
that
we're
building-
and
this
is
because
the
sample
data
that
exists
in
the
magento
sample
data
repository
for
which
there's
all
this
documentation,
that
and
for
which
the
code
is
very
stable.
Everyone
knows
how
to
import
it
all.
That's
the
loominator.
We
do
have
any
store
data.
C
We've
engaged
our
solution
control
the
consultants
team,
so
we
have
some
outside
help
doing
this,
but
they
have
committed
to
producing
a
module
which
can
install
and
the
venía
sample
data
into
your
Gentoo
instance
in
one
style
and
we're
going
to
add
this
to
the
recommended
development
setup,
so
that
so
that
us
and
you
can
begin
working
with
data.
That
fits
the
theme
and
that
fits
the
the
user
experience
and
the
use
cases
for
the
vertical
that
he
has
built
for
for
for
fashion.
That's
that's
to
me.
C
A
A
Alright,
very
good,
so,
let's
up,
let's
switch
gears
to
us
aux
so
Sammy
is
going
to
walk
us
through
some
of
the
updates
on
my
account.
So
as
you
guys
can
imagine,
what
we're
trying
to
do
is
to
stay
one
step
ahead
if
some
of
the
proofs
of
concept
or
on
check
out
and
so
Sam
is
keeping
us
honest
on
that
and
and
so
she's
gonna
walk
us
through
some
of
the
my
account
pieces,
hi.
G
G
So
currently
exploring
access
to
my
account
through
the
main
menu.
If
the
person
does
not
have
an
account,
yet
you
would
see
a
create
an
account
button
here.
Instead,
I'm
assuming
everyone
can
see
my
screen.
Okay
in
the
event
that
they
have
created
an
account
and
I'm
not
signed
in,
they
would
do
so,
and
this
would
be
a
sticky
footer.
G
So
they
sign
in
this
is
sort
of
similar
to
how
Android
does
it's
signed
in
experience
and
access
to
my
account
on
things
like
Google
Drive.
So
this
is
what
it
would
look
like
if
you
didn't
have
any
you
know
new
items
inside
your
account.
If
you
did
have
new
items,
you
would
see
a
little
indicator
that
you
know
that
that's
available
for
you
to
check
out
I
mean
no
checkouts,
the
wrong
word
available
for
you
to
look
at
and
then
on
the
the
my
account
section
itself.
These
are
some.
G
You
know
conceptual
sort
of
areas
that
were
thinking
still
thinking
about
which
ones
to
build
out
in
detail.
But
if
you
had
a
your
profile
would
contain
things
like
if
you
enter
preferences,
or
you
know,
brands
you,
like
your
size,
information,
etc
purchase.
History
is
what
you've
purchased
on
the
store.
If
the
store
did
have
a
rewards
program,
you
would
see
an
indicator
of
you
know
whatever
you've
earned
in
this
case
the
example
says
points,
but
it's
not
it.
That's
not
a
you
know
it's
not
set
in
stone.
G
Then
you
see,
if
you
do
have
any
notifications
you
haven't
looked
at
yet
wish
lists
and
security
settings
would
be
passwords,
and
you
know
things
like
that
and
then,
of
course,
a
way
to
sign
out.
So
if
you
were
to
go
in
and
then,
if
you
close
this
out,
you
would
go
back
to
the
main
menu.
So
if
you
were
to
go
into
notifications,
there's
sort
of
broadly
bucketed
as
things
that
you
haven't
looked
at
yet
and
order
things,
some
design
changes
are
still
pending
to
this
section.
G
But
one
thing
we're
exploring
is
just
like
in
the
mini
cart.
If
you
wanted
to
nest
more
actions
on
a
message
via
a
swipe
or
a
tab,
you
could
do
it.
This
way
where
you
could
either
delete
individual
messages
or
you'd
have
option
to
clear
all
your
notifications,
and
this
is
something
we
could
extend
to
other
sections
of
this
site
as
well.
So
that's
what
we
have
so
far,
Oh.
A
G
It
depends
on
which
journey
we're
showcasing
right.
There
will
be
multiple
prompts
throughout
the
the
shopping
experience
to
create
an
account,
typically
after
first
purchase
or
right
before
first
purchase.
You
would
advertise
that
there
is
a
rewards
program
that
you
can't,
you
know
be
a
part
of
unless
you
have
an
account
either
before
you
checkout
or
after
your
first
successful
purchase.
You
would
prompt
somebody
to
create
an
account
as
far
as
recognizing
or
showing
a
view
within
the
navigation.
Whether
somebody
has
an
account
or
not.
G
That's
not
a
point
in
the
journey
that
has
been
explored
in
that
particular
path.
Yet
definitely
a
good
point
to
note
and
we'll
talk
about
it
internally,
but
I
think
before
that
we
would
have
to
kind
of
identify,
which
is
the
best
place
to
prompt
the
user
to
create
an
account,
because
if
before
they've
done,
they've
before
they've
made
a
purchase,
so
when
they're
just
exploring
for
the
first
time,
chances
are
that
that
annoying
notification
that
pops
up
as
soon
as
you
log
onto
a
site.
Now
that
says
you
don't
have
an
account.
G
A
C
Corresponds
to
OAuth
I
mean
you
you're,
your
auth
tokens
expire
that
you
refresh
token
is
not
and
that
map
directly
on
see
the
user.
Experience
of
we
know
you're
there,
like
you,
visited
before
your
cookie
has
your
name
and
in
it,
but
you're
not
authorized
enough
to
like
change
your
password
that
more
the
warmest
day.
Is
it's
already
there?
So
are
you
already
affected
and
what
you.
G
Definite
very
good-
and
perhaps
it's
one
of
those
things
where
on
first
to
load,
they
don't
see
the
option
to
sign
in
or
create
an
account
inside
the
menu,
but
once
they've
been
prompted
once
then
it
shows
up
there
on
a
subsequent.
Yes,
sir
I
mean
this
is
these
are
just
these
need
to
be
explored
just
thinking
aloud,
but
yeah?
That
would
be
my
bigger
question.
Mr.
prompt,
very
good.
Any.
A
F
Documentation
updates.
For
me,
there
are
two
new
topics:
I
published
they're,
both
under
a
Benny
Athene
section.
One
of
them
is
a
simple
rest
check
out
club,
but
the
games
demonstrated
a
war,
of
course
gonna
iterate
on
this,
but
this
is
basically
what
you've
seen
a
s
demo
and
a
little
bit
of
today's
demo.
It
goes
through
the
shopper
experience
the
rest
endpoints
were
using
and
then
the
detailed
technical
flow
of
the
events
that
are
being
produced-
and
so
that's
here
and
the
other
documentation
that's
published
for
this
spring
is
home
page
design.
F
This
is
the
work
that
saw
me.
I
did
and
now
that
that's
public,
you
can
go
ahead
and
check
out
the
details
for
each
of
the
components
here
they're
listed
here,
and
you
can
see
the
reference
images
you
can
click
into
and
you
can
see
the
specifications
that
that
are
associated
with
that
component
and
there
are
different
variants
of
components
like
carousel
and
sample
banner,
small,
large
and
then
promotional.
A
That's
great
James
yeah
I
mean,
if
you
think
about
it,
we're
really
trying
to
solve
some
of
those.
Some
of
those
questions
you
get
around
first
install
where
originally
you
get
that
CMS
placeholder
stub
experience.
You
know,
arts
taking
a
look
at
the
home
experience
building
off
of
from
that
and
then
kind
of
kind
of
pre
and
post.
We
were
looking
at
the
UX
of
documentation,
all
kind
of
the
same
kind
of
all
in
the
same
circles,
so
we're
excited
to
come
to
get
ahead.
Of
that.
A
My
account
is
next
I
think
we
know
I'm
21
we're
also
looking
a
little
bit
more
on
the
mini
current
for
that
which
is
good,
but
that's
it
so
so
those
are
our
biggest
updates
I'm.
Taking
a
look
at
I'm,
not
sure
if
andrew
is
here
for
the
he's
doing
a
little
bit
of
research
on
the
on
some
of
the
architecture
relative
to
some
of
the
extension
discussions
that
are
happening,
but
we.