►
From YouTube: Magento PWA Community Meeting, 4 January 2019
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
Excellent,
so
let's
go
and
get
started
here,
so
I
I
promised
a
little
bit
of
a
change
of
pace
if
you
paid
attention
and
slack
in
in
Twitter
on
kind
of
the
format
of
the
meeting,
and
so
one
of
the
things
I
think
Alexander
will
will
appreciate.
This
is,
from
a
community
standpoint,
one
to
be
a
little
bit
more
consistent
and
how
grooming
demos
things
like
that
can
be
managed,
and
so
the
agenda
for
today
is
really
gonna
be
more
about
a
year.
A
You
know
really
gonna
just
talk
about
what's
next,
and
so
so
the
spirit
of
this
really
doesn't
change.
In
many
ways
our
grooming
was
what
was
a
culmination
of
things
that
were
pre,
groomed,
anyways
and
but
really
looking
at
ways
to
accelerate
and
scale
where
we
started
off
with
2018
and
then
that's
gonna
be
a
big
part
of
we're
going
to
talk
about
today.
A
We're
also
gonna
get
some
upward
updates,
and
so
James
and
team
have
been
extremely
busy
with
that
with
several
others
who
recently
joined
us
on
some
updates
to
upward,
and
so
specifically
around
PHP
cloud
enablement
and
some
performance
updates.
That
I
think
will
really
really
play
well
into
to
to
things
like
lighthouse
cores,
but
also
you
know
what
would
be
expected
from
a
high-performance
PWA,
and
so
so
with
that.
A
So,
let's,
let's
kind
of
go
through
that
go
through
some
of
those
introductions
and
then,
of
course,
at
the
end,
will
will
save
some
time
to
talk
a
little
about
that
blog,
any
specific
items
there,
because
we
do
want
to
talk
through
any
questions,
really
leave
it.
Some
more
open
ours,
I'm,
sorry
office
hours
and
then
Q&A
at
the
end,
so
I
began
a
new
year
new
faces
for
repeat
for
PW,
and
so
just
a
couple
of
couple
team
announcements
here
and
so
from
a
product
standpoint.
A
Those
who
probably
seemed
had
seen
his
name
on
slack
and
github
and
others,
and
so
want
to
do
a
couple
of
introductions
here
so
Andrew
will
Cox
joins
us
from
from
bizarre
voice.
He's
actually
been
involved.
You've
been
involved
for
the
past
the
past
month
or
two
shadowing
everything
going
into
the
two
that
three
release,
but
he's
gonna,
be
helping
me
from
a
product
side,
really
really
shape
up
and
drive.
Now
that
we're
a
fully
you
know
fully
staff
fully
functional
team
across
what
you
see
is
a
lot
of
new
faces
in
engineering.
A
These
are
just
the
new
people
really
in
the
last
month
or
two
they're
gonna
give
us,
you
know,
give
us
what
we
need
to
do
to
accelerate
whether
it
be
venya.
Some
of
the
developer
experience
pieces
upward,
you
name
it,
and
so
a
lot
of
that
has
to
do
with
the
the
you
know.
The
people
really
here
on
the
call
that
helped
us
prove
the
concept
that
really
are
already
helping
us
in
the
community.
That
they're
also
then
allowing
us
to
work
on
some
of
the
big.
A
You
know
the
big
strategic
pieces
of
pita
way,
which
includes
things
like
payments
and
page
builder
and
and
other
aspects
like
that,
and
so
so
these
are
odds.
So
it's
really
just
again
to
hear
new
faces
here,
somewhat,
introduce
Andrew
and
then
kind
of
go
around
the
room
here.
We've
got
that
we've
got
Caden
I
believe
Craig
may
be,
may
have
a
conflict
but
kind
of
go
around
the
room,
just
wave
and
just
kind
of
just
introduce
yourself
and
maybe
maybe
something
maybe
a
fun
fact.
So
Dan
you
want
to
kick
kick
us
off.
A
B
Sharky
sharks
on
github,
if
you've
seen
some
stuff
on
there,
so
my
yeah
I'm,
coming
in
as
DevOps
and
looking
at
to
just
support
the
team
as
much
as
we
can
getting
into
a
really
good
CIC
flow
and
is
currently
working
on
getting
us
containerized
and
once
you
improve
our
infrastructure.
So
anything
cooling
related
any
kind
of
stuff
via
feedback
on.
Please
feel
free
to
reach
out
and,
of
course,
I'm.
A
I
believe
Craig
may
have
a
conflict
with
Craig
is
actually
our
engineering
manager,
and
so
he's
gonna
be
a
big
part
of
how
you
know
how
we've
got
here,
but
how
we're
going
so
he's
just
come
back
from
holidays.
He
supports
other
projects
than
PWA,
but
really
really
great
guy
who
just
joined
us
in
the
past
couple
weeks
as
well,
and
so
I'll
keep
going
here
and
hit
it
off
the
Steven
who
they
yeah.
D
D
A
A
A
Excellent
yeah
in
dangers
that
could
be
a
new
father
as
well,
and
so
that's
gonna
be
a
big
theme
for
the
team.
A
lot
of
babies.
Yes,
it
is.
It
was
part
of
the
interviewing
process,
excellent
so
and
then
India,
no
you're,
you're
you're
under
the
weather
and
so
I
feel
free
to
do
your
best
there
from
from
remote
that
usually
people
have
known
and
seen
you
but
probably
haven't
heard
from
you.
Yeah.
F
F
C
So
I
am
Tommy
full-stack
engineer
brought
on
to
help
out
with
the
upward
PHP
project,
but
I
have
also
written
a
few
lines
of
reacts
so
we'll
maybe
start
helping
out
on
the
front
end
front
as
well.
Once
upward
is
wrapped
here
in
a
few
weeks,
fun
fact
about
me:
I
am
a
a
nationally
right
ski
ballplayer,
so
watch
out
for
me
at
Chuck,
E
Cheese
we're
all
the
competitive
skee-ball.
It
happens,
Chucky
Cheese
I'm,
actually
a
national
champion.
I'm
Wow.
C
C
B
D
A
Good
we're
very
lean
for
very
long,
but
but
you
know
that's
that's
exciting,
so
well,
good.
In
the
time
you've
been
with
magenta
for
a
while
right,
I
mean
I'm
looking
around
the
room
new,
it's
kind
of
relative
two
years,
which
sounds
like
very
good
excellent
and
then
just
rounding
things
up.
We've
got,
we've
got
a
QA
QA
engineer
starting
next
week
as
well,
and
so,
as
you
can
see,
you
know,
depending
on
your
math,
because
we've
got
we've
had
quite
a
few
people
of
all
of
the
project.
A
So
so,
thank
you
so
welcome
up
welcoming
a
new
year
new
faces.
You've.
Probably
seen
some
names
here
wondered
who
they
are,
and
now
you
know-
and
everybody
here
is
based
in
unless
on
this
slide
is
based
in
Austin
here
all
right.
So
a
couple
process
updates
again
the
spirit
of
making
this
more
of
a
community
meeting
and
kind
of
getting
beyond
getting
beyond
grooming
and
making
that
more
of
a
dedicated
forum.
We've
moved
a
Kanban.
A
A
You
know
we're
watching
things
like
with
limits
and
others
were
things
like
reviews
and
others,
or
a
bit
and
catch-up
mode,
but
with
now
the
now
that
the
internal
focus
and
the
reviews
are
really
taking
shape,
I
think
we're
well
prepared
or
for
what
we
what
we
want
to
do
again,
whether
it
be
the
the
shopper,
experience,
developer
experience
and
then
the
upcoming
merchants
experience
as
we
start
to
plan
for
page
builder,
and
so
so.
That's
that
that's
that
and
so
you'll
see
a
lot.
So
what
does
that
mean
for
for
the
teams
here?
A
The
people
who
are
listening,
grooming
will
no
longer
carry
estimates
right.
Kanban
is
more
about
creating
a
work
that
is
similarly
sized,
so
we're
gonna
pay
the
special
thing
special
attention
to
that
also
means
that
we
are
gonna,
be
moving
away
from
again
this
the
notion
of
Sprint's,
but
we
will
have
regular
meetings
right
similar
to
how
this
is
being
done
within
MSI,
how
this
is
being
done
with
graph,
QL
and
other
projects,
and
so,
if
you
were
involved
in
multiple
Magento
community
projects,
this
should
be
familiar.
A
If
it's
not
keep
us
honest
from
that,
and
so
we
want
to
be
consistent
with
that,
and
so,
but
we
will
have
demos,
we
will
have
these
types
of
meetings
and
we
want
your
feedback.
This
community
really
has
a
has
an
ownership
of
where
we
want
to
go
with
this,
but
a
lot
of
the
grooming
that
we've
done
and
things
have.
It
was
really
just
pre
grooming
of
things
that
that
that
was
community
focused,
but
you
know:
we've
had
such
great
contribution
for
many
of
you
here.
A
People
were
saying:
hey
can
I
pick
up
ticket
numbers,
you
know
127,
and
they
said
yes,
this
makes
sense,
assign
it
and
go
you
don't
necessarily
need
a
meeting
for
that
and
if
there's
questions
or
ambiguity,
you
know
we're
always
available
to
address
any
of
that
as
they
as
they
come
forth.
But
now
that
we've
got
now
that
we've
got
a
lot
of
a
lot
of
depth
and
then
strike
here
on
the
team.
We're
gonna
be
able
to
go
fast,
you're
gonna
be
able
to
go
faster
well
beyond
venue.
A
I
started
to
get
into
things
like
the
components
which
I
know
is
a
big
big
effort
of
ours,
but
also
things
like
the
upward
PHP
project
and
the
work
that
that's
being
done
there.
The
past
couple
weeks,
which
which
James
will
talk
about
here
in
just
a
little
bit
so
that'll,
be
that'll,
be
a
big
of
a
bit
of
a
shift
which
may
be
familiar
for
those
who
are
other
other
other
Magento
projects.
That
should
be,
but
maybe
a
little
bit
of
a
shift
for
folks
here.
A
The
other
part
is
preparation
for
231,
and
so
as
much
as
you
know,
as
much
as
2
3
O's
out
as
it
seemed
and
5
by
many
as
a
success,
both
from
a
from
an
experienced
future
product
perspective
and
also
operational.
The
work
doesn't
stop
by
two
three
one.
What
it
would
it
means
to
us
has
a
lot
to
do
with
that
graph,
QL,
enablement,
and
so
so
folks,
like
Misha
and
others,
have
actually
put
together
a
really
nice.
A
A
really
nice
chart
on
the
types
of
enablers
where
it
means
and
what
it
means
to
PWA
really
continue
to
build
off
of
that.
A
lot
of
that
already
in
development.
A
lot
of
that
already
built
by
a
community
some
folks,
even
here
for
that,
and
so
we,
you
know
we're
keeping.
You
know
we're
keeping
focused
on
that
and
right
now
that
that
the
goal
for
that
is
really
the
first
quarter
of
this
year,
and
so
look
for
more
updates
to
that.
A
We
will
be
thinking
and
looking
more
towards
two
through
one,
but
also
covering
the
rest
fall
back
where,
where
that
doesn't
make
sense,
last
but
not
least
least,
is
Magento.
Events
you'll
start
to
see
a
different
focus
on
those,
as
we
start
to
plan
for
those
whether
they
be
the
meet
Magento
is
the
imagines
etc?
And
it's
really
gonna
be
more
about
empowering
the
developer
community
right.
We've
got
a
core
product
out
there.
We
hit
MVP,
but
look
for
workshops.
A
So,
just
a
just
a
quick
eye,
a
quick
reflection
on
your
interview
again
for
those
who
are
following
the
work,
that's
happening
in
potential,
it's
it's
pretty
dramatic
and
so
the
the
work
today
again
much
with
you
know
with
much
input
from
the
community.
Is
it
really
culminated
into
what
what
became
the
2.3
release
at
the
end
of
November
and
in
that
in
that,
as
many
of
you
know,
came
together
in
a
both
a
developer
experience
and
the
shopping
experience?
And
so
in
that
we
had
a
basic
experience.
A
We've
got
everything
from
from
home
all
the
way
to
a
basic
check
out
with
static
payment
methods
and
is
provided
as
a
foundation
for
for
for
where
we
want
to
go
and
in
many
ways
where
can
we
continue
to
add
to
that,
especially
with
some
of
the
recent
merges
on
search
that
both
Adrienne
and
the
bargaining
team
have
put
together,
and
so
we're
continuing
to
merge,
review
and
and
and
kind
of
work
past
a
lot
of
the
work
that's
there,
and
so
all
this
again
is.
That
is
a
direct
result
of
the
work
here.
A
All
the
result
of
the
work
is
a
direct
result
of
the
transparency
with
the
planning
and
the
roadmap
that
continues
to
evolve,
based
on
the
documentation
from
calculon
and
others
on
PW
Studio
IO.
But
again
the
work
is
not
done.
Some
of
the
twenty,
some
of
the
big
changes
in
2018
really
had
came
down
to
thinking.
What
graph
kill
not
only
is
an
enabler
but
not
no
longer
as
a
blocker,
and
so
for
those
who
are
who
new
to
the
project.
A
We
made
a
conscious
decision
to
it
to
use
as
much
rest
as
we
could,
especially
around
checkout,
that
will
get
better
in
Bakke
well
and
if
you
look
at
the
graph
you'll
coverage
again,
Misha
doesn't
much
better
job
of
this
in
the
in
the
roadmap
slide
for
graph,
QL
and
github.
A
lot
of
the
work
is
already
there.
A
It's
checked
in
there's
some
work
that
needs
to
be
done
around
payment
methods,
especially
around
credit
and
debit,
but
that
is
that
is
the
fast
follow
and
a
lot
of
that
work
is
being
done
by
the
community
and
and
is
going
to
be
marked
tested
and
reviewed
4-2-3-1.
So
as
we
as
we've
made
some
conscious
decisions
in
that
previous
slide
around
around
graph
QL
coverage
and
using
rest
as
a
fallback,
there
is
a
fast
following
that's
happening.
That's
gonna
enable
a
lot
of
these
key
experiences
that
you
see
here
that
we're
pretty
excited
about.
A
Now
me
and
others,
you
know
our
big
focus
as
we
look
at
2019
priorities
is
to
start
extending
in
those
areas,
especially
around
authentication,
especially
around
new
covered
Dharana
graph,
QL,
and
especially
around
areas
that
were
that
were
reserved
primarily
for
our
Magento
commerce,
flavor
of
the
of
the
product
itself,
and
so
you'll
see
a
lot
more
of
that
in
this
my
account
piece,
especially
around
gift
registry,
especially
around
around
some
of
the
the
other
aspects
of
the
project.
There
were
once
again
once
reserved
for
for
that.
A
So
that's
kind
of
2018.
In
a
nutshell,
I
I
made
a
conscious
decision
not
to
that's
a
necessarily
to
walk
you
through
all
the
other
stats
and
contention.
I've
shared
some
of
those
in
the
past,
but
it's
really
really
impressive.
You
can
see
a
tremendous
keep
happening
well
into
took
you
for
that.
You
know
was
often
it
was.
You
know
actually
done
with
without
even
the
help.
That's
recently
joined
that
and
the
help
is
really
going
to
help
us.
G
As
they're
kind
of
pointed
out
here
right
for
2019
right,
do
we
have
a
lot
of
there's
a
lot
of
things
going
on
for
for
the
team
over
here
right?
We
have
new
members,
we're
also
moving
to
combo.
So
there's
both
the
immediate
I
think
impact
of
that
in
terms
of
just
operational
impact.
Our
operational
cadence
things
like
that
things
that
are
changing
around
rooming
meetings
right.
G
The
the
community
meetings
so
well,
of
course,
be
transparent
about
all
those
changes
and
how
that's
going
to
impact
everyone
involved
and
I
think
it'll
all
be
for
the
better
right.
Obviously,
it
should
be
for
the
better
terms
of
our
long
term
parties
for
2019
right.
Nothing
is
changing
as
of
now
so
the
next
slide
right
now.
The
long
poles
in
the
tent
continue
to
be
a
completion
of
Enya
PW
historic
storefront
will
continuing
to
look
at
the
integration
with
page
builder.
G
The
next
slide
is
just
kind
of
a
cover,
a
review
of
exactly
what
is
already
outlined
on
the
wiki,
and
the
roadmap
right
is
mostly
to
say,
like
we're,
still
aligned
to
the
roadmap
as
we
continue
with
2019
planning
and
as
we
harden
kind
of
the
requirements
between
my
team
in
reference
to
those
three
items
in
the
previous
slide
right.
Those
will
obviously
have
impacts
on
the
roadmap
and
we'll
continue
to
update
that,
and
you
know,
that'll
stay
in
the
same
bat-time
same
bat-channel.
G
You
guys
go
to
the
same
reference
for
look
at
that
roadmap
again
will
be
transparent
and
communicate
all
of
those
changes.
So
a
lot
of
soft
talk
around
what's
coming
up
for
2019,
but
as
we
as
we
continue
to
you
know,
evolve
around
that
planning
again,
we'll
communicate
that
outward
upward
network
upward.
There.
A
G
A
That's
it
for
me,
yeah
perfect,
so,
let's
so,
let's
switch
gears,
then
to
upward
speaking
of
which,
and
so
I'd
asked,
is
James
to
talk
a
little
bit
about
some
of
the
some
of
the
great
work.
That's
happened
in
the
past
couple
weeks
without
from
Tommy,
been
in
others
on
really
the
cloud
deployment
piece,
but
also
some
of
the
image,
optimization
work
and
so
I
thought
it'd
be
worthwhile
kind
of
walking
through
that
and
having
James.
A
E
All
of
those
types
of
servers
are
still
going
to
produce
the
same
PWA
it's
going
to
be
based
on
venía.
It's
gonna
be
based
on
our
Paragon
components.
It's
going
to
be
built
with
our
our
build
pack
pipeline,
so
it's
going
to
rely
on
the
graph
QL
api's
and
on
the
rest
api's,
but
it
needs
to
be
rendered
from
an
application
shell.
E
So
what
we
came
up
with
in
lieu
of
rendering
it
from
the
Magento
theme
architecture,
which
you
know
that
had
some
serious
disadvantages
to
it-
is
to
create
a
middle
tier
specification
for
the
behavior
of
the
backend
for
front-end
that
serves
the
application
show
and
that
routes
requests
from
the
PWA
to
the
network,
and
that
thing
is
called
upward.
That
is
a
specification
for
a
simple
declarative
language
which
describes
the
things
that
the
middle
tier
should
do.
E
You
can
think
of
it
as
a
domain-specific
language
for
a
a
sane
and
reasonable
subset
of
the
things
that
a
web
server
is
supposed
to
do
just
optimized
for
the
things
that
PWA
really
needs
and
we
implemented
a
reference
client.
Sorry,
a
reference
server
implementation
for
upward,
called
upward
Jes
as
part
of
our
suite
of
applications
in
the
PWA
studio,
mono
repository,
but
we
always
intended
for
this
specification
to
be
implementable
in
other
languages,
for
flexibility
and,
of
course,
the
first
language
we
being
Magento
that
that
began
to
take
place
was
PHP.
E
This
is
gonna
help
us
tremendously,
because
our
cloud
environments
are
much
simpler
to
deploy
with
the
PHP.
Only
back-end,
and
many
of
the
scenarios
where
our
partners
and
sis
are
doing
deployments
are
also
much
much
simpler
scenarios
if
you
are
using
the
same
either
the
same
server
itself
or
container
or
the
same
template
or
image
to
spawn
multiple
containers
where
you
can
render
the
PWA
and
start
delivering
it
to
the
client,
with
a
PHP
only
back-end.
E
So
in
light
of
that,
our
internal
core
engineering
team
shifted
some
things
around
and
gave
us
two
senior
talented
PHP
and
full
stack
developers
in
the
form
of
Ben
Bachelet.
Who
is?
Is
he
here
he's
not
not?
Okay
and,
and
he
is
on
retainer
from
our
cloud
management
team
and
of
Tommy.
We
know
who
is
here:
wait
is
he
here.
E
Who
is
wet
together
with
been
taking
the
specification
that
we
have
written
in
the
repository
and
adapting
it
and
writing
a
PHP
server
for,
and
this
is
going
to
enable
a
single
Magento
installation
to
run
the
production
version
of
a
PWA.
The
up
word,
PHP
repository
is
currently
live
in
the
Magento
research
organization.
E
Right
now
we're
projecting
within
the
month
of
January,
and
then
at
that
point
it's
going
to
be
part
of
our
recommended
deployment
solution
for
board
up
work
now
part
of
the
process
of
making
up
word
available
to
other
runtimes
and
making
it
a
reasonable
and
feasible
way
to
deploy
a
PWA
is
adding
some
functionality
to
it.
So
upward
is
also
going
to
gain
some
default
best
practices
as
part
of
its
render
pipeline
up
to
and
including
compression
we've
been
asked
several
times
to
perhaps
use
more
advanced
content,
negotiation
and
more
advanced
algorithms.
E
It
alone,
though,
that
broadly
real-time
compression
can
save
up
to
75%
of
the
size
of
those
images
and
of
other
types
of
assets
that
nature
and
because
it's
a
CPU
bound
activity
and
that's
rarely
what's
causing
the
we
get
with
your
phones.
You
will
find
that
the
actual
time
to
first
interaction
response
is
going
to
improve
tremendously
as
a
result
of
that
addition
to
our
code
base,
which
is
almost
entirely
just
bringing
in
a
separate
library,
so
very
few
extra
lines
of
code
for
us
to
maintain
huge
advantages.
E
That's
going
to
come
in
soon,
but
at
the
same
time,
image
optimization
requires
a
degree
of
control
over
the
images
actual
dimensions
over
its
compression
over
its
format.
And
to
that
end,
we
are
adding
image
resizing
ability
to
the
to
the
upward
configuration
specifically
for
venía
the
catch
is
we're
not
going
to
add
it
to
upwards,
specifically,
at
least
at
this
time,
there's
already,
of
course,
an
upward
to
brewing
in
my
head.
E
But
for
now
what
we're
gonna
do
is
add,
just
a
simple
idea
to
upward,
where
it
can
forward
requests
based
on
rewriting
a
URL
and
then
issuing
a
302,
and
in
that
way
we
can
forward
any
image
requests
to
a
resizing
service
of
any
kind.
If
you
have
a
fastly
subscription
to
fastly
IO,
we're
gonna,
do
it
that
way?
If
you
don't,
then
we
can
either
use
a
feature
that
we're
going
to
add
to
the
node
development
server
or,
as
the
upward
PHP
team
is
working
on.
E
Maybe
somehow
leverage
this
built-in
image
optimization
functionality
in
Magento,
so
long
story,
short
upward,
is
expanding
dramatically
in
its
usability
and
in
its
usefulness
to
our
various
deployment
scenarios.
It's
now
going
to
run
on
two
different
language
runtimes,
but
with
identical
behavior,
we're
adding
a
lot
of
performance
optimization
to
its
default
pipeline
and
we're
going
to
give
you
the
ability
to
redirect
certain
types
of
requests
so
that
you
can
art
direct
and
further
optimize.
E
Your
images
super
exciting
stuff,
and,
judging
from
what
our
analytics
say
today,
that
alone
is
going
to
decrease
the
size
of
the
PWA
payloads
down
to
the
device
by
a
dramatic
amount
and
we'll
land
before
our
first
release
hoped
for
applause,
and
that's
it.
That's
the
update,
I
think
I
don't
have
diagrams
like
I
can
very
shortly
because
I'm
actually
putting
something
together
for
Adobe
tech
summit.
But
there
you
go
any
questions.
I
can
answer
Oh
first
question
I
just
want
to
get
out
ahead
of
this.
E
A
Anything
else
so
yeah,
thank
you,
James
for
walking
through
that.
That's
really
been
a
big
part.
I
know
what
you've
been
up
to
in
the
last
couple
weeks,
but
are
really
going
to
give
us
a
big.
A
big
lift
in
both
are
both
of
our
cloud
offerings,
but
also
the
performance
piece
as
well,
and
so
so
good
stuff
there.
So,
just
again
before
we
go
before
we
break
here,
just
kind
of
kicking
out
the
audience
any
other
questions
or
comments
before
we
have
before
you
break.
A
Okay,
well
very
good.
Well,
thank
you!
So
much
everybody,
as
always,
I
appreciate
your
help.
Your
help
and
support
throughout
all
this
again.
You
know
this.
This
meeting
series
will
continue
in
this
in
this
format
and
and
grooming
and
other
activities
will
be
done
asynchronously
and
in
in
in
and
will
be
done
in
a
much
more
much
more
nimble
format
and
so
you'll
see
a
lot
of
this
I
think
good
example
of
that
is
the
is
the
mini
cards
example
that
that
Adrienne
picked
up
where
it's
really
just
a
couple.
A
So
look
for
a
lot
of
those
types
of
things
as
the
team
gets
that
symbol
if
you're
looking
to
help
if
you're
looking
for
feedback
or
questions,
let
us
know-
and
so
we're
we're
going
to
show
this
mo
a
little
bit
if,
if
there's
feedback
about
it,
we'll
continue
to
adjust,
but
as
always
thank
you
again
for
your
time
have
a
great
rest
of
your
day
and
have
a
great
weekend.
Thank
you
much.
My.