►
Description
More from series.
Creative SDK vs Adobe Stock integration.
A
Let
me
share
my
screen
and
today,
I
want
to
represent
the
new
picture
which
we
have
at
the
almonds
for
a
grid,
and
this
is
a
just
image
series,
as
we
know
that
we
have
a
main
image
here
and
under
the
keywords
line,
we
have
a
new
blog,
which
has
named
more
from
this
series
and
help
additionally
for
images.
So
those
images
are
images
that
market.
A
Means
its
own
serious,
yes,
and
switching
between
images.
We
can
just
see
that
related
to
medicine,
serious
idea
so
and
what
I
would
say
that
this
request
is
a
sink
or
nose,
so
it
doesn't
block
image
float.
So
it's
good
for
performance
and
the
next
step
will
be
just
to
introduce
the
show
more
button
on
quick
it.
You
will
get
more
images
from
the
base
Syria
to
which
the
main
image
is
related.
Oh
my
visits
all.
B
A
C
Couple
of
not
notes,
I
understand
is
that
just
like
first
take
on
this
implementation,
we
have
a
mock-up
that
explains
the
spacing
between
the
elements
in
the
image,
details
and
explained
the
spacing
between
battles,
for
example,
keyboard
themselves
and
view
all
button
and
the
size
of
the
buttons.
You
just
pay
closer
attention
to
those
details,
because,
basically
like
following
those
guidelines,
make
the
impression
of
the
design
to
be
like
complete,
because
now
it
really
looks
really
all
of
the
elements
really
close
to
each
other
and
some
of
the
images.
B
Hey
Elena,
I'm,
wondering
I
think
would
be
good
somewhere
on
here
and
I.
Don't
know
if
we
had
this
in
the
original
design.
It
would
be
good
if
there
was
a
link
to
allow
you
to
view
it
on
Adobe
stock.
That
way,
if
there's
any
issue
or
whatever,
so
what
I
was
thinking,
maybe
we
could
maybe
we
could
mock
this
up.
I
was
thinking
where,
where
he
has
file
highlighted,
maybe
that
could
be
a
link.
B
C
We
can
think
about
that.
It
will
be
beneficial
for
me
to
understand
more
clear,
like
what
is
the
use
case.
So
what
can
go
wrong
and
if
we
can't
handle
that
exceptions
properly
in
the
admin
side,
it's
okay
to
add
a
limb,
but
like
haven't
any
external
links
it
in
magenta
admin
will
increase
the
risk
that
people
just
get
navigated.
B
B
That's
what
I,
yeah
I
would
mean
to
open
in
a
separate
tab,
but
also
to
give
some
kind
of
indication
to
the
user
that
they're
going
to
an
external
thing
which
I
don't
know.
If
you
have
you
know,
sometimes
styling
will
have
a
little
icon
with
an
arrow,
pointing
out
to
show
that
you
know
this
will
take
you.
B
C
A
C
C
A
C
B
D
E
B
C
B
B
B
If
you
click
on
any
of
those
images,
I
think
it
will
still
replace
what
we're
looking
at,
but
it's
still
but
the
search
query
and
everything
is
still
the
same
as
sighs
moonlight
on
ocean
and
all
the
other
images
around
it
have
not
changed
as
far
as
I
can
tell
I
don't
yeah,
so
everything
else
is
still
the
same.
Just
this
just
this
component
has
updated
yeah.
B
C
B
B
C
B
C
A
A
A
C
E
A
E
B
C
C
A
C
A
A
D
B
B
A
G
I,
don't
have
anything
to
them,
but
I
have
just
a
quick
update.
Today
we
merged
book
request
we
to
the
magenta
to
Corvis,
fix
to
media
gallery
browser,
and
probably
all
issues
connected
to
JavaScript
on
the
domestic
integration
will
be
resolved.
So
I
recommend
to
update
here
magenta
to
Forks
and
get
the
latest
changes
with
this
fix.
A
Okay,
good,
so
let
me
let
me
show
you
a
couple
of
more
updates,
so
the
first
one
is
that
we
actually
have
more
tests
running
on
Travis
right
now,
so
I
added
API
and
integration
tests
to
the
driver
statute.
So
if
you
update
your
branch
and
look
at
the
result
of
Travis
you'll
see
that
we
now
have
studied
unit
integration
and
an
API
tests,
I'm,
currently
working
out
in
functional
tests
to
Travis
as
well,
it
can
take
some
time
and
yeah
problem
is
its
own.
The
major
update.
F
A
Yeah
yeah
that
would
be
really
good
to
track
our
code
coverage
so
that
we
know
how,
if
you
like,
what
Scott
got
coverage
of
our
tests
in
general,
probably
I
know
somebody
wants
to
take
this
task
and
implement
it
with
Scott
cough
that
will
be
good.
Otherwise,
after
all,
then
I'm
FTF
test
I'm
planning
to
switch
to
it
as
well.
A
A
Actually,
in
the
pull
request
that
is,
are
in
sign-in
link
to
the
grid,
so
the
scene
is
that,
in
order
to
add
a
sign-in
link
and
fetch
the
user
information
as
part
of
signing,
we
need
to
change
our
scope
like
if
you
have
using
creative
SDK,
we
have
to
pass
creative
SDK
as
part
of
our
request
to
the
server.
Let
me
find
that
configuration
and
if
we
are
using
Adobe
stock
integration,
we
have
to
pass
different
parameters
to
URL.
A
B
B
I
wonder
if
we
could
just
require
one
and
then
do
some
sort
of
test
when
you
test
the
connection
to
see,
if
well,
of
course,
to
test
connection
today
doesn't
doesn't
doesn't
test
the
sign-in
mechanism.
All
it
does
is
test
the
up.
The
API
key
word
I
was
trying
to
think
that
if
we,
if
we
required
one
of
them
like
let's
say
we
said,
always
use
creative
SDK
and
then
and
then
it
tests,
and
if,
if
that
scope
fails,
then
we
can
throw
an
error
and
say:
hey
you,
don't
you're,
not
using
the
right
one.
B
B
B
A
A
B
A
A
That's
the
story.
We
have
started
working
on
already
and
it
basically
means
to
move
out
of
this
stock.
I
must
log
into
a
separate
package
and
right
now,
as
we
discussed
it
on
the
previous
meetings,
we
moved
out
that'll
be
ims
and
tired
of
the
ims
modules
and
we
are
planning
to
create
a
separate
repository
for
them,
move
them
to
that
repository
and
release
them
as
separate
package,
and
that
will
be
a
dependency
for
Adobe
stock
package
and
that
can
that
will
be
available
for
the
developers
to
use
as
part
of
the
year.
Adobe
integrations.
C
C
B
C
E
C
So
just
a
couple
of
clarifications
for
me:
maybe
I
missed
that
from
your
discussion,
but
what
I
understood
is
that
we,
you
ran
guys
into
some
issues
and
it's
not
possible
to
provide
the
flexibility
for
users
to
decide
which
integration
to
configure
to
your
stock
either
stock
or
creative
ad
SDK.
So
now
we
need
to
recommend
on
there
like
one
integration.
Is
this
right
or
I
just
kind
of
messed?
Something?
Yes,.
A
So
it's
it's
actually
the
continuation
of
our
discussions
playing
during
grooming
meetings
as
we
identified
the
race
required
different
behaviors
of
and
assessed
levels
of
Adobe
stock
integration
and
creative
SDK
integration
and
security.
As
we
started
implementing
the
requests
for
user
information
for
user
profile,
we
know
you
that
we
have
to
perform
different
requests
out
of
stock,
so
it
would
catch
you
you
have
to
amass,
so
it
will
be.
A
A
B
B
That's
that's
a
thing.
I
mean
it
sort
of
depends
on
the
use
case
if,
in
the
case
of
an
integration
where
this
is
only
going
to
be
used
internally
or
that
so
the
developer
who's,
creating
this
and
is
creating.
The
integration
is
a
member
of
that
company,
and
this
is
only
going
to
be
used
by
members
of
that
one
company-
it's
probably
okay,
to
use
the
stock
integration,
but
if
the
user,
and
also
if
they
don't
care
to
show
to
display
the
user
name
or
anything
like
that,
then
that's,
probably
okay,
too.
B
But
if
it's
a
case
where
a
developer,
maybe
works
outside
the
company
or
multiple
users
might
be
signing
in
and
they
might
be
in
different
companies.
It
would
be
much
better
to
use
the
creative
SDK
scope
because
then,
first
of
all,
it
will
ask
their
permission
to
to
access
their
information
they
give
permission
later
on
they
can.
They
can
withdraw
permission
from
that
from
that
developers,
app
integration
and
also
as
a
side
effect.
You
could
also
access,
like
their
user
name
and
email
address.
If
you
want
it
to
display
those
or
do
something
with
them,.
C
But
if
it's
really
like
small
merchants-
and
they
rely
on
someone
personal
account
and
this
person
needs
to
understand-
okay,
so
how
many
credits
I
have
left
can
I
afford
to
license
the
image.
So
in
this
case
the
personal
information
and
their
the
number
of
credits
left
is
kind
of
more
important.
So
that's
why
you
want,
and
if
I
remember,
there
are
different
types
of
users
support.
B
They
could
they
could
access
anyone
who
signs
in
to
their
account
they
could
they
could
go
and
drain
all
of
their
credits
and
and
those
users
would
have
nothing
no
way
to
do
anything
about
it
other
than
cancelling
their
accounts.
They
would
not.
They
would
never
be
able
to
go
and
withdraw
permission
for
that
bad
developer
to
stop
using
their
credentials,
at
least
that
bad
user
could
use
their
credentials
for
two
weeks
now.
If
this
is
a
small
company,
you
know
the
developer.
You
there's
a
member
of
your
company,
it's
probably
no
big
deal.
B
So,
that's
that's
why
the
creative
SDK
it
has
that
protection
that
you
can
you
can.
You
can
withdraw
your
permission
after
the
fact
and
then
no
one
else
can
still
use
your
credits
now
the
user
would
still
have
to
sign
in
at
least
once
it's.
This
is
not
you
know,
so,
in
all
cases,
in
both
in
both
cases
the
user
still
has
to
sign
in
at
least
one
time,
it's
just
more
of
a
question
of
what
happens
after
they
sign
in.
C
B
Right
so
if
if
they
do
have
two
options
now
now,
then
the
question
is:
what
do
we
display
it's
it'll
be?
It
would
be
difficult
to
know
for
your
application,
for
your
integration
to
know
which
type
they've
chosen.
So
we
really
want
them
to
tell
us
when
they
when
they
set
it
up.
So
if
they
choose
one
of
the
two
we
should
know
which
one
it
is
and
then
there
should
be
some
way
to
confirm
that
or
we
just
say
everyone
do
this
one
thing
and
that's
just
the
way
it
is.
B
It's
just
the
one,
that's
more
protective.
So
if
we
just
required
everyone
to
use
that-
and
you
always
called
the
creative
SDK
scope,
then
if
they
try
to
use
the
stock
only
integration,
it
should
fail
and
then
we
could
have
some
documentation
explaining
hey.
Did
you
follow
the
instructions?
The
instructions
say
you
know
it's
not
intuitive,
but
use
creative
SDK,
not
just
Adobe
stock.
So
if
you,
if
you
require
it
at
the
integration
level,
I
mean
a
developer,
could
go
in
and
change
it
because
it
is
open-source.
B
C
B
So
that's
where
it
gets
tricky
so
with
the
creative
SDK,
it
will
support
any
individual
user.
What
we
call
type
one
if
the
if
the
company
has
a
type
2
or
type
3
of
their
enterprise
if
their
enterprise-
and
they
have
done
some
certain
things
to
their
identity,
it
it
will
block
them
from
logging
in
unless
they
contact
us
and
ask
us
to
waitlist
them.
I,
don't
really
know
mine.
That
I
really
mind.
If
they
do
that,
you
know
you
can
give
them.
My
I
have
my
group
ID.
That
way.
B
We
know
because
at
that
that
way
we
have
a
little
bit
of
control
and
visibility
on
who's
actually
using
this,
because
then
I
can
be
a
gatekeeper
to
allow
them
to
do
you
know
to
to
give
them
this
access,
and
then
we
know
hey.
You
know
these
companies,
you
know,
but
that's
that's
up
to
you
it
just
that's
that's
kind
of
how
we
do
it
today.
We
tell
customers
to
go
out
and
sign
up
for
this
and
they
come
to
me
if
they
need
to
allow
enterprise
logins.
So.
B
The
other
way
around,
so,
if
there,
if
they
have
an
enterprise,
if
they
have
an
enterprise,
account
or
enterprise
hook,
they
don't
they're,
not
automatically
type,
become
type
2
or
type
3.
They
have
to
actually
go
into
the
admin
console
and
what
they
call
claim
the
domain.
So
they
they
say.
Ok,
my
domain
is
you
know
my
images
dot-com
or
you
know
my
my
chairs
comm,
so
they
would
claim
my
chairs
calm.
B
So
anyone
who
has
an
email
address
with
Christopher
at
my
chairs,
calm
or
Elena
at
my
chairs,
calm
automatically
becomes
part
of
their
domain.
That
means
they
become
type
2.
Now
they
would
have
to
do
an
additional
step
if
they
want
to
also
use
their
own
identity
provider,
so
they
have
Active
Directory,
login
and
some
kind
of
single
sign-on.
So
they
would
have
to
draw
one
more
step
if
they
wanted
to
become
type
3,
but
got
it
if
they
do
nothing.
If
they
do
nothing
at
all.
B
With
some
of
our
smaller
customers
do
some
of
the
smaller
customers?
Don't
do
any
of
this?
There
they
just
are
by
default
all
type
1.
So
one
is
automatically
supported
for
all
creative
SDK
type,
2
and
type
3,
that's
where
they
would
need
to
comment,
asked
us
and
we
just
put
in
a
ticket.
It
gets
resolved
in
few
days
and
stuff.
Do.
B
B
I
don't
know
now
I'd
have
to
ask
we
could
we
could
we
could
we
can
pursue
that
as
a
separate
thread
offline?
If
you
want
to
I,
can
I
can
put
you
in
touch
with
you
know,
because
I
remember
we
did
this
before
when
we
were
working
with
HootSuite
and
we
found
that
there
really
aren't
a
lot
that
the
majority
of
our
enterprise
customers
are
still
using
type
1
logins,
although
we
are
trying
to
push
them
we're
trying
to
get
them
to
do
type,
2
and
type
3.
So
actually
we
are
trying
to
encourage
them.