►
From YouTube: PWA Studio Community Sync 7 April, 2021
Description
Topics this week include roadmap updates for PWA Studio and Venia, SSR improvements, and updates to My Account and Wishlist in Venia.
A
So
that's
gonna
be
our
first
bi-weekly
community
meeting,
so
we're
gonna
have
one
week
there,
regular
community
call
and
another
week
just
the
office
hours.
So
this
is
the
plan
for
now,
and
we've
already
had
one
office
hour
meeting,
which
was
a
great
start
and
success.
So
this
is
what
we're
gonna
continue
doing
there
like.
If
someone
happens
not
to
know
me,
I
am
a
new
andrew,
so
andrew
resigned
adobe
and
I
took
over
pwa.
A
You
might
know
me
from
a
page
builder
project.
So
now
I'm
a
mother
for
two
of
those,
so
the
agenda
for
today
is
basically,
I
wanna
share
their
roadmap
updates.
If
you
haven't
had
a
chance
to
see
that
on
github,
I
would
like
to
walk
you
through
and
like
have
some
time
for
questions.
A
If
any,
and
also
we
have
some
demos
from
the
team
about
my
account
and
which
list
progress,
that
is
it
on
the
course
side
on
the
community
side
guys
do
you
want
to
share
anything
during
this
call.
A
Okay,
you
still
have
a
chance
to
jump
in,
but
I'll
start
sharing
my
screen
and
walk
you
through
the
roadmap
updates.
A
A
Basically,
our
architect
is
working
on
the
proof
of
concept
and
we're
gonna
roll
out
that
first
attempt
next
community
call
in
basically
two
weeks.
A
So
that's
it's
a
bit
of
a
teaser
for
you
to
attend
that
call,
and
we
would
continue,
share
the
progress
and
to
gather
feedback
on
that,
because
we
definitely
want
to
make
sure
that
the
way
we
move
forward
with
the
global
styling
on
the
pwa
storefront
is
something
that
you
guys
will
be
comfortable
working
with
and
that
follows
like
developer
best
practices
and
makes
your
life
easier,
customizing
and
styling
pwa
magenta,
pwa
storefronts.
A
So
currently
we
are
investigating
and
looking
into
essential
work
that
need
to
be
done
for
the
adding
new
payment
methods
on
top
of
what
we
already
have
and
providing
those
additional
extension
points
to
make
that
easier
for
their
third
parties
to
add
the
new
payment
methods
and
make
sure
that,
with
the
each
upgrade
of
to
the
new
pwe
studio
version,
those
extensions
keep
in
the
working
state.
A
Also
in
on
a
kind
of
shopper,
experience
and
merchant
experience
side
we're
going
to
focus
on
product
prices
and
make
sure
that
they
are
correctly
displayed
across
the
catalog,
so
that
will
cover
the
price
ranges
and
as
low
as
price
representation.
That
is
very
common
for
their
configurable
products.
In
case
the
configurable
product
variation
has
different
price.
A
Special
price,
obviously,
is
a
big
one
and
the
catalog
sales
promotion
prices
also
gonna
be
displayed
in
a
category
one.
While
the
shop
are
browsing.
The
category
pages
and
product
detail
pages
there.
My
account
and
wishlist
keeps
keeps
the
priority
here,
because
the
work
has
already
started
and
you've
seen
with
the
pwa9
release
the
first
kind
of
first
tab
in
that
in
that
area.
A
So
we
have
already
implemented
the
adding
to
wishlist
and
viewing
the
product
in
the
wishlist,
and
we
keep
working
on
that.
We'll
talk
about
that
in
more
details
today,
as
I
said
also
there
in
the
scope
of
their
shopper
and
merchant
experience
for
this
year,
gonna
be
product
attribute
support.
A
So
all
of
the
default
product
attributes
that
exist
in
magenta
are
going
to
be
displayed
on
product
pages
and
category
pages
if
they
are
configured
so
so
that
will
enable
merchants
to
have
their
correct
product
representation
out
of
the
box
so
for
their
second
half
and
the
beginning,
basically
of
their
next
year.
A
We're
gonna
focus
on
the
integrated
server-side,
rendering
capabilities,
and
this
is
something
that
we
basically
do
the
rnd
at
the
moment
and
investigating
the
options
that
we
have
for
the
magenta
cloud
environment,
also
we're
looking
into
building
their
best
seo
best
practices
into
pwa,
storefront
support
and
economical
urls,
and
such
things
that
currently
is
out
of
the
box
magenta
functionality
to
make
sure
that
pwa's
storefront
remains.
A
So
for
the
second
half
of
this
year
on
the
shop
and
experience
side,
we're
gonna
introduce
the
additional
product
type
support
that
we've
seen
is
in
the
most
demand
across
their
merchants.
A
So
we're
going
to
support
custom
options
for
products
and
implement
the
simple
version
of
the
bundle
product,
also
very
desired
functionality
of
displaying
swatches
and
add
to
cart
button
on
a
category
page
that
streamlines
the
shopper,
experience
and
enables
buyers
to
configure
their
complex
product
and
add
that
to
the
cart
right
from
the
category
page
by
passing
the
product
page.
A
Also,
the
thing
that
concerns
magenta
commerce-
they
are
support
of
the
customer
segment
and
ability
to
display
their
targeted
content
with
the
dynamic
blocks
on
the
pwa.
Storefront
is
something
that
we're
going
to
introduce
in
the
nearest
future.
A
So
this
is
something
that
we
are
actively
looking
at
and
like
we,
we
agreed
on
internally
that
we're
not
gonna
publish
something
that
is
more
like
for
future,
so
it
just
doesn't
distract
you
guys
from
what
is
the
immediate
focus
and
what
we're
gonna
allow.
Next,
I
will.
I
will
allow
some
time
for
questions
if
you
have
any
on
that
before
we
move
forward
with
the
my
account
review
and
demo
any
questions
about
the
roadmap.
A
Oh
okay,
since
I'm
sharing
it's
kind
of
tricky
to
say.
B
A
That's
a
good
question
I
mean
here
I
have
like
what
has
been
included
in
the
previous
two
releases,
but
I
don't
think
we
have
that
that
kind
of
the
high
level
overview
across
all
of
their
functionality.
Eric
do
you
know
if
there's
anything
like
that.
C
And
adding
to
to
dev
docs
right,
and
so
we
will
definitely
take
a
look
at
it,
because
that
this
does
come
up
from
time
to
time,
but
we
don't
have
anything
ready
readily
available.
Yet
it's
more
of
a
look
forward.
Roadmap.
B
I
guess
I
would
also
say
if
there's
any
specific
functionality
that
someone
needs,
they
can
always
ask
in
the
slack
channel
someone's
bound
to
know
whether
that's
covered
in
that
use
case
would
be
covered.
And
then
obviously,
if
it's
not
then
open
a
feature
request
on
github
and
and
we
can
prioritize
it
or
check
it
out.
A
Oh
there's
a
question
about
the
for
the
desktop
optimization:
it's
actually
the
good
one,
because
it's
exactly
what
was
on
my
radar
lately.
So
after
the
mega
menu
release,
like
I
asked
myself,
what
is
are
the
things
that
we
need
to
do
in
terms
of
their
further
desktop
optimization
and
for
now
we
just
have
that
as
a
the
kind
of
research,
epic
for
their
product
and
ux,
to
identify
the
scope
that
we
want
to
prioritize
for
the
for
the
further
desktop
optimization
and
chris.
A
Definitely
we
can
work
close
with
you
to
kind
of
make
sure
that
your
feedback
is
taken
into
the
account.
Definitely,
we
are
gonna
keep
working
on
that
as
well.
We
just
need
to
identify
what
is
what
is
that.
A
Basically,
okay,
if
there
are
no
more
questions,
I
think
I
see
the
request
to
demo
their
lsp
and
ssr.
We
can
do
that
now
and
save
the
my
account
demo
for
later.
D
I've
been
working
on
ssr
with
pwa,
and
I
also
created
a
pr
for
this
because,
a
year
ago
there
was
a
discussion
about,
should
you
use
rendered
drone?
Should
you
just
create
templates
for
it
with
metadata,
but
google
from
may
is
also
going
to
count
core
web
files,
and
so
things
like
the
largest
content
will
paint
will
also
start
counting
and,
as
at
the
moment,
we
get
first,
the
spinner
and
then
it
loads.
D
The
rest
of
the
page
and
the
after
interaction
is
pretty
quick,
but
first
hit
is
the
the
thing
where,
where
an
optimization
can
be
made,
what
I
did
is
use
rendertron
to
give
the
first
hit
and
then
use
the
use
react
dome.
D
D
That
screen,
I
think
you
now
see
my
chrome,
I'm
not
sure
yeah.
We
can
see
that
this
you've,
probably
seen
before,
because
this
is
built
on
top
of
pwa
studio
in
which
normally.
D
We
get
this
spinner
and
the
actual
dome
element
which
is
first
loaded
is
the
one
with
javascript
is
disabled,
oops
and
then
it
starts
loading
the
actual
page.
D
But
what
I
did
is
return
the
static
html
from
renderton
by
using
the
rendertron
middleware,
which
is
created
for
react,
and
then
you
get
the
actual
html
and
by
using
react
hydrate,
it
rehydrates
the
page,
and
so
you
have
the
interaction
back
and
it's
only
on
the
first
page
head.
So
if
I
now
reload
the
page.
D
Then
you
get
the
the
largest
content
for
paint
immediately,
which
will
be
counted
for
in
the
core
web
files
without
needing
to
wait
for
the
spinner,
and
it
now
updates
the
actual
data
and
the
html
is
already
served
to
the
customer.
D
E
That
I
had
a
tiny
question,
so,
while
it
is
hydrating
what
is
like
the
user
experience
like
like,
do
you
prevent
all
interactions
with
that
static
page,
or
what
do
you
do
in
that
kind
of
intermediary
step
where
we
normally
would
have
seen
that
loading
indicator.
D
D
D
So
you
want
a
spinner
to
go
away
on
only
on
the
first
hit
and
when
the
customer
changes
to
another
page,
then
you
want
the
spinner,
because
the
customer
has
to
know
that
the
page
is
loading,
but
it's
pretty
fast
when
you
switch
between
pages
of
course,
so
it's
only
for
the
first
actual
hit.
So
when
you
come
from
the
search
engine
from
a
product
page
in
google,
for
example,
that
that
hit
is
faster
served
to
you.
A
A
Cool
okay,
thanks
for
sharing
this
luis,
it's
exciting
to
see
their
kind
of
ssr
solutions,
because
it's
definitely
a
valuable
feature
so
guys
who
wants
to
start
with
the
with
the
add
to
favorite
functionality.
A
E
Right,
can
you
see
avinia
yep,
great
okay,
so
the
feature
that
I
am
working
on
is
related
to
adding
to
the
favorites
from
the
category
page.
I
think
recently
we
merged
some
functionality
to
add
to
favorites
from
the
product
page,
so
this
is
actually
going
to
take
a
slightly
different
design.
E
E
There
now
so
after
you
see
that
message,
you
can
say:
okay,
I'll
sign
in
or
I'll
just
go
and
create
an
account
here.
E
All
right
so
now
I
am
authenticated.
If
I
go
back,
you
still
see
these
beautiful
hearts
and
if
you
see
something.
E
Like
this
hannah
sweater,
you
just
click
it
and
it
confirms
that
you've
successfully
added
so
right
now,
I'm
going
through
the
ce
flow,
where
customer
only
ever
has
one
wish
list,
calling
them
favorites
list.
So
there's
no
need
to
ask
which
one
they
want
to
add
it
to.
We
can
just
automatically
do
that.
It'll
also
function
this
way
for
ee.
If
you
have
multiple
wishlists
disabled,
so
very
easy
to
just
you
know,
click
add,
then.
E
If
we
go
to
our
favorites
list,
we
should
see
that
those
two
things
that
we
added
there
are
also
there
and
then
a
neat
caveat
is
since
we
added
this
to
the
gallery
item
component,
which
is
also
used
by
search.
E
So
let's
say:
if
we
do
a
search
for
vitalia
you'll
see
here
that
it's
persistent,
so
that's
another
change
from
the
product
page.
I
think
the
product
page
only
kept
track
of
the
state
while
you're
on.
C
E
You
left
and
came
back.
We
didn't
really
try
to
do
a
lookup
to
see
if
that
was
existing
in
a
in
a
wish
list.
So
now
this
is
using
some
local
state
that
when
you
log
in
it's
going
to
kind
of
collect
a
list
of
all
the
skus
that
are
in
your
product
list.
So
then,
when
we
render
those
views,
we
can
correctly
display
if
it's
in
a
wish
list
already
or
not
so
you'll,
see.
E
If
I
go
back
to
drop
the
look,
the
let's
see
the
hannah
sweater
and
the
vitalia
top
for
there
as
well.
If
I
out
and
then
sign
back.
A
E
E
I
will
likely
just
go
ahead
and
lazy
load
that
that
wishlist
data,
so
there
there
might
be
a
chance
if
you're
super
fast
after
you
log
in
and
go
to
a
view,
while
we're
still
collecting
that
data,
it
might
not
show
up,
but
as
soon
as
we
do
get
it
it'll
fill
in
as
expected,
and
then
the
ee
flow
is
going
to
be
very
similar
to
what
steven
demoed
from
the
product
page.
E
But
I
think
scott
was
going
to
go
ahead
and
run
through
the
xd
demos
of
that
functionality
and
show
off
what
you
can
expect
from
the
category
page.
F
Yes,
yes,
thank
you,
sir.
I
just
wanted
to
yeah
get
it
on
deck
here
so
yeah.
Let
me
oops.
I
pushed
the
wrong
button.
I'm
ready
really
okay
yeah,
so
I'm
just
going
to
share
with
you
guys
the
kind
of
the
prototype
for
the
ad
to
favorites
or
wish
list,
as
it's
known
in
the
parlance
of
m2
and.
F
F
That
all
right
all
right,
all
right
good,
I
just
I'm
kind
of
yeah
out
of
it
all
right,
so
we're
looking
at
the
the
mobile
view
here.
So
so
what
happens?
Is
you
know
category
page
here
they
see
the
category
listing
page.
They
see
those
those
tools
for
favoriting
and
in
this
case,
the
user,
the
shopper
taps
it
as
we
saw
before
their
head
and
tommy
had
mentioned.
F
There's
kind
of
this
gentle
message,
if
you
will
of
like
oh
you're,
not
signed
in
and
you'll
need
to
do
this.
If
you
want
to
save
this
thing,
to
favorites,
you'll
need
to
have
an
account,
etc,
and-
and
I
saw
there
was
a
message
in
chat
and
that's
kind
of.
F
Focusing
on,
but
I
think
this
is
a
little
gentler
to
let
the
shopper
decide
if
really
favoriting
is
kind
of
worth
the
effort,
and
so
in
this
case
let's
say
yes,
I
do.
I
do
have
an
account.
I
do
want
to
save
this,
so
they
open
this
or
create
account.
Option
is
still
there.
F
Of
course
they
enter
they
sign
in
they're
signed
in
get
back
to
the
page
they're
at
and
now
when
they
click
this
we're
looking
at
the
the
enterprise
edition
where
they
can
have
multiple
lists,
so
they
could
either
tap
this.
It
would
go
straight
to
that
favorites
or
that
default
list,
or,
if
they'd
like
to
create
a
new
list.
To
put
this
in
specifically,
I
can
do
that
right
from
here.
F
Add
a
name
select
kind
of
the
status
of
this,
whether
it's
private
or
public,
save
that
and
now
it's
saved
and,
of
course
the
message
comes
up
to
confirm,
and
that
was
a
little
quick,
but
you
could
see
it
actually
has
the
list,
the
name
of
the
list
that
it
was
actually
put
into,
which
will
help
as
a
shopper
kind
of
goes
through
if
they
want
to
add
things
to
different
lists.
They'll
get
the
confirmation
to
let
them
know
specifically
what
list
you
know
it's
it's
added
to.
F
If
we
could
look
at
that,
maybe
we'll
look
at
ce
on
desktop
view.
Just
real,
quick,
too
same
kind
of
thing,
so
they're
not
signed
in
the
message,
appears
sign
in
now:
they're
ready
to
go
now
they
if
they
continue
or
decide
they
wanna
go
ahead
and
save
that
because
there
aren't
additional
lists
or,
as
tommy
mentioned,
if
they
have
multiple
lists
turned
off
in
the
ee.
F
A
Cool,
thank
you
thanks,
scott
yeah.
That
was
really
helpful
and
just
like,
we
are
out
of
time
just
like
one
comment
from
the
product
side
to
the
discussions
that
is
happening
in
the
chat.
Definitely
we
kind
of
see
that
the
option
to
for
the
user
to
log
in
immediately
and
not
having
that
kind
of
extra
step
of
seeing
a
message
would
be
a
better
experience
and
like
seamless,
but
that
as
you've
seen
in
the
message,
chat
requires
more
work
from
our
side,
and
this
is
like
an
immediate
step
towards
that.
A
So
we
still
think
it's
better
to
have
that
indication
of
their
adding
to
wishlist
displayed
to
all
of
the
customers,
regardless
their
login
status,
rather
than
display
that
only
to
the
users
who
have
already
logged
in
so
there
are
other
features
in
magento
storefront.
That
would
require
users
to
log
in
like,
for
example,
additional
product
types.
Definitely,
some
of
those
require
users
to
be
logged
in.
A
Okay,
thank
you
guys.
That
was
like
a
lot
to
cover
within
30
minutes.
I
feel
as
if
it
was
a
productive
call.
So
hopefully
you
feel
the
same
and
have
a
good
rest
of
your
afternoon
and
the
day
talk
to
you
in
couple
of
weeks.