►
From YouTube: PWA Studio Community Sync 29 May, 2020
Description
New Venia Landing Page w/ Page Builder, Portals vs Modals, Upcoming Roadmap Priorities, Zetlen Sneaks
A
All
right,
hello,
everyone
happy
Friday,
welcome
to
another,
welcome
to
another
pwace
to
do
community
sync
meeting.
So
today
we
have
a
pretty
light
agenda,
but
we
have
a
couple
of
really
nice
demos
from
the
team.
We'll
do
a
quick
review
on
where
we're
at
with
the
roadmap,
some
of
the
upcoming
kind
of
priorities
for
the
team,
where
our
folks
will
be
over
the
next.
You
know
month
or
two
with
future
work
and
then
we'll
kind
of
open
up
to
anything
from
anyone
on
the
call
any
questions
and
we'll
wrap
from
there.
A
A
A
C
D
D
C
D
A
C
Right
cool
I
just
wanted
to
go
over
the
portal
component,
real
quick,
so
we
had
a
and
you
can
kind
of
read
along
I'm
talking,
but
we
had
a
modal
component.
That
was
really
just
creating
a
react
portal
and
would
give
it
like
a
default.
If
you
didn't
send
in
like
a
target
container
for
to
render
your
content
scene
and
so
as
we,
we
were
using
that
for
all
of
our
modal's
Oliver,
like
kind
of
slide
in
from
the
right
or
the
you
know,
on
desktop
when
it
pops
up
in
the
middle.
C
But
since
we
kind
of
standardized
those
into
the
dialog
component,
this
modal
component
that
actually
created
react
portals
was
confusing.
The
dialog
component
actually
has
like
a
modal
mode
that
you
can
set
it
to
you,
and
so
there
was
some
confusion
there,
and
so
what
this
PR
does
it's
pretty
far
along
in
the
pipeline?
It's
not
merged
yet,
but
probably
will
be
soon
it
just
renames
modal
they're,
two
portals
so
like
I
guess,
I
can
show
you
that
it
changes
and
so
most
of
the
good
stuff.
C
Sorry
we're
gonna
have
to
scroll
through
some
tests
and
stuff.
But
the
good
stuff
is
so
you
kind
of
see
here.
Modal
is
renamed,
moved
whatever
to
portal
and
I
just
updated.
You
know
some
of
the
internal
names
and
things
to
call
it
portal
from
now
on
and
then
what
happens
to
modal
since
it's
been
around
for
a
while
and
we're
not
sure
who
externally
is
using
it
in
their
own
projects.
Have
you
created
your
own?
C
You
know
react
portal
using
our
modal
component
as
we've
kind
of
kept
that
modal
acting
as
a
react
portal
for
now.
So
this
just
like
renames
re-exports
the
the
portal
component
and
calls
it
mogul,
so
your
stuff
will
keep
working
for
now.
We
did
add
this
kind
of
deprecation
notice
about
okay.
Ideally
we
get
rid
of
this
modal
component
entirely
or
we
mode
modal
component
could
like
compose
the
dialogue
component
in
in
its
modal
mode,
which
would
make
a
little
more
sense,
but
really
the
only
kind
of
that
would
be
a
breaking
change.
C
You
would
have
to
go
through
and
you
know
obviously
update
all
instances
of
modal
to
portal,
which
is
exactly
what
the
rest
of
this
PR
does
by
the
way.
Here's
one
example:
it
just
goes
through
and
every
everywhere
where
we
were
using
the
modal
component,
we're
now
using
the
portal
component.
It
does
read
a
little
bit
nicer,
it's
more
explicit
about.
What's
going
on,
there's
no
magic
like
this
modal
component
here
it
doesn't
actually
create
a
modal
for
you,
that's
all
like
done
by
the
modal
class
and
all
that
stuff.
C
So
it's
a
little
more
straightforward.
Now
you
know
you're
creating
a
portal
and
putting
some
content
inside
of
it.
That
is
pretty
much
the
extent
of
this
one
like
I,
said
I
think
the
highlights
are.
You
should
use
the
new
portal
component,
where
you
were
using
modal,
because
at
some
point
in
the
future
we
will
probably
change
our
modal
component
and
that'll
be
a
breaking
change
and
we'll
kind
of
highlight
it,
but
just
wanted
to
give
you
a
heads
up.
Oh
that
is
it
for
me.
B
A
C
Yeah
good
question
so
because
I'll
just
start
sharing
my
screen
again
because
modal
just
literally
re-exports
portal,
it
is
the
same
and
this
the
changes
that
you
see
in
this
file
are
really
just
changing
the
name
of
modal
to
portal.
It's
in
portal.
It
lives
in
portal
J.
Yes
now,
but
modal
just
reacts
ports
that
same
exact
thing,
so
they're
not
actually
two
different
components
right
now,
the
same
exact
thing,
but
yes,
the
API
service.
C
A
A
B
B
Right
so
this
is
veneer
dot,
Magento
com.
This
is
what
the
old
home
page
looks
like
everyone's
familiar
with
it
now
five
circles
that
we've
always
had.
This
was
essentially
always
a
to-do
page
for
us.
You
know
we
never
actually
designed
a
true
home
page
like
you'd,
have
on
those
sites,
and
so
we
just
kind
of
gave
ourselves
some
quick
links
to
the
categories,
but
what
we've
been
working
on
is
a
new
home
page
bill
with
page
builder.
B
B
B
F
B
B
B
So
page
builder
offers
some
of
the
common
components,
but
if
you're
familiar
with
PW
studio
right,
the
the
way
to
get
the
most
customization
possible
is
going
to
be
to
write
your
own
react
components.
Make
a
home
page
component
right
that'll,
give
you
full
control
to
let
you
write
optimal,
CSS
and
all
the
rest.
Exactly.
F
B
If
what
you're
looking
to
do
is
have
a
marketing
person
work
on
the
home
page
right,
someone
who's
not
going
to
be
familiar
with
reactant
and
such
then
page
builder
is
kind
of
our
suggested
way
to
do
that.
So
the
page,
while
building
is
more
for
non
developers
right
benefit,
then
for
developers
benefit
right.
If
you're
a
developer,
I
think
you
should
build
in
react,
you
don't
really
get
the
full
range
of
options.
B
Depending
on
what
you're
trying
to
I
know
what
you're
trying
to
serve
right,
if
you
need
people
to
edit
CMS
blocks
that
are
not
developers
and
you
want
those
updates
than
the
LS
your
option
for
sure
cool,
but
if
you're
a
developer
and
you're
building
your
own,
the
site
right,
you'll
always
have
more
power.
If
you're
not
working
through
any
sort
of
CMS
platform
right
working
right
through
the
JavaScript
and
CSS
yeah,
all
right
make
sense.
I.
H
Just
wanted
to
add
a
note
Jordan,
so
Scott
and
I
wanted
to
be
the
non-technical
people
that
worked
with
page
builder,
to
do
some
of
the
initial
work
on
this
home
page
and
I'd
like
to
share.
Maybe
a
couple
of
the
observations
we
made.
Even
for
somebody
non-technical,
the
amount
of
design
flexibility.
H
Page
builder
allows
you
is
limited
if
you
have
a
very
straightforward
layout,
where
there's
nothing
kind
of
laying
on
top
of
one
another
everything
just
Falls
neatly
into
a
grid,
one
under
the
other,
it's
possible
to
achieve
something
good,
but
if
not,
it
takes
kind
of
some
ramp
up
time
for
us
to
figure
out
how
to
achieve
that.
I
mean
Scott
finally
resorted
to
the
blocks
where
he
was
able
to
kind
of
approximate
the
design
but
I
think
once
Jimmy
started
working
on
it.
H
A
lot
of
that
had
to
be
stripped
out
in
order
to
truly
achieve
the
design
that
we
wanted.
So
that
is
something
to
keep
in
mind
if
using
page
builder,
to
construct
a
design.
Is
that
it's
not
it's
not
as
sophisticated
as
you
know,
design
imagination
would
would
be
you'd
have
to
kind
of
pare
back
your
expectations
on
what
you
can
achieve.
Yeah
well,.
F
Yeah
I'm
still
a
bit
wondering
like
what
is
right
now,
if
you
need
to
create
a
custom
home
page
feed,
every
city
is
not
really
offering
something
for
community
versions
of
Magento.
Right,
like
you,
can
add
a
CMS
page,
but
you
still
have
to
do
a
lot
of
work
yourself,
instead
of
just
having
a
way
to
implement
a
banner
or
just
a
simple
product
block
like
you
were
doing,
regular,
which
enter
home
pages.
F
B
B
B
B
A
Yes,
I'd
say
I'd
say
that's,
definitely
something
like
you
know.
We
wouldn't
say
that
you
know
delivering
any
sort
of
kind
of
DMS,
page
or
home
page
experience
for
CD
is
off
the
table
right,
I.
Think
just
for
the
context
here.
You
know
we
delivered
the
page
builder
PWA
integration
and
at
the
beginning
of
the
year,
and
we
saw
a
clear
opportunity
here
of
where
we
wanted
to
improve
the
landing
page.
A
We
had
page
builder,
we
felt
we
could
do
it
with
relatively
little
developer
intervention,
as
saamiya
pointed
out
by
using
page
builder,
so
we
we
kind
of
like
jumped
on
that
opportunity
to
improve
the
landing
page
now
so
I'd
say
in
the
future.
Here,
like
you,
know,
there's
definitely
more
on
everything's
on
the
table
in
terms
of
evaluating
delivering
additional
content,
page
management
or
landing
page
experience
for
CG
or
whatever
the
case
might
be
right.
This
is
not
definitely
an
exclusive
like
this
is
the
only
way
we
will
do
landing
page.
A
A
We
will
talk
about
the
more
kind
of
text-based
roadmap
here
for
a
second,
so
at
a
high
level,
where
we're
at
today
with
PWA
studios.
Obviously,
here
in
q2,
we've
been
working
on
delivering
new
features
across
the
storefront,
specifically
with
the
cart
and
the
checkout
experience,
as
you
guys
have
seen
over
the
last
few
demos,
we've
made
some
significant
progress
in
those
areas.
You
know,
extensibility
is
something
that
has
landed
recently
with
the
from
from
mr.
Dylan
there
on
the
initial
framework
for
extensibility.
A
We've
done
project
scaffolding
that
earlier
this
year,
and
so
the
throughout
the
rest
of
this
quarter
were
really
focused
on
doing,
is
cleaning
up
and
finishing
out
the
rest
of
those
cart
and
check-out
experiences,
the
rest
of
those
kind
of
venue,
storefront
features
and
then
wrapping
that
up
and
moving
on
to
the
next
set
of
kind
of
feature
areas.
So
the
coming
up
next
are
the
mini,
cart
refactor.
A
So,
as
we've
talked
about
on
previous
calls,
we
did
we've
created,
created
a
new
cart
and
check-out
experience,
and
that
necessitates
us
to
go
back
into
the
the
existing
vania
mini
cart
kind
of
remove
those
checkout
flows
from
that
mini
cart,
make
it
a
true
mini
card
and
and
then
now
defer
or
you
know,
use
the
new
cart
and
checkout
experience.
So
that's
coming
up
next,
as
Jimmy
talks
about
on
his
on
his
demo,
so
we're
moving
into
the
new
kind
of
venya,
styling
and
venya
branding
and
venya
design.
A
So
there's
some
work
there
with
style
guide
with
redoing
the
the
venue
header
that
we
are
prioritizing
and
then
the
next
big
piece
of
feature
work
that
we
have
coming
is
my
account.
So
my
account,
the
team
has
just
recently
finished
kind
of
with
looking
at
all
the
designs,
doing,
story
decomposition
and
then
now
it's
stacked
up
and
our
backlog
to
pick
up
next,
my
account
is
a
wealth
of
features.
A
A
The
dressing
bugs
things
like
that,
so
that's
kind
of
a
high-level
look
at
hey
the
next
few
months
in
terms
of
feature
feature
focus
around
refactoring,
a
minicar,
the
style,
guide
and
kind
of
redesign
work.
My
account
and
then
kind
of
the
continued
focus
on
developer
experience
with
scaffolding
extensibility
and
then
the
quality,
improvement,
quality
and
performance
improvements.
So
any
questions
on
kind
of
what
we're
focused
on
next.
Our
comment:
you.
A
Sure
so
that's
a
great
question.
So,
with
my
account,
you
know
we
we've
definitely
and
I'll,
allow
you
know
I'll,
let
somebody
kind
of
jump
in
here
where
maybe
I
missed
speak,
but
we
started
off
with
a
course
feature:
parity
in
mine
and
looking
at
lumens
and
asking
ourselves
the
question.
Okay,
what
are
all
the
features
that
are
in
luma
and
now?
How
do
we
port
those
over
to
the
new
vania
experience?
I?
A
Think
initially,
what
we've
done
is
is
try
to
focus
on
what
we
feel
based
on
some
some
additional
research
and
some
analysis
that
we've
done
with
breaking
down
those
features
we
try
to.
We
try
to
prioritize
what
holds
the
highest
Shopper
value,
a
shock,
close
shopper
and
merchants
value
for
the
my
account
experience.
H
Thank
you
most
of
it.
I
think.
The
only
thing
worth
noting
is
that
illumise
kind
of
a
repository
of
both
b2c
and
b2b
kind
of
an
intersection
of
the
two
where
my
account
is
concerned-
and
one
thing
we've
tried
to
do-
is
draw
a
line
for
b2c
and
look
at
the
80/20
use
case
out
there
when
kind
of
deciding
what
to
do
in
this
first
phase.
Right.
H
Forgive
me
if
I'm
miss
peaking
here,
but
that
was
kind
of
the
discussion
we
have
had
on.
You
know
what
we
would
do
first.
In
my
accounts,
we
would
support
the
most
common
commonly
occurring
pieces
of
functionality
and
use
cases
both
based
on
looking
at
websites
out
there,
and
you
know
the
research
effort
that
Kathryn
and
Scott
had
run
last
month
to
validate
some
of
those
hypotheses
and
and
that's
kind
of
the
the
foundation
for
what
you
will
see
coming
up.
A
Also
so
we
definitely
welcome
the
feedback
you
know
I
have
to
a
bit
look
through
and
make
sure
that
all
of
our
public
facing
roadmaps
are
updated.
There's
of
course,
the
public
road
map
in
the
and
the
github
wiki,
as
well
as
some
of
these
slides
that
we
we
do
share
out.
So
if
you
have
questions
feel
free
to
reach
out
about
the
roadmap
specifically
or
any
of
the
team's
priorities.
A
H
E
More
asking
around
like
it'll,
be
implemented
in
a
similar
manner,
as
the
page
bill
was
implemented
as
multi
wish
list.
Is
a
commerce
only
feature
right,
so
you
like
base
wish
list.
Implementation
would
be
fully
featured
and
then,
if
they're
running
a
commerce
edition,
you
would
use
the
extensibility
framework
to
inject
in
the
multi
wishlist
functionality.
On
top
of
it
right.
A
Yeah
I'm
not
sure
we
thought
through
the
specific
implementation
details,
but
we
we
have
called
out
that
there
is
the
distinction
between
having
a
single
wish
list
and
then
multi
wishlist
functionality,
and
so,
as
we
move
forward
with
picking
that
up,
maybe
Jimmy
o'james.
You
guys
want
to
jump
in
on
how
we
plan
to
implement
but
I
think.
B
D
Ultimately,
we
will
move
away
from
the
EE
JSC
ejs
approach
in
our
core,
but
not
for
the
foreseeable
future.
It's
fairly
simple
to
understand,
going
forward.
I
think
we
may
end
up
lifting
that
concept
into
an
extension
or
we
may
end
up
adding
another
way
to
resolve
when
the
hundred
language
ento
instance
is
enterprise.
D
You
could
certainly
do
some
kind
of
graph.
Ql
is
sort
of
the
same
way
that
we
grab
other
site
info
at
Build
time.
You
could
also
kind
of
check
the
set
of
installed
modules,
it's
something
that
we've
been
discussing,
but
that's
not
something
that
we
want
to
go
for
right
now,
because
there's
the
deployment
questions
around
it,
but
we're
also
taking
suggestions.
D
E
That
account
for
things
like
a
lot
of
the
account
dashboard
is
configurable
in
the
system.
Config
in
Magento,
like
I,
can
enable
a
disable
multiple
wish
list.
I
can
enable
a
disk
disable
the
registry
or
accounts,
or
things
like
that.
We
may
be
planning
for
any
like
retrieving
any
of
that
configuration
stuff
I.
D
So
that's
part
of
the
basic
feature
set
and
mission
of
PW
studio
is
to
reflect
those
admin
side
configurations,
but
something
like
that
would
be
what
we
would
determine
it
at
run
time,
because
an
administrator
may
make
that
change
and
not
wanted
to
play
the
PWA
in
our
case,
I
think
we
just
want
to
make
sure
there
is
not
the,
but
we
want
to
make
sure
that
there's
not
a
circular
dependency
at
Build
time,
when
you're
figuring
out
what
modules
are
even
installed.
That's
the
E
and
C
ejs
distinction
the
stuff
you're
talking
about.
D
We
would
probably
resolve
client,
client-
or
maybe
you
know,
a
varnish
layer
for
a
given
query.
That
is
not
going
to
be
very
frequently
variant.
Then
it
would
have
cache
headers
so
that
you
know,
as
every
phone
comes
up
and
requests,
what
the
configuration
for
the
my
account
pages,
then
you
wouldn't
have
to
continue
to
go
back
to
origin
for
it.
But
in
general
things
like
that
we
would.
We
would
want
to
calculate
a
run
time.
A
Pretty
question
anything
else,
the
other
the
other
caveat
I'd
also
add,
as,
of
course,
our
roadmap
is
still
subject
to
change,
as
the
disclaimer
claim
that
the
set
at
the
bottom
right
we
are,
we
are
entering
a
phase
of
college.
Second,
we're
finalizing
second
half
planning,
so
there
are
still
some
moving
pieces
here,
I
think
even
on
that
roadmap
for
you,
you
saw
the
internationalization
was
pushed
further
out,
but
based
on
a
lot
of
the
effort
that
we
know
that
mr.
Brava
endure
who's.
Just
asking
all
those
great
questions
has
contributed
into
the
project.
A
We
believe
that
we'll
go
to
move
that
to
the
left,
as
well
as
some
of
the
other
pieces
there
so
subject
to
change
there.
But
of
course
the
the
main
priority
prioritization
and
feature
focus
around
mini
cart,
refactor
new,
my
account.
It's
all
still
hold
true
and
a
fairly
locked
into
what
we're
doing
next.
So,
okay,
great.
So
if
there
are
no
other
questions
here,
I
open
up
and
say
hey!
Do
we
have
any
questions
comments,
demos
from
anyone
on
the
line?
Jordan?
A
A
D
D
D
Interesting
though
I've
zoomed
in
that's
why
the
style
doesn't
look
good
whoops
there
we
go
now,
let's
go
to
a
blogpost,
URLs
working
contents
coming
in
there's
a
cousin
coming
from
boy
from
a
completely
different
graph,
QL
API.
Of
course
it's
coming
from
a
Content,
full
blog,
here's
how
we're
doing
it
in
our
PWA
studio
instance.
This
is
again
the
developer
equivalent
of
installing
a
module.
D
I
am
installing
my
experimental
module,
PWA
content,
full
blog
and
then
setting
the
endpoint
for
that
content
for
blog
and
then
at
that
point,
with
a
little
tweak
to
our
Apollo
adapter,
we
are
checking
to
see
whether
the
operation
that's
running
is
a
Content
folder
tis.
If
it's
a
query
that
starts
with
content
full
over
here
in
my
extension
implementation,
for
instance,
the
index
query
is
called
content,
will
index
query
little
hack,
but
it
works,
and
then,
if
it
is
content,
full
it'll
use
the
link
to
that
endpoint.
D
Otherwise,
it'll
use
the
regular
Apollo
link,
so
we
can
call
a
totally
different
graphic
UL
api
with
exactly
the
same
hooks
exactly
the
same.
Clients
no
duplication.
So
how
does
it
do
all
the
stuff
that
we
just
saw?
How
does
it
creates
this
page,
and
how
does
it
make
this
well
I
added
a
few
things
to
my
branch
of
PWA
studio
and
we
would
pair
the
branch
turn
into
a
pull
request
with
this
PWA
content.
Full
blog
example
experiments.
It
has
some
additional
interceptors
for
some
additional
hooks
targets.
D
This
is
saying:
let's
make
a
new
end
of
our
definition
for
the
endpoints.
Let's
make
sure
that
we
are
modules.
Let's
add
a
nav
item,
so
Nick
the
blog
that
a
couple
of
routes,
one
for
the
blog
index
and
one
for
the
blog
with
slug
that
slug
parameter
gets
passed
in
this
is
for
development
stuff,
and
then
we
have
blog
j/s,
which
does
a
graph
QL
query
returns
blog
data
from
the
graph,
QL
query
and
then
blog
post,
which
pulls
out
the
slug.
Just
like
you
pull
out
any
other
URL
parameter.
D
G
F
D
I
wanted
to
show
you
guys,
because
again,
community
sync
and
have
a
little
preview
as
a
treat,
but
I
I
don't
have
this
code
public.
Yet,
however,
it's
it's
intended
to
be
interesting,
better
documented,
that's
it!
This
is
the
way
that
you
start
integrating
and
syndicating
other
things
that
appear
to
all
be
part
of
the
same
graph.
You
all
again
question.
G
D
The
plan
is
to
do
it
very
basically
and
simply
by
looking
at-
and
this
is
what
we
do
today
by
looking
at
the
package.json
set
of
dependencies.
So
in
this
case
our
build
bus
always
looks
at
what
project
is
being
built,
its
venía
and
it
looks
in
the
package
for
dev
dependencies
and
dependencies,
and
in
this
case
it
sees,
for
instance,
that
we
have
page
builder
as
a
dependency.
D
So
that's
how
it
finds
and
installs
page
builders
targets
and
when
you
add
another
dependency
like
if
I
added
you
know
magic,
sorry,
Magento,
research,
PWA
content,
full
blog
Yan
would
complain
because
this
module
isn't
published
and
it
doesn't
exist.
So
I
thought.
Well,
that's
a
downside
of
using
package.json,
but
I
still
want
to
use
package.json,
because
it's
so
simple.
So
what
I
did
was
make
this
exception
case,
for
if
you
want
to
test
out
a
module
without
actually
installing
it
or
it's
a
local
dev
thing.