►
From YouTube: PWA Studio Community Sync 10 July, 2020
Description
Joined by the team from DigitalSix to demo and discuss the recent launch of thewhiskybarrel.com and PWA Studio.
A
A
Obviously,
since
since
then,
you
guys
have
launched
the
site
get
get
you
guys
perspective
on
how
the
launch
went
things,
how
pwas
how
it
was
working
with
pwa
studio,
post,
launch
right,
and
so
I
think,
that'll
be
a
really
exciting
content
for
us
to
have
on
the
call
today
and
then.
Lastly,
I
think
we'll
we'll
cover
some
community
corner
kind
of
content
and
updates
and
then
we'll
wrap
from
there
so
quickly
I'll
turn
it
to
the
team.
A
B
So
spoken
to,
can
everyone
hear
me
first
I'll
check
you
cool
so
yep,
I'm
ewing,
technical
director
of
digital
six
and
we've
got
tony
mcall
and
yoda
on
the
line
as
well.
Who
were
the
the
developers
that
implemented
this
so
I'll?
Let
them
do
the
majority
of
the
talking,
because
I
can't
answer
most
of
the
questions
but
yeah.
We
recently
launched
our
first
pwa
studio
website
the
whiskey
barrel
and
then
so
yeah
I'm
going
to
hand
over
to
the
guys
to
talk
through
what
we
liked
about
it.
B
What
we
struggled
with
and
what
we're
looking
forward
to
with
obviously
2.4
is
going
to
be
a
big
change
for
ewa
studio,
with
the
amount
of
functionality
that
we're
going
to
be
working
there.
So
that's
definitely
something
we're
looking
forward
to
so
tony.
Do
you
want
to
go
first
and
maybe
talk
through
the
the
front
end.
B
C
C
B
C
D
A
B
Generally,
we
really
really
enjoyed
working
on
this
project.
It's
been
the
most
exciting
project,
we've
done
in
a
long
time,
probably
since
we
made
the
jump
to
magento
one
about
eight
years
ago.
So
it's
it's.
I
think
the
most
significant
change
in
how
we
work
since
then,
and
the
way
we
see
it,
we
we
are
going
to
hopefully
eventually
become
a
pure
pwa
studio.
B
We're
not
going
to
do
any
normal
magento
front
ends
anymore
in
the
long
run.
Obviously,
that's
we've
got
some
projects
which
are
using
traditional
magento
2
front
end
at
the
moment
which
we
will
have
to
complete,
but
going
forward.
Pwa
studio
is
going
to
be
our
primary
choice
for
any
any
future
projects
unless
there's
a
really
good
reason
to
not
use
pwa
studio.
E
C
B
E
C
Yeah
another
the
thing
was
turned
out
quite
useful,
using
it
like
using
video
studio
with
prismic
and
magenta
is
that
we
could
set
toggles
quite
easily
in
prismic
to
like
change
templates,
because
even
on
category
pages
like
this,
quite
a
lot
of
content
comes
from
frisbee
but
yeah
that
let's
change
templates
really
easily.
So
we
could
yeah
so
there's
lots
of
like
toggles
in
the
back
end
of
that
which
will
because
they've
got
a
few
categories
like
that
they
like
to
display
differently
something
like
independent
bottlers.
C
This
yeah,
for
example,
has
the
logos
on
category
london
and
then
we've
got.
You
know
traffic,
which
is
the
other
one.
Maybe
it's
exclusives,
that's
a
standard
category
page
for
you,
some
things
we've
kept
quite
similar
to
the
default
pdf
studio
and
the
layouts
filters
have
on
the
sidebar.
I've
already
been
scaled
up
brown
eyes.
Also.
We
switched
which
side
to
make
it
a
bit
more
consistent
and
I'll
just
run
through
the
product
and
that's
cats.
C
C
F
C
There
isn't
any
feature
for
actually
resetting
passwords
on
accounts,
and
so
we
had
to
build
in
like
functionality
for
that
and
which
I'm
sure
yoda
will
talk
about
more
because
he
had
a
big
role
in
that.
But
there
was
some
issues
we
ran
into
it.
Didn't
like
the
admin
area
didn't
like
using
different,
my
urls
that.
E
C
E
We
had
to
basically
build
a,
I
say
we,
I
had
to
build
a
lot
of
the
graphql
just
to
fill
out
bits
that
didn't
exist
like
resetting
passwords,
adding
extra
data
for
orders
we
actually
built
in
all
the
history.
They
were
still
working
on
that
the
gift
for
app
functionality,
it's
in
commerce,
but
it's
not
an
open
source.
So
I
had
to
build
that
as
well.
We're
currently
working
on
git
messaging,
because
that's
again
not
something
supported
in
the
graphql
yet,
but
we're
just
about
getting
that
good
sorted
out.
E
E
Magenta
always
wants
to
return
the
back-end
url,
which
is
not
the
front-end
urls.
We
had
to
use
the
customer
url
hack
to
make
that
work,
so
we
can
actually
pretend
that
urls
and
then
we
had
an
issue
where,
because
there's
a
bug
in
magento
it
would
always
try
and
send
you
back
to
the
pwa
when
you
saved
products
and
there's
just
a
lot
of
niggling
things
and
it
basically
doesn't
handle
being
on
two
different
urls
very
well.
E
It
was
just
a
headache.
It
took
about
two
weeks
to
sort
that
out
back
and
forth
larger
than
that.
It's
not
being
huge.
Today
is,
let's
say
it's
just
missing:
functionality
sending
emails,
resetting
passwords,
dipping
estimates,
gift
messages,
block
alerts,
nothing
huge
other
than
custom
attributes.
We
had
to
build
in
functionality
to
actually
allow
custom
attributes
and
products
that
come
through,
because
a
lot
of
them
are
drop-down
values.
E
C
So
yeah
in
general,
yoda
experienced
a
lot
of
questions
from
me:
macau
going.
Why
isn't
this
working
or
why
can't
we
get
this?
And
then
you
had
made
it
work,
so
we
could
actually
access
the
data
we
needed
and
yeah
the
product
attributes.
One
is
is
a
good
example,
because
yeah
we
were
just
getting
the
id
my
values
which
by
itself
isn't
particularly
useful
on
the
front
end.
E
Yeah,
the
other
one
we
had
issues
with
was
the
wizard
ones
because
they
came
through
unformatted,
so
you'd
get
all
of
the
wysiwyg
tags
for
media
url.
I
think,
and
not
an
actual
url
for
the
image
we
had
to
build
the
formatter
to
like
get
that
to
actually
come
in
before
it
goes
out
to
the
product
as
well.
C
Yeah,
that
is
a
a
good
example
which
yeah
we
encountered
that
when
we
were
just
trying
to
add,
I
think
we're
actually
just
trying
to
add
an
image
section
is
like
a
product
attribute
for
the
like
an
extra
section
on
the
description
yeah
and
we
encountered
killed
that
issue.
Michalis.
Is
there
anything
you
want
to
go
through.
F
Yeah,
thank
you
very
much.
Hi,
I'm
michael
and
or
mikhail,
and
I've
been
working
mainly
on
on
the
pwa
front
end,
and
it's
been
really
interesting
to
work
on
this
project,
as
we
have
learned
a
lot
of
new
things,
and
this
project
is
really
big.
So
so
we
have
gained
a
lot
of
new
knowledge
and
we
are
really
really
happy
to.
F
I
think
when
we
use
the
pwa
studio.
It
helped
us
a
lot
because
because
some
of
the
functionality
was
already
implemented
in
the
pwi
studio,
so
it
definitely
saved
us
some
time
and
other
than
that
we
had
just
some
of
the
things
just
just
needed
some
some
implementation,
but
it
really
helped
a
lot
and
for
the
future
projects
don't
like
to
integrate
typescript
and
to
help
us
it
would
be
the
stability
of
the
pwa
and
definitely
we
would
like
to
get
more
testing
done.
B
Yeah
yeah,
so
we
now
have
a
php
version
of
that,
but
yeah.
So
I
am.
I
don't.
I
can't
think
of
any
other
major
issues
we
experienced.
I
mean
there's
a
lot
of
learning
involved,
but
we've
we've
got.
We've
got
another
pwa
studio
project
on
the
go
at
the
moment,
so
we're
don't
know
when
that'll
be
launching
just
because
of
the
size
of
the
project,
but
we
will
keep
you
updated
on
on
our
developments
with
that
and
probably
have
some
questions
for
you
guys
as
well.
E
G
E
G
E
B
G
You
need
the
mailbox
for
yeah.
Absolutely
I
mean
you
can
ship
all
sorts
of
things.
I
do
have
questions,
but
historically
I
have
been
able
to
easily
take
up
everyone's
question
time,
so
I
want
to
leave
it
to
the
end.
If
someone
else
has
a
burning
question
about
what
they've
just
seen,
I
I'll
just
say
if
I
don't
get
the
chance
to
ask
mine
that
this
was
amazing,
it
was
the
most
impressive
by
far
pwa
studio,
visual
and
personal
experience
that
I
had
had
seen
thus
far,
and
I
was
thrilled
to
see
it.
H
Thank
you,
yeah,
I'm
gonna,
I'm
gonna
chime
in
just
really
briefly.
So
this
is
this
is
craig
herdman,
the
manager
of
pwa
studio
and
sorry
spongebob
might
be
playing
in
the
background.
I
can't
I
can't
hear
it.
It's
not
so
yeah
this
this
was,
you
know
the
most
impressive
pwa
studio
demo
that
I've
seen
not
to
disparage
the
other
ones,
but
I
think
we've
seen
an
evolution
over
time
as
pwa
studio
has
evolved
and
the
quality
of
the
various
sites
that
we're
beginning
to
see.
I
love
it.
H
I
I
have
it
installed
to
my
phone.
I
can
pull
it
up,
it's
fantastic!
It's
it's!
It's
incredibly
responsive!
There's!
You
know,
as
evelyn
mentioned
it's
very
visually
stunning
and
and
it
flows
well,
and
I
have
yet
to
run
into
a
single
issue
as
I've
been
navigating
around
the
site.
So
well
done.
I
parade
it
around
to
my
friends
and
it's
it's
an
amazing
site.
So,
pat
yourselves
on
the
back,
and
we
really
appreciate
the
feedback
that
you've
been
giving
us
about
the
about
the
experience.
B
A
I
I
just
have
a
quick
question.
As
far
as
I
mean
it
is
a
very
nice
website.
It
has
a
lot
of
functionality
in
it.
I
was
wondering:
do
you
have
to
leverage
rest
apis
for
some
of
that
functionality?
How
much?
How
much
do
you
get
out
of
the
box
of
how
much
do
you
have
to
customize
in
your
code
or-
or
I
don't
wanna
say
hack
around,
but
that's
a
lot
of
what
we
do
as
developer?
E
Quite
a
bit
so,
like
I
said,
we've
got
a
lot
of
things
that
we've
had
to
hack
around.
Mostly
it's
just
missing
functionality
blows
it
so
we've
had
to
add
in
stuff
for
getting
shipping
estimates
or
getting
country
names,
resetting
passwords,
sending
emails
for
a
contact
form,
adding
addresses
and
items
to
all
the
histories,
adding
gift
messages.
E
E
E
Okay,
so
we've
done
the
same
for
custom
attributes,
product
alerts.
Changing
we
had
some
issues
with
changing
store,
ids,
because
it's
a
multi-store
site.
We
had
to
do
some
functionality
as
well.
That's
the
majority
of
the
stuff
we
did
for
default
magento,
because
I've
kind
of
got
separated
out.
We
had
to
make
some
modifications
to
some
other
modules,
third
party
ones,
so
a
master
gip
and
brightpearl
modules.
We
had
to
adapt
to
actually
add
in
some
graphql
functionality
because
they
didn't
have
any.
I
E
I
mean
I
like
both,
so
I'm
actually
finding
myself
in
a
bit
of
an
interesting
situation
at
the
moment,
because
traditionally
I've
been
building
things.
I've
been
building
up
the
back
end
because
I'm
a
back-end
developer
and
they're
building
the
front-end
functionality
for
the
front-end
guys
to
come
in
and
finish
up
and
dial
and
make
it
all
look
pretty
and
work
nice
and
now
what
it
is
is
I'm
basically
just
patching
magento
make
it
work
the
way
it
needs
to
so
they
can
make
it
look
pretty
do
all
the
front
and
functionality.
E
I
think
it
was
probably
trickiest
the
first
couple
of
ones
I
did,
but
I
was
still
trying
to
get
my
head
around
how
it
worked
by
the
end
of
the
project.
If
we
needed
a
new
bit
of
graphql
functionality,
I
could
punch
out
in
a
couple
hours.
It
was
like,
depending
what
it
was.
Some
things
was
like
really
quick
and
a
bit,
so
it's
just
it'd
give
me
a
couple
hours
and
I'll
source
the
magenta
functionality
and
bring
it
out
into
graphql.
E
It's
where
possible.
I
didn't
want
to
write
new
functionality.
I
just
wanted
to
use
these
as
seen
magenta
functionality,
so
it
was
a
lot
of
figuring
out
how
it
worked
and
then
how
to
incorporate
the
graphql
into
it,
because
I
didn't
really
want
to
be
rewriting
the
wheel
when
I
could
just
use
what
was
already
there.
B
Yeah
we
are
going
to
have
to
give
things
with
2.4,
because
we've
written
a
lot
of
functionality.
That's
now
going
to
be
available
in
2.4,
so
or,
and
the
latest
pwa
studio.
So
things
like
the
account
area.
We're
gonna
have
to
work
out
how
we
we
do
that,
because
going
forward
we'd
like
to
use
the
magento
functionality
rather
than
our
own,
so
it's
getting
updated.
So
that's
gonna,
be
your
factor.
E
A
That's
a
that's.
A
really
important
point
right
is
that
every
major
release
that
we
have,
whether
it's
the
majestic
core
release,
will
release
an
additional
graphql
coverage
right
or
pw
studio
releases,
we're
releasing
additional
functionality
with
carton
checkout
recently
and
now
we're
moving
into
my
account
right,
like
every
release
that
that
we
push,
fortunately,
is
helping
with
that
story
of
requiring
customization
in
areas
where
there
are
gaps
right
so
that
that
we
should
tighten
that
up
over
time
and
by
this
time
next
year.
Right.
A
Obviously,
if
you're
working
from
newer
versions
of
pws
studio
that
that
problem
shouldn't
exist,
but
it
is
a
reality
that
teams
have
to
face
today
and-
and
you
guys,
like
you,
tackled
it
head-on
and
in
the
end,
I
think
it
is
a
customization
requirement,
but
something
that,
as
you
would
have
said
right
by
now,
he
can
kind
of
do
some
of
those
graphql
extensions
in
a
couple
hours.
So,
of
course,
we're
closing
that
gap.
But
I'm
happy
that
you
guys
were
able
to
kind
of
work
through
that.
A
F
Future
yeah,
I
think
the
the
graphql
documentation
was
very
useful
for
us,
and
you
know
everything
described
in
in
the
documentation.
Work
pretty
well,
and
probably
we
had
some
issues
with
with
like
a
server-side
rendering
or
switching
the
stores.
So
probably
that's
something
we
will
like
that's
something
we've
had
found
in
the
documentation
and
probably
it
will
be
great
to
have
and
but
other
than
that
the
documentation
worked
really
well
for
us.
C
Yeah,
I
definitely
agree
with
michael
on
that
it
was
a
really
good
reference
and
it
pretty
much
had
everything
we
needed
that
and
it
was
easy
to
read
yeah.
It
was
well
documented
in
the
media.
I
was
looking
looking
to
be
and
it
seems
like
there's
some
of
the
webpack
configuration
documentations
up
there.
So.
G
G
B
For
this
specific
project,
we've
got
so
we've
got
the
magento
admin
running
on
a
separate
domain
and
then
there's
a
single
store.
Well,
no
there's
multiple
store
fronts,
but
they're
all
on
the
same
domain,
so
it
just
changes
the
currency,
but
we
did
have
so
that
the
the
reason
well.
This
is
why
it's
to
run
the
general
on
one
port
and
the
pwa
on
the
different
ports.
So
that
was
the
easy,
the
easiest
setup
to
get
the
admin
panel.
The
standard
magento
running.
B
B
E
Right
the
real
issues
we
had
were
in
the
the
url
resolver.
It
doesn't
do
very
well
with
when
you
actually
have
different
admin
and
front-end
urls,
so
it
was
throwing
a
lot
of
wrong
urls
and
then
errors,
just
in
trying
to
bridge
the
fact
that
there
was
a
different
domain
for
the
front
end
in
the
back
end.
We
did
eventually
resolve
it.
G
C
Would
some
some
existing
modules
were
quite
easy
to
adapt?
We
ended
up
keeping
like
the
overall
structure
with
them
in
like
there's
things
like
indexed
css
with
like
which
has
like
all
the
variables
in
and
kind
of
right,
some
more
global
styles.
We
ended
up
keeping
that
that's,
probably
something
where
we
won't
be
keeping
in
the
future
like
it
way
in
the
next,
the
next,
the
next
project.
We
do
so
well
we're
planning
to
just
switch
it
completely
to
sas
variables.
C
Quicker
because
some
yes
at
some
sections
like
it,
it
was
hard
to
really
keep
keep
it
keep
them
how
they
were
using
the
stuff
like
the
way
it
was
set
up
with
the
styles.
For
that,
so
we
ended
up
just
taking
maybe
like
some
functionality
and
then
just
starting
from
scratch
on
quite
a
few
of
them.
Okay
and
yes
time,
we
just
returned
the
actual
functionality
in
components
and
a
lot
of
times
that
just
image
scratched
a
lot
of
css.
C
In
in
general,
yeah
yeah,
in
fact,
in
general,
we
used
a
lot
of
those
as
they
were,
but
there
were
certain
things
and
that
we
ended
up
end
up
having
to
alter.
I
can't
think
of
there's
one
like
one
in
particular,
but
I
just
like
it's
not
coming
to
me
and
but
overall
yeah
and
there
was
exceptions,
but
there
are,
I
think
they
always
will
be
exceptions
and
because
every
site
has
a
different
use
case,
but
yeah
overall,
yes,
mccann
might
be
able
to
expand
more
on
that
as
well.
G
Okay:
okay,
that's
I'm
interested
in
the
google
tracking
part,
but
that
would
get
into
some
details.
Interesting!
Well,
there's
a
lot
more!
I
could
ask
I
I
mean
I
don't
want
to
grill
you,
but
you
guys
are
part
of
the
community
engineering
slack.
So
you
are
right:
yeah,
yeah,
okay!
Well,
then,
yeah
I'd
be
interested.
E
A
Yeah
thanks
guys
for
joining
today
again
on
for
another
demo,
and
thanks
for
sharing
your
project
and
of
course,
we
look
forward
to
continue
to
to
chat
with
you
guys
and
yeah
get
feedback
from
you
guys.
You
know
we
look
forward
to
your
blog
post
right,
and
so
we
look
forward
to
more
more
exciting
projects
from
you
guys
in
the
future.
Okay.
Moving
on,
I
think
the
only
thing
we
have
to
do
is
cover
kind
of
community
corner.
A
J
J
All
right
so
for
anybody
not
familiar,
if
you
go
to
our
repo
and
are
looking
for
community
work,
we
have
this
project
board
called
community
backlog
with
prioritized
things
in
it.
We've
been
working
tirelessly
to
try
to
fill
prioritize
items
into
this
board,
so
a
lot
of
them
have
a
lot
of
detail
in
them.
A
lot
of
guidance
from
architecture
and
team
leads,
and
really
just
looking
for.
If
you're
looking
for
anything
to
work
on
to
help
contribute
to
the
project.
J
J
I
think
the
guys
here
that
just
showed
whiskey
barrel
mentioned
that
this
was
a
gap
in
coverage.
It's
now
available,
so
using
graphql
you
can
send
a
mutation
to
get
a
to
request
a
token
be
emailed
to
that
user.
That
user
takes
that
token
insert
enters
it
back
into
the
pwa
to
send
another
mutation
to
reset
their
password
that
resets
their
password.
They
can
now
log
in
again
previously
there's
just
nothing
you
could
do.
J
J
The
ui
is
kind
of
there
already,
so
there
shouldn't
be
a
lot
of
like
ui
work.
So
that's
if
kind
of
building
ui
is
something
that
you're
adverse
to
this.
This
is
kind
of
like
more
kind
of
back-end
front-end
work
where
you're
just
interfacing
with
graphql
and
sending
off
the
correct
requests
and
then
validating
them.
So
if
you're
looking
for
work,
this
is
a
great
one.
J
It's
flagged
for
our
8.0
release.
If
that
turns
out
to
be
what
is
actually
the
release,
there's
some
other
good
ones
in
here
you're
on
windows,
there's
some
docker
issues
that
some
people
have
encountered.
So
we
don't
operate
a
lot
on
windows
internally,
so
community
help
in
that
front
would
be
greatly
appreciated.
J
A
Anything
else
you
want
to
add
andrew
yeah.
The
other
thing
here
is
that,
of
course,
tommy
has
spent
a
lot
of
time,
making
sure
that
our
issues
that
are
on
our
board
are
properly
tagged
with
priority
severity
as
well
as
well
as
award
categories
right.
So
if
you've
been
involved
with
community
and
are
used
to
seeing
points
get
distributed
for
contribution.