►
From YouTube: Adobe Stock Integration public meeting, 27th May 2020
Description
Adobe Stock Integration public meeting, 27th May 2020
A
A
B
A
B
Yeah
so-
and
we
kind
of
agreed
to
have
very,
very
granular
and
it
approach
in
achieving
that
goal,
but
essentially
there
have
their
high
level
goal.
That
we
have
in
mind
is
enable
user
in
admin
panel.
Do
the
transformation,
was
images
and
create
transitions
and
assign
this
image
renditions
to
different
break
points
that
are
used
on
the
particular
website
and
the
way
they
can
share
their
roadmap?
B
It's
kind
of
big
long-term
goal
and
in
order
to
be
truly
agile,
we
agreed
to
split
that
face
into
smaller
little
iterations
within
the
face.
So
we
have
some
deliverable
functionality
after
each
iteration,
though
in
the
first
we
are
looking
at
the
face
5
at
the
moment.
So
within
this
first
iteration
it
will
be
possible
to.
B
Programmatically
without
user
input
generate
their
image
renditions
based
on
the
parameters
that
user
provided
in
a
configuration,
and
these
parameters
will
be
used
for
all
of
the
images
that
are
inserted
into
the
content.
So,
let's
say,
as
a
user
I
have
two
break
points
that
my
website
supports
and
I
want
to
use
on
my
desktop
break
point
images
with
no
more
than
100
1000,
60,
pixels
width
and
on
my
on
my
mobile
break,
would
I
want
to
use
images
no
more
than
let's
say:
1200.
B
Kind
of
process
the
images
and
compress
them
to
match
this
rule
that
user
provided
in
a
configuration.
So
when,
as
the
user
I
insert
the
image
into
the
content,
I
don't
need
to
specify
the
width
and
other
parameters
of
the
image.
I
just
insert
this
image
normally
as
I
used
to
before,
but
magenta
make
sure
that
this
is
an
image
that
is
optimized
to
the
certain
break
point
based
on
their
configuration
provided
previously.
A
B
B
B
B
More,
like
a
completion
of
the
media
gallery
basic
functionality
that
we
already
started
in
phase
3.
So
we
are
planning
to
add
various
features
listed
here,
but
the
main
goal
of
the
phase
4
is
provide
the
ability
for
the
user
in
the
media
gallery
to
find
assets
that
are
used
in
a
different
areas
of
Magento.
B
So,
let's
say
I
want
to
find
all
of
the
images
that
are
used
in
CMS
pages
or
I
want
to
find
images
are
used
in
CMS
pages
created
in
a
certain
period
of
time
or
I
want
to
find
images
on
CMS
pages
on
a
certain
store
view
was
that
there
will
be
ability
also
to
find
images
that
are
not.
They
are
not
that
not
used
anywhere.
B
A
By
the
way,
is
this
story
during
the
review
raised
the
most
questions?
Probably
the
stories
currently
see
on
the
two
stories
in
our
backlog.
That's
poor
block,
dynamic
blocks
and
four
pages
I
was
supposed
to
cover
the
catalog
content.
Part
as
well.
I
mean
the
categories.
Products
are
that's
for
Hydra.
B
For
four
products
we
can
cover
on
there
like
a
Content
area
again
right,
because
busy
week
can
be
used
only
in
I
mean
this
week.
Images
can
be
used
only
in
the
content
section
of
the
image.
That's
why
I
kind
of
prioritized
at
lower,
but
we
can
discuss
that
because
I
see
that,
like
lifestyle
images
are
used
much
less
in
the
product
content
versus
the
CMS
area.
So
that's
why
it's
more
important
to
focus
on
demise
area
first
and
add
their
brought
that
catalog
area
support
later
but
I
believe
on
a
road
map.
B
A
Kent
Street,
but
anyway,
I
I,
agree
that
probably
the
CMS
is
the
media
gallery
from
CMS
and
it
is
are
used
much
more
so
that
we
should
focus
on
that.
One
first,
okay-
and
here
listen-
is
that
this
filter
looks
to
be
quite
complicated.
I
mean
that,
from
the
acceptance
criteria
criteria
we
can
see
that
the
user
should
be
able
to
filter
first
to
be
able
to
filter
by
the
product
by
the
entity,
type
of
the
same
as
like
lock,
a
dynamic
block,
page
and
so
on.
But.
B
B
A
For
dynamic
locks,
right
and
yeah,
and
basically
that's
it-
that's
why
it
was
really
hard
to
understand
how
we
can
process
that,
like
what
conditions
can
we
get
in
the
result
and
how
it
will
look
on
the
front
end?
First
of
all
how
this
filter
is
going
to
look
on
the
front
end.
Basically,
I
can
imagine
that
selecting
the
blocks
like
having
the
multi
select,
drop-down
four
blocks
pages
and
then
as
trying
to
find
the
specific
book
by
its
name
as
a
sub-item
on
this
block
selection,
but
it
becomes
more
complicated.
A
B
A
B
Type
of
the
field
from
certain
entity
like,
for
example,
CMS,
page
or
dynamic,
block
and
I
know
I
know
that,
like
from
the
technical
perspective,
it
might
be
challenging.
So
we
can
discuss
that
because
the
way
how
we
associate
certain
entity
to
the
store
view
happens
differently
on
dynamic
blocks,
for
example
and
pages.
So
maybe
we
can't
align
that
type
of
the
filter,
so
yeah
I
mean
the
goal
is
to
make
it
as
flexible
as
possible
and
so
that
the
fields
are
not
dependent
on
the
entity
type
that
users
directed.
B
A
B
A
A
B
D
Is
just
a
very
quick
mock-up,
so
basically
we
will
have
maybe
some
sort
of
like
a
first
component,
that
you
can
select
entities
that
use
products
categories
and
it's
a
multi-select,
and
once
you
select
that
it's
already
applies
the
filter.
So
it
shows
all
the
images
in
products
and
categories,
but
it
also
adds
two
additional
or
whatever
additional
number
of
dropdowns
needed
to
refine
third
or
by
category
or
product.
If
people
want
to
do
that,
so
it's
additional
filter
and
maybe
we
can
have
a
additional
filter
for
store
views
or
whatever.
D
So
since
that
is
a
separate
thing
right,
we
have
an
T
and
it
is
like
product
category,
CMS
pages
blogs,
dynamic
blocks
and
further
kind
of
like
those
can
be
applied
to
store
use
or
whatever.
So
that
can
be
a
separate
control,
and
here
you
can
select
either
all
or
you
can
select
as
multi
selective,
individual
stores
store
views
or
whatever.
So
that's
can
be
so
again,
two
controls,
but
this
control
is
a
compound
one
that
adds
additional
controls.
If
you
selected
entities
specific
to
that,
what
do
you
think
is?
D
B
C
Also
I
would
like
to
see
something
that
would
cover,
for
example,
select
assets
used
on
product,
a
B
and
C,
for
example,
that
you
would
select
on
that
select
box
there,
but
it
wouldn't
cover
cases
where
it
is
described
on
the
septons
criteria
like
if
the
block
is
enabled
or
block
is
disabled
and
cover
other
attributes
from
those
entities.
So
these
selects
would
cover
selecting
specific
entities.
D
C
D
Definitely,
this
is
more
limited
again
I'm,
just
saying
here's
the
simple
solution
that
will
mostly
work
for
to
the
majority
of
cases.
Right
again,
the
first
part
filtering
by
the
entities
itself
I
think
it's
useful
implementing
even
this
one
without
each
individual
entity-
and
we
can
add
individual
ones
or
we
can
even
add
dropdowns
for
attributes,
but
that
you
understand
right
that
that
would
be
even
more
complicated
because
it's
actually
a
pair.
D
You
have
to
select
for
entity,
and
then
you
have
to
select
the
value,
so
it
gets
even
more
complex
which
we
can't
go
that
route.
Of
course,
if
we
want,
if
we
have
time
or
whatever
but
I,
think
if
we
just
start
with
like
the
bigger
chunk
again
select
the
entity,
then
you
can
refine
by
each
entity
and
then
maybe
you
can
refine
even
further
by
the
attribute
and
value
in
that
entity.
D
B
B
D
B
Choose
what
they
want
to
filter,
whether
they
want
to
filter
image,
they're
used
in
product
a
B
and
C,
or
they
would
choose
to
use
the
filter
that
filtered
by
all
products
right.
So
they
have
all
of
the
filters
for
them
and
whatever
they
choose.
We
just
apply
that
parameters
and
show
the
images
and
if
they
choose
like
two
filters
that
don't
work
together,
there
would
be
just
like
no
results.
Basically
yeah.
D
F
F
That
you
press
the
future
button
and
you
have
a
list
of
those
filters
and
then
you
will
click
apply
and
again
you
will
see
just
very
huge
panel
up
to
your
image
boards
and
it
will
be
not
so
maybe
useful,
maybe
it's
time
to
create
vertical
funnel
with
the
futures,
because
yeah
the
flat
filters
are
good,
but
with
the
current
future
panel.
Maybe
it's
not
so
user-friendly.
D
Yeah
I
agree,
but
that,
if
you
think
about
that
design
that
basically
on
a
higher
level,
then
then
we
working
right
now
right
we're
working
on
each
adding
individual
filters,
and
this
is
work
actually
changing.
How
filters
work
in
general
in
well,
let's
say
just
for
the
this
slide-out
panel
right,
but
still
we
need
to
redesign
the
whole
section
which
again
there
is
a
pattern
like
that
on
the
side,
you
can
have
filters
where
you
have
it
on
a
storefront
and
it's
actually
in
Adobe
spectrum
design
language.
D
B
Unfortunately,
nothing
is
easy
with
magenta
and
what
we
have
is
just
an
implication
of
greed,
that
used
not
only
in
media
gallery
but
also
in
other
places,
and
we
use
the
same
kind
of
pattern
for
filtering
and
that
greed
that
lets
say
in
greets
with
products
or
other
grease
that
we
have
and
changing
that
pattern
would
require
changing
this
pattern
in
other
grids.
Otherwise,
you
are
all
guys
know
that
we
have
like
how
many
types
of
grids
we
have
in
magenta
and
with
that
idea
we
just
introduced
kind
of
another
variation.
F
Sorry,
sorry
to
rat
you,
but
maybe
not
too
great
and
create
a
new
UI
component
for
filters,
because
greet
in
any
case
is
just
the
receiver
of
information
of
data.
So
when,
for
example,
you
click
apply
if
I
understood
this
mechanism
correctly.
So
when
you
click
apply
your
to
magenta
that
magenta
applied
these
amounts
on
fields.
F
Recent
select
these
dates
are
from
database
so
and
maybe,
if
we
can
say
to
do
the
same
thing
to
magenta
from
another
UI
component,
just
we
will
be
great,
but
yeah
I
understand
your
point,
but
just
going
to
suggest
an
idea
if
we
implemented
the
Mehsana
grid.
So
so
maybe
we
could
implementing
you
filter
for
grid
I,
single.
F
F
B
F
F
B
A
Yeah
as
for
filters,
if
we
are
going
to
use
some
of
these
simple
filters
and
display
them
all
at
once,
then
probably
we
need
a
list
of
simple
filters
with
the
options
or
just
the
description
of
option
that
also,
in
this
case
the
name
filter
the
question
the
name
filter
like
if
we
are
searching
the
block
select
blocks,
for
example,
filter
that
Yujin
was
showing
on
his
mock-ups.
Is
it
going
to
have?
Are
we
going
to
provide,
after
so
gesture
just
list
or
just
a
input
for
third
block
name
search.
B
A
D
In
page
builder,
for
example,
we
have,
when
you
open,
the
drop-down,
will
show
you
either
the
full
list
of
entities
available
in
case
of
categories,
for
example,
or
same
as
pages,
or
we
show
you
the
search
for
products
because
there's
so
much
products
right.
We
don't
show
you
any
products
and
you
can
search
by
name,
but
then
you
select
the
entity.
It
shows
you,
the
actual
entities
that
we
found
in
the
database
and
you
select
which
one.
So
it's
not
you're,
not
just
typing
any
name.
D
D
It's
it's
also
complete
feature
so,
for
example,
here
I
have
this
easy
bottom
link
will
not
have
this
compound.
It
will
just
only
have
like
select
whatever,
and
you
see
CMS
pages
I
have
here
already.
I
can
search
for
them
of
course,
and
select
the
issue
one
individually,
but
for
products
with
not
not
showing
you
the
old
products,
but
I
can
select,
I
can
filter,
I'm,
sorry,
I
can
search,
and
it
shows
me
entities
and
I
can
select
like
that.
So
it's
a
a
synchronous
kind
of
like
a
way
of
selecting
entities.
A
D
A
F
F
F
Yeah
great
so
then
I
have
a
question
to
Sergei,
because
you
know
this
issue
inside
out
I
mean
the
content
part
of
enhancement
ago.
So
as
I
understood
now
we
do
not
have.
We
do
not
store
this
relation.
We
store
only,
for
example,
content
or
asset
contents
relation,
but
we
are
not
able
to
simply
get
the
story
of
elation.
Am
I
right
to
this?
F
F
A
Let
me
check
the
other
stories
that
raised
some
questions:
oh
yeah,
by
the
way,
as
so
right
now
the
filtering
looks
a
bit
more
clear
and
simple,
but
there
is
a
story
to
display
the
detailed
information
on
the
same
day
used
in
entities
on
the
view
details
panel.
So
right
now
we
are
displaying
like
number
of
pages
number
of
blocks
number
of
products.
The
asset
is
Houston
and
we
are
of.
We
are
going
to
display
more
information
on
those
entities.
A
B
A
D
Yes
again
trying
to
extremely
simple
so
we're
referring
to
this
section
right,
remove
this
section
and
introduce
a
new
group
and
basically
it
will
show
you
more
detail
and
I'm.
A
food
guru
entities
per
group
will
show
you
the
number
like
pages
to
home,
whatever
products
that
will
be
categories
to
match
box,
just
as
a
simple
kind
of
like
first
step.
But
we
can
do
this
and
maybe
later
we
can
introduce
kind
of
links
here.
So
you
can
click
and
go
to
that
actual
entity.
I,
don't
know
how
that's
gonna
work
like
I.
D
B
D
D
Perhaps
if
we
want
to
go
that
way
like
we
can
have
some
sort
of
a
model
window
for
each
entity
type,
that's
gonna
show
you
the
new
model
with
with
the
table
with
that
information
right,
so
we're
gonna
pull
up
the
data
grid
that
we
have
right
now.
Full
data
grid
with
those
attributes
as
columns,
and
it
would
be
basically
you
will
see-
only
pages
blocks
or
dynamic
box
one
at
a
time
because
yeah,
it's
gonna,
be
mass.
A
A
A
But
from
my
point
of
view,
if
we
are
going
to
displace
detailed
information
on
slight
panel,
then
why
wouldn't
believe
the
basic
use
team
Pollock
as
it
is
right
now,
just
displaying
the
number
of
pages?
If
anyway
clicking
on
Euston,
you
will
get
the
detailed
information,
because
there
can
be
like
that
damage
can
be
used
on
100
products
and
obviating
with
the
show
more.
It
will
probably
fix
it
for
the
beginning.
But
if
you
click
show
more,
it
will
display
100
clients
in
this
block,
and
that
is
going
to
be.
D
D
Then
you
have
like
a
separate
data
grid
for
each
entity
type
in
that
model.
Oh
that's
totally
doable,
but
it's
it's
kind
of
like
more
complicated,
because
user
has
to
scroll
through
may
different
data
grids.
Imagine
like
first
data
grid
would
be
let's
say
products.
That's
going
to
be
a
long
scroll.
Probably
then
it's
going
to
be
pages,
I
suggest
fold
them
only
data
grid
for
the
entity
type
date.
Shoes,
because
that
data
grid
itself
is
a
huge
component
right
and
it
can
have
first
of
all
and
have
multiple
lines.
D
It
also
has
controls
for
pagination
for
I
know,
maybe
filtering
search.
If
we
want
to
add
that,
but
it's
a
component
that
we
can
use
for
it.
So
we
can
yes,
we
can
put
them
all
in
one
page.
We
can
even
put
them
here
on
this
slide
up
panel
at
the
bottom
of
the
style
panel.
We
can
dedicate
the
bottom
of
the
slide.
D
Will
be
basically
infinite
right,
it
will
be,
it
will
have
the
grid,
but
that's
gonna
be
a
long
scroll
by
the
big
others.
How
does
multiple
data
grids
would
work
if
there's
gonna
be
like
thousands
of
images
or
whatever?
Are
we
gonna
make
them?
In
that
case,
how
the
pagination
will
work
right?
If,
let's
say
we
show
I,
know
20
elements
on
one
side,
and
we
just
say
next
page
will
show
another
20,
that's
kind
of
weird.
D
D
Whatever
he
wants
to
know.
If
he
wants
to
die
this
image
is
associated.
He
can
go
that
route.
I,
don't
have
a
solution.
So
that's
right,
yeah
and
I'm,
trying
to
say
I
don't
have
a
reference,
whether
it
should
be
all
in
one
page,
a
lot
of
information
on
one
page
and
possibly
some
weird
UI
issues
again
with
the
generation
whatever
or
it's
just
scoped
I
think
scoped
is
easier,
but
again
we'll
lose
kind
of
like
the
ability
to
see
information
at
the
glance
right.
D
D
It
sounds
weird
but
I
like
this
idea,
because,
let's
think
about
the
workflow
of
somebody
who
use
this
thing
right,
you
said
this
image
can
be
associated
with,
say
thousands
of
products.
So
realistically
I,
don't
think
anybody
would
expect
to
see
this
information
here.
But
if
we
can
open
this
view
in
a
separate
tab
and
basically
filter
the
data
grid
by
this
asset,
50
filtered
the
products
grid
that
use
this
asset
now
I
have
a
specific
view
dedicated
for
that
asset.
D
So
now,
I
can
work
with
the
data,
so
I
can
associate
the
tacit
with
another
products.
I
can
D
associated
asset
or
whatever
and
I
have
an
updated
view.
If
I
just
reload
that
tab,
it
will
update
the
view,
and
it
will
show
me
always
and
I-
don't
need
to
go
into
some
weird
slide
out
panel
and
show
more
and
it
will
show
me
the
model
or
find
this
information
here
scroll
through
the
entities.
I
will
just
have
a
dedicated
tab
open
to
that.
I
think
that
that
would
work
better.
D
Honestly,
it
is
a
little
bit
like
having
some
sort
of
a
like
a
new
window
open
with
specifically
filtered
by
this
entity,
and
we
will
probably
will
not
have
a
UI
for
the
product
grid
to
filter
by
specific
entity.
Unless
we
want
it,
we
can
definitely
develop
such
thing
right.
We
can
add
a
filter
on
the
product
grid
that
lets
you
select
the
asset
and
filter
the
product
users,
but
I
don't
think
it's
needed
honestly.
F
B
A
B
You
guys
are
talking
about
kind
of
the
same
thing:
I
don't
know.
At
least
that
sounds
to
me.
So
we
are
not
going
to
enable
filtering
by
asset
on
a
product
grid
in
to
admin,
but
from
the
media
gallery.
When
user
views
the
asset,
we
will
use
product
grid
and
kind
of
have
this
filtering
by
asset
implemented
behind
the
scene
applied
when
user
clicks
like
show
more
where
this
asset
used
on
products
and
we
use
the
product
grid.
I,
don't
know
in
a
separate
tab
somewhere,
but
we
don't
build
that
interface
ourselves.
B
A
B
A
B
B
B
B
E
A
A
We
have
we
had
that
kind
of
hidden
filters,
not
the
Vista
integration.
I
do
remember
that
there
are
a
lot
of
scenarios
to
be
considered
because
we
want
to
display
this
filter
partially,
but
partially
hide
it
like
when
we
show
that
these
products
in
the
grid,
we
still
need
to
display
the
active
filter
that
we
are
filtering
by
assets,
because
it's
applied
for
user
to
be
able
to
drop
it,
but
we
are
not
displaying
it
in
the
filter
section,
and
that
makes
a
custom
approach
that
first
of
all,
it
probably
requires
some
attention
for
complexity.
A
B
D
Oh
just
to
reiterate,
the
flow
would
be
something
like
this
I
would,
but
we
will
have
the
section
used
in
and
we
will
have
the
numbers
and
then
we
will
within
the
each
number
we
will
have
a
link
that
will
open
a
new
tab
with
data
grid
and
with
the
applied
filter
we
will
have
some
sort
of
a
possibly
again.
If
that's
the
case,
we'll
have
some
sort
of
UI.
D
B
B
D
B
D
B
B
A
D
D
First
of
all,
it
will
select
the
asset
like
this,
not
with
the
ring,
and
it
will
have
ten
on
this
control
here
and
the
actions
probably
will
appear
so
you
can
now
take
actions
with
it,
but
again,
I'm
not
I,
haven't
thought
this
through.
This
is
not
a
real
prototype.
It's
just
like
an
example
of
how
can
this
be
achieved?
I
believe
is
Elena,
it's
a
little
bit
fishy,
because
we're
mixing
different
selections
on
an
on
a
one
interface
right.
D
We
were
selecting
these
are
supposed
to
select
a
single
asset
and
then
proceed
with
edits
to
the
page,
but
now
we're
kind
of
like
allowing
edit
assets.
It's
a
little
bit
weird,
my
proposal.
Maybe
we
have
this
functionality
of
selecting
multiple
assets
and
making
actions
with
them
only
on
a
standalone
media
grid.
Right
we
have
like
the
page
called
media
gallery
right.
You
can.
D
B
D
B
D
B
I,
don't
see
any
harm
of
having
that
functionality
available
anywhere
because,
like
as
a
user,
you
might
have
that
experience.
When
you
are
like
trying
to
insert
the
image,
you
started
filtering
finding
something,
but
then
you
get
just
kind
of
just
started
by
finding
some
assets
that
you
actually
don't
need
and
you
decided
to
clean
up
a
bit.
But
oh
wait!
It's
not
possible
here.
I
need
to
go
somewhere
else.
Wow.
D
B
B
D
I
think
I
think
we
can
try
to
pull
this
off,
though
I
would
want
us
to
basically
enter
a
specific
mode
for
the
this
component
for
from
this
level
panel
work
where
you
can
click
some
button,
and
now
the
this
button
bar
is
gone
and
it
will
be
just
a
button,
color
delete
selected
or
something
like
that
or
cancel
to
basically
another
slider
path,
but
yeah
that
makes
for
that
I
agree.
It's
worth
thinking
over
I
haven't
done
that
much
thinking,
yeah.