전사 🔗
00:00:00.000 --> 00:00:01.530
Sam Brace: Hey there.
00:00:01.770 --> 00:00:03.580
Welcome to DevJams.
00:00:03.600 --> 00:00:08.730
This is where we talk with developers
who are doing very interesting things.
00:00:08.730 --> 00:00:13.050
Maybe they're projects that are pushing
the boundaries of what's possible with
00:00:13.055 --> 00:00:15.180
image and video management and delivery.
00:00:15.420 --> 00:00:17.760
Maybe they're looking at things
from a different perspective.
00:00:18.120 --> 00:00:22.290
Maybe it's just things that we got really
excited about here at Cloudinary, and
00:00:22.590 --> 00:00:25.170
that's where we're gonna be talking
about the intersection of where
00:00:25.170 --> 00:00:30.540
developers are building awesome, amazing
projects and how they're incorporating
00:00:30.600 --> 00:00:32.430
Cloudinary into those projects.
00:00:41.760 --> 00:00:42.960
My name is Sam Brace.
00:00:42.965 --> 00:00:45.690
I am the Senior Director
of customer Education and
00:00:45.690 --> 00:00:47.280
Community here at Cloudinary.
00:00:47.625 --> 00:00:52.125
And in this DevJams episode, we're
gonna be talking with one of our very
00:00:52.125 --> 00:00:56.835
own employees, one of our solutions
architects, Igor, and he has gone and
00:00:56.835 --> 00:01:02.745
developed an amazing project connecting
together Canva, one of the best, most
00:01:02.745 --> 00:01:07.755
widely used tools when it comes to
creating content, specifically, maybe
00:01:07.755 --> 00:01:10.905
slides, maybe graphics, all sorts
of things you can do with Canva.
00:01:10.910 --> 00:01:15.525
It's a tool that I personally love
using, and I'm very excited to show how
00:01:15.525 --> 00:01:19.815
he created this connector between Canva
and Cloudinary to really make sure that
00:01:19.815 --> 00:01:24.795
there's a space for creating this overall
content inside of Canva, and then making
00:01:24.795 --> 00:01:29.775
sure that it can be optimized, delivered
perfectly for websites, mobile projects,
00:01:29.775 --> 00:01:32.765
and other various needs via Cloudinary.
00:01:33.479 --> 00:01:36.750
Joining me for this
episode is Becky Peltz.
00:01:36.839 --> 00:01:40.350
And Becky Peltz, of course, is somebody
that you've seen in almost every
00:01:40.350 --> 00:01:45.149
Dev Jams episode, and she oversees
our overall curriculum and learning
00:01:45.179 --> 00:01:49.800
opportunities at Cloudinary for our
developers that are using Cloudinary.
00:01:50.039 --> 00:01:53.300
So Becky, it is wonderful to
have you here for this episode.
00:01:54.480 --> 00:01:56.250
Becky Peltz: Hey, I'm excited to be here.
00:01:56.250 --> 00:02:03.509
I used Canva as an instructional design
student for many years, and I was always
00:02:04.109 --> 00:02:08.699
downloading it from Canva, uploading
it to Cloudinary, and so I love this
00:02:08.704 --> 00:02:11.200
project and it's great to be here.
00:02:12.629 --> 00:02:14.130
Sam Brace: I completely agree.
00:02:14.310 --> 00:02:17.610
What's wonderful about this, as you're
pointing out, is that is a flow, but
00:02:17.610 --> 00:02:20.880
not only you have faced and I have
faced, but it's probably something that
00:02:20.885 --> 00:02:26.760
millions of Canva users have faced, is
they probably have certain times where
00:02:26.760 --> 00:02:30.790
they say, I would love to have this
delivered as a URL, and not only as a
00:02:30.790 --> 00:02:35.130
URL to make sure it's optimized of all
of the various things to make sure that
00:02:35.250 --> 00:02:39.810
it loads quickly and efficiently on
people's devices, on people's browsers.
00:02:39.810 --> 00:02:44.130
So it's to say that this is not just a
niche use case, and it's something that
00:02:44.135 --> 00:02:46.590
excites maybe a portion of the population.
00:02:46.830 --> 00:02:50.520
To me, this is something that every
Canva user can benefit from the work that
00:02:50.520 --> 00:02:52.070
Igor is gonna be showing us here today.
00:02:52.100 --> 00:02:53.870
So I'm very excited by that.
00:02:54.885 --> 00:02:59.085
Becky Peltz: Yeah, and I think for
developers we have a lot of integrations
00:02:59.085 --> 00:03:03.075
with a lot of different tools,
headless tools, image video tools.
00:03:03.465 --> 00:03:07.575
But I think it's interesting to be
able to see how an integration is
00:03:07.580 --> 00:03:13.145
created, and in Igor's process, he
worked with the Canva documentation,
00:03:13.175 --> 00:03:18.505
and to just of see how how this
integration is done using a node server.
00:03:18.565 --> 00:03:22.405
So I, there's many different ways to
integrate and this is an interesting one..
00:03:23.135 --> 00:03:23.945
Sam Brace: Exactly.
00:03:24.000 --> 00:03:27.750
And I gotta tell you, if you're a
developer that is trying to figure out
00:03:27.755 --> 00:03:31.660
ways to connect two like-minded systems
together, you're gonna find an absolute
00:03:31.770 --> 00:03:34.140
amazing learning resource in this.
00:03:34.320 --> 00:03:37.135
But if you're just a Canva user or
a Cloudinary user and you're trying
00:03:37.135 --> 00:03:40.019
to say huh, I've always wondered if
those two systems can work together,
00:03:40.079 --> 00:03:41.940
there's all sorts of things you're
gonna be able to extract from this.
00:03:41.940 --> 00:03:44.190
So should be a great
conversation with Igor.
00:03:44.880 --> 00:03:48.030
One thing I do wanna point out before
we bring our friend Igor onto this to
00:03:48.030 --> 00:03:52.410
start talking all about his project,
is we do wanna point out that all
00:03:52.440 --> 00:03:55.200
Cloudinary podcasts, including the
one that you're part of here today,
00:03:55.204 --> 00:04:00.549
which is DevJams, that is gonna be
found at cloudinary.com/podcasts.
00:04:00.900 --> 00:04:05.160
And as we can see here on the screen,
that is where you're able to go through
00:04:05.160 --> 00:04:09.480
and review all of the previous podcasts
that we have gone and issued across the
00:04:09.480 -->
Load full transcript
00:04:11.550
many different programs that we do have.
00:04:12.080 --> 00:04:15.395
And of course you can dive into
the episodes and watch them and
00:04:15.395 --> 00:04:17.154
listen to them as you so choose.
00:04:17.555 --> 00:04:20.525
And similarly, you can enjoy
these on any of the services
00:04:20.525 --> 00:04:22.084
that you we happen to be on.
00:04:22.265 --> 00:04:26.855
That includes our own Cloudinary Academy,
YouTube, also in listening only mode
00:04:26.860 --> 00:04:32.315
for various services like Spotify, Apple
Podcasts, Google Podcasts and more.
00:04:32.825 --> 00:04:35.585
And we're gonna have some
great conversations here today.
00:04:35.615 --> 00:04:38.585
But if you wanna continue those
conversations, pass this episode,
00:04:38.825 --> 00:04:44.465
know that you can always head over to
community.cloudinary.com and be part of
00:04:44.470 --> 00:04:48.005
all of those various discussions that
are taking place so you can meet other
00:04:48.005 --> 00:04:53.555
users maybe those like Igor or maybe those
that were previous guests on DevJams, or
00:04:53.555 --> 00:04:56.705
people that have never been on DevJams,
but possibly could be because they're
00:04:56.705 --> 00:05:00.275
doing great things with our overall
service and pushing the boundaries of
00:05:00.280 --> 00:05:03.935
what's possible with image and video
delivery and management programmatically.
00:05:04.415 --> 00:05:07.595
So want to make sure everybody is
aware of those things before we
00:05:07.595 --> 00:05:10.005
jump on over to talk with Igor.
00:05:11.965 --> 00:05:15.135
Igor, let's have you
come on to the program.
00:05:15.585 --> 00:05:16.365
Great to have you here.
00:05:16.755 --> 00:05:17.445
Igor Vorobeychik: Hi there.
00:05:18.285 --> 00:05:20.115
Sam Brace: Igor, let's get a
little bit of context here.
00:05:20.115 --> 00:05:23.325
So I gave you the audience some
details saying you're a Solutions
00:05:23.325 --> 00:05:25.095
Architect that works at Cloudinary.
00:05:25.215 --> 00:05:26.895
I didn't give anybody much more detail.
00:05:26.955 --> 00:05:30.045
So go ahead, give us a little
bit of flavor about who is Igor
00:05:30.045 --> 00:05:31.455
and why are you here today.
00:05:32.535 --> 00:05:32.925
Igor Vorobeychik: Thank you.
00:05:32.955 --> 00:05:33.705
Thank you Sam.
00:05:34.055 --> 00:05:35.905
Thank you Becky.
00:05:35.905 --> 00:05:40.705
And yes, I'm a new, relatively new
solution architect in Cloudinary.
00:05:40.705 --> 00:05:43.445
Even though almost a year
within the Cloudinary.
00:05:44.805 --> 00:05:50.705
And I've been in the
industry since year 2000.
00:05:51.105 --> 00:05:58.815
So been sometime in different roles as
a web developer, team lead, as a managed
00:05:59.685 --> 00:06:06.135
professional services, integrated lots
of different systems during my career.
00:06:06.555 --> 00:06:09.145
Excited to be part of
the Cloudinary family.
00:06:09.855 --> 00:06:12.570
And this is more or less my background.
00:06:14.310 --> 00:06:17.610
Sam Brace: And what's great about
what's happening here is that, of
00:06:17.610 --> 00:06:21.630
course, you're a first guest that is
really coming from the solutions team.
00:06:21.630 --> 00:06:26.580
We typically pro profile people from
the outside, people that have done
00:06:26.585 --> 00:06:30.420
something with no ties to Cloudinary
before, other than maybe reading the
00:06:30.420 --> 00:06:33.450
documentation, maybe being inspired
by some of the training courses we
00:06:33.450 --> 00:06:35.280
have, and they go and build something.
00:06:35.280 --> 00:06:38.370
But you of course work with us
and we get the chance to interact
00:06:38.370 --> 00:06:39.780
with you on a daily basis.
00:06:40.080 --> 00:06:44.880
Tell us about why you decided as part
of the getting to learn Cloudinary
00:06:44.880 --> 00:06:48.750
phase, being within Cloudinary
and understanding what it's about.
00:06:48.900 --> 00:06:52.110
What inspired to do this project
that you have here today, connecting
00:06:52.260 --> 00:06:53.820
Canva and Cloudinary together?
00:06:54.810 --> 00:06:55.080
Igor Vorobeychik: Sure.
00:06:56.010 --> 00:07:02.160
First of all before even I decided to
join Cloudinary, I was excited about
00:07:02.160 --> 00:07:04.290
Cloudinary onboarding process, right?
00:07:04.500 --> 00:07:06.720
Which sounds for me, unique.
00:07:06.989 --> 00:07:09.659
Some companies doesn't
even have such a process.
00:07:10.289 --> 00:07:15.179
And part of this process was
actually, that was clear to me from
00:07:15.179 --> 00:07:19.080
my manager, is that I will have
to build some sort of a project.
00:07:19.440 --> 00:07:25.979
The project should be something real,
not some, imaginary and unusable
00:07:26.179 --> 00:07:31.979
project project should be maybe even
blog, something facing our customers.
00:07:32.590 --> 00:07:37.530
And I said, this company probably
does something right if they
00:07:37.534 --> 00:07:42.925
want their own employees actually
use the software, try it.
00:07:42.925 --> 00:07:49.090
And they actually later deliver
it to the clients and customers.
00:07:49.094 --> 00:07:52.049
And I was excited already in this part.
00:07:52.349 --> 00:07:55.690
I was sold pretty much in the beginning.
00:07:56.159 --> 00:08:02.039
And eventually due to my background
in some building some online editors
00:08:02.039 --> 00:08:07.109
or involved in lots of integration,
when I saw one of the projects or
00:08:07.109 --> 00:08:11.879
possibilities to build something with
Canva, there was an easy choice for me.
00:08:14.399 --> 00:08:17.534
Sam Brace: Well, and I think the great
thing about being able to do this,
00:08:17.539 --> 00:08:19.335
is that, as you're saying, it's real.
00:08:19.335 --> 00:08:24.164
It's code that people can use today
to be able to bring these two systems
00:08:24.164 --> 00:08:28.215
that don't have direct integrations,
official integrations, together, but
00:08:28.365 --> 00:08:31.514
you are
able to create something that
really is gonna benefit so many users
00:08:31.514 --> 00:08:35.855
and also give essentially developers
an answer when someone says, can
00:08:35.855 --> 00:08:37.024
you connect these systems together?
00:08:37.355 --> 00:08:40.694
You've given 'em a very clear
pathway, which I love that was
00:08:40.694 --> 00:08:45.464
part of your graduation project
as a good term that is out there.
00:08:45.464 --> 00:08:48.464
A way for you to say, I'm putting
my work out into the world.
00:08:48.464 --> 00:08:50.815
This is my first way to tell
people I'm working at Cloudinary.
00:08:51.329 --> 00:08:53.550
And be able to do that
in an excellent way.
00:08:53.550 --> 00:08:56.069
So that was fantastic that you've
been able to pull this off.
00:08:56.579 --> 00:08:58.589
But what inspired you to look at Canva?
00:08:58.609 --> 00:09:02.760
Was there ever experiences working
with it or seeing it out in the wild?
00:09:02.764 --> 00:09:04.169
Maybe personally, professionally?
00:09:04.389 --> 00:09:08.040
What got you to say I should
link this to Cloudinary?
00:09:08.490 --> 00:09:13.510
Igor Vorobeychik: So for the past 15
years I was actually working a lot with
00:09:13.510 --> 00:09:15.990
the a lot of Adobe products, right?
00:09:16.649 --> 00:09:20.669
InDesign, Photoshop, a lot
of personalization using
00:09:20.669 --> 00:09:23.129
InDesign servers and et cetera.
00:09:23.159 --> 00:09:28.970
We had lots of requirement from users to
have something as powerful as Photoshop.
00:09:29.079 --> 00:09:34.710
Maybe not necessary as complex as
Photoshop, but for the wide variety of
00:09:34.710 --> 00:09:37.450
customers, and have it online, right?
00:09:38.160 --> 00:09:44.670
And I would say about already maybe
four or five years ago, the Canva,
00:09:44.700 --> 00:09:46.330
everybody was talking about Canva.
00:09:46.350 --> 00:09:49.069
I said, I need to look at the Canva.
00:09:49.200 --> 00:09:54.990
And by the way, my own previous job we
had our own proprietary online editor.
00:09:54.990 --> 00:09:57.720
When I saw the Canva, just blew my mind.
00:09:57.720 --> 00:10:05.220
And this is a unique Australian company
which developed something unique.
00:10:05.790 --> 00:10:13.890
And when I joined Cloudinary, I saw
parallels that Canva was the best at
00:10:13.890 --> 00:10:16.530
what they do in the design space, right?
00:10:16.530 --> 00:10:20.970
And Cloudinary is the best of
what they do with the media.
00:10:20.970 --> 00:10:26.130
And and for me it was
interesting to combine those two.
00:10:26.579 --> 00:10:31.860
And actually I think you started
your podcast with with something that
00:10:31.860 --> 00:10:34.050
millions of users are using Canva.
00:10:34.110 --> 00:10:41.680
And I actually today Googled, I think I
found that, again, it's a bit old article,
00:10:41.680 --> 00:10:50.530
but in 2022, the projection was that they
were gonna hit about 1 million user mark.
00:10:50.960 --> 00:10:58.649
So an amazing, so I
always,
I had some commercial way of
00:10:58.649 --> 00:11:00.300
looking at one new build, right?
00:11:00.329 --> 00:11:04.030
One one way is to build something
which can be useful, but that if
00:11:04.379 --> 00:11:08.190
our developers can also make it
out of it, a successful product.
00:11:08.609 --> 00:11:14.879
So I think to this connector can expose
them, can expose their Cloudinary,
00:11:15.149 --> 00:11:17.280
maybe to a millions of users, right?
00:11:17.909 --> 00:11:22.139
It could be a business to
business, it could be a B2C.
00:11:22.139 --> 00:11:27.869
So it just gives them ideas of how
they can actually help millions
00:11:27.869 --> 00:11:31.569
of users to deliver media.
00:11:31.950 --> 00:11:34.040
And that's what's
exciting, I think about it.
00:11:35.960 --> 00:11:37.890
Becky Peltz: Yeah, I think
this is interesting too.
00:11:37.890 --> 00:11:42.839
I was looking at the documentation from
Canva and I noticed that we'll be seeing
00:11:43.040 --> 00:11:47.100
movement from Canva into Cloudinary,
but you can actually move both ways.
00:11:47.400 --> 00:11:51.480
So here you have these two kind of
headless media companies able to
00:11:51.480 --> 00:11:56.280
exchange with each other and then
of course other websites if needed.
00:11:56.280 --> 00:12:00.720
So it's just a really cool
integration between these two
00:12:00.750 --> 00:12:02.370
companies and their product.
00:12:04.710 --> 00:12:05.670
Sam Brace: Absolutely.
00:12:05.730 --> 00:12:09.690
So Igor, let's do a quick
walkthrough of this so that way
00:12:09.694 --> 00:12:10.890
everybody understands what this is.
00:12:10.890 --> 00:12:13.200
Cause I think we've talked
about conceptually enough where
00:12:13.440 --> 00:12:16.319
something's happening in Canva,
content creation, and then it's
00:12:16.319 --> 00:12:17.730
gonna be delivered by Cloudinary.
00:12:17.730 --> 00:12:20.190
But let's see the overall
flow of this thing.
00:12:20.190 --> 00:12:24.560
So I'm gonna bring your screen in here
and maybe we can do a quick demonstration.
00:12:25.665 --> 00:12:25.935
Igor Vorobeychik: Sure.
00:12:25.940 --> 00:12:26.625
Absolutely.
00:12:26.655 --> 00:12:28.685
So here I'm in Canva, right?
00:12:29.494 --> 00:12:32.685
And I want to create my design.
00:12:32.714 --> 00:12:37.280
Let's assume it's some
Instagram post maybe, right?
00:12:38.540 --> 00:12:44.699
I can choose from variety of different
designs, like templates, right?
00:12:44.699 --> 00:12:51.389
And I don't know, maybe this
is an HR type of post like we
00:12:51.395 --> 00:12:54.389
are hiring or some other stuff.
00:12:54.389 --> 00:13:00.689
Maybe I want to to customize it, right?
00:13:02.519 --> 00:13:08.970
Once I customize it, I would like
probably to publish it, right?
00:13:09.540 --> 00:13:16.439
And this is where the a lot of
customers will say, okay, what do I do?
00:13:16.439 --> 00:13:22.020
How do I make sure that it will be
delivered in most optimized format?
00:13:22.050 --> 00:13:28.619
How I will actually use this CDN
also, so it's gonna be cashed super
00:13:28.619 --> 00:13:30.300
fast and et cetera, et cetera.
00:13:30.300 --> 00:13:33.119
So millions of users can
see this fast and et cetera.
00:13:33.119 --> 00:13:35.495
And this is where the integration.
00:13:35.495 --> 00:13:39.375
So all they need, if let's say they
have already a Cloudinary account,
00:13:39.855 --> 00:13:46.785
and they have an integration, then
they just, in this case, I have
00:13:46.785 --> 00:13:48.704
this already integration in place.
00:13:48.704 --> 00:13:54.795
I'm choosing the Cloudinary, it's already
connected to my particular cloud, right?
00:13:55.275 --> 00:13:58.725
And I can choose maybe some
folder where I want to maybe
00:13:59.245 --> 00:14:00.435
organize something like that.
00:14:00.735 --> 00:14:05.195
Maybe I can choose the format,
one of the formats that's
00:14:05.525 --> 00:14:07.604
available for me to save this.
00:14:07.604 --> 00:14:10.584
This is, by the way,
configurable by your extension.
00:14:11.545 --> 00:14:17.515
Maybe provide some message that can
be used later on there, and save it.
00:14:18.525 --> 00:14:25.215
If all went well and my extension
is up and running, first of all,
00:14:25.215 --> 00:14:29.395
you're gonna get back already a
URL, which can be shared, right?
00:14:32.255 --> 00:14:37.259
The version which we
just customized, right?
00:14:38.759 --> 00:14:42.570
If those of you who know Cloudinary,
you will see that this version
00:14:42.570 --> 00:14:48.420
include f_auto, q_auto, meaning is
optimized format, optimized quality.
00:14:48.420 --> 00:15:00.560
And again, we can go wild here and
add more transformation even on top of
00:15:00.949 --> 00:15:10.590
this asset, and if we will go to the
Cloudinary, and let's say go to this
00:15:12.650 --> 00:15:16.814
folder, we will find this asset now.
00:15:16.874 --> 00:15:23.864
And we also can notice that I
applied some contextual metadata.
00:15:23.864 --> 00:15:26.175
I applied some tags to it, right?
00:15:26.175 --> 00:15:35.074
So that can be also searchable
within my my let's say asset library
00:15:35.135 --> 00:15:44.205
to find something that has certain
tags something that maybe has a
00:15:44.205 --> 00:15:48.195
contextual metadata we scan by id.
00:15:48.495 --> 00:15:54.735
So I can basically not only publish
it, but also organize it in a certain
00:15:54.735 --> 00:15:57.165
way within the Cloudinary, right?
00:15:57.824 --> 00:16:04.344
And obviously this published URL
now can be served in any systems
00:16:04.344 --> 00:16:07.305
can can be used on any website.
00:16:07.844 --> 00:16:12.814
So that's the overall workflow
final workflow which we see.
00:16:13.680 --> 00:16:17.820
Sam Brace: It's incredible and I think
what's amazing about it is that you've
00:16:17.820 --> 00:16:22.739
able to done do a few things that
you've pointed out really is that if you
00:16:22.739 --> 00:16:27.090
wanna make sure that this is now
easily
searchable for inside of your Cloudinary
00:16:27.094 --> 00:16:31.759
system, you've now shown how adding
something into the comments field be as
00:16:31.759 --> 00:16:36.539
searchable content that when it makes
its way into Cloudinary as an asset.
00:16:36.870 --> 00:16:39.569
I think it's also where we
didn't have to wait long.
00:16:39.739 --> 00:16:41.279
This is a real-time demonstration.
00:16:41.279 --> 00:16:43.170
This wasn't taped prior
or anything like that.
00:16:43.640 --> 00:16:47.039
And then you add something where you
created in Canva, you delivered it
00:16:47.045 --> 00:16:51.719
in to Cloudinary within a minute,
if less it's incredible what you
00:16:51.725 --> 00:16:52.769
just pulled off here at Igor.
00:16:52.769 --> 00:16:53.910
Becky, I didn't mean to interrupt you.
00:16:53.910 --> 00:16:54.630
You had a point there.
00:16:55.979 --> 00:16:56.489
Becky Peltz: No problem.
00:16:56.489 --> 00:16:58.529
But yeah, I was struck by the, same thing.
00:16:58.719 --> 00:17:05.010
We've taken an image that had really no
context, no metadata, and made it into,
00:17:05.070 --> 00:17:10.340
put it into a place where it can be, have
a high amount of context and be pulled
00:17:10.340 --> 00:17:17.579
in from many different data identifiers
like the tag or the context metadata.
00:17:17.989 --> 00:17:23.190
So I think that's something to look for
as we see how you implemented this Igor
00:17:23.190 --> 00:17:29.670
is how did you get that context associated
with those images that you are pulling in?
00:17:31.290 --> 00:17:32.159
Igor Vorobeychik: Yeah, absolutely.
00:17:32.159 --> 00:17:35.730
So this is where we can, we will
need to already get in the bits
00:17:35.730 --> 00:17:37.315
and bytes of the integration.
00:17:37.404 --> 00:17:41.449
So I guess that would be
a natural progression.
00:17:41.455 --> 00:17:52.400
So for those that would like maybe later
go a bit more detailed I do have a blog
00:17:53.240 --> 00:17:59.385
that you can find that describes how to
build Canva extension give you pretty
00:17:59.385 --> 00:18:01.725
much all the information you need.
00:18:01.725 --> 00:18:03.855
This is just like for
your reference, right?
00:18:03.855 --> 00:18:05.205
So have you detailed here.
00:18:06.175 --> 00:18:09.465
We may not be able to dive
into all the aspects here.
00:18:10.094 --> 00:18:15.445
For this particular project and
also the project that was facing
00:18:15.445 --> 00:18:18.575
the public, I decided to use Glitch.
00:18:19.765 --> 00:18:25.845
Glitch is a very easy way where
you can create an application.
00:18:26.505 --> 00:18:35.955
You do not have to use any desktop id
you pretty much, any student can use it.
00:18:35.955 --> 00:18:38.895
He doesn't have need to have
a very powerful computer or
00:18:38.895 --> 00:18:42.825
any proprietary software.
00:18:42.825 --> 00:18:45.105
He can create a very powerful application.
00:18:45.110 --> 00:18:51.085
I use the, in this
particular express framework.
00:18:51.495 --> 00:18:59.555
This is for for, to create my
REST API influence that should
00:18:59.555 --> 00:19:03.284
satisfy Canva publish extension.
00:19:03.284 --> 00:19:06.554
We're going to get into
details a bit more.
00:19:06.554 --> 00:19:13.965
So I use Glitch as a platform where
I develop the poc and also also
00:19:14.205 --> 00:19:19.455
something that is actually the,
where I published my endpoint, right?
00:19:19.455 --> 00:19:25.365
So this is a development environment
plus actual my endpoint resides on
00:19:25.370 --> 00:19:27.915
this system and can be accessed, right?
00:19:28.275 --> 00:19:30.844
So it's self-contained.
00:19:31.094 --> 00:19:35.594
Some of you may use some
IDE Visual Studio Code.
00:19:35.655 --> 00:19:43.860
They maybe gonna use git or GitHub
to, for their PUT versioning and
00:19:43.860 --> 00:19:48.100
eventually they may use, I don't
know, let's say AWS to actually
00:19:48.105 --> 00:19:53.360
publish their lambda their endpoints.
00:19:53.380 --> 00:19:56.280
But this is more like self-contained.
00:19:56.280 --> 00:19:57.750
A bit easier to understand.
00:19:57.755 --> 00:20:06.900
But I also love Glitch, its an awesome
company, which was acquired by Fastly,
00:20:06.900 --> 00:20:12.965
which is also a Cloudinary CDN partner.
00:20:13.335 --> 00:20:17.205
This is what I used for
this particular project.
00:20:17.755 --> 00:20:21.065
Becky Peltz: Hey, just not to
interrupt you, but excuse me, Igor,
00:20:21.065 --> 00:20:28.295
but for this extension, now I, as I
understand it, you need a base URL.
00:20:28.325 --> 00:20:32.825
So, whatever code that you, however
you package it up, whether in
00:20:32.830 --> 00:20:36.875
Glitch or in serverless functions,
you will need a base URL.
00:20:36.875 --> 00:20:39.514
So you get that automatically
from Glitch, right?
00:20:39.545 --> 00:20:40.055
Igor Vorobeychik: Exactly.
00:20:40.125 --> 00:20:47.705
So your like a unique name space, right?
00:20:48.155 --> 00:20:49.915
You call it a domain name.
00:20:49.960 --> 00:20:58.655
You obviously have a more robust version
and pay for your CNAMEs and have but
00:20:58.715 --> 00:21:08.010
yes, it was very easy to use because
I got all my domain names, everything
00:21:08.010 --> 00:21:10.320
set up for me pretty much, right?
00:21:11.070 --> 00:21:12.000
You getting it.
00:21:12.050 --> 00:21:14.130
And it, it was very easy.
00:21:14.400 --> 00:21:19.080
Now, Canva also has
tremendous documentation.
00:21:19.580 --> 00:21:26.460
And I actually when I look, looked at
Canva documentation, look in Cloudinary
00:21:26.550 --> 00:21:35.400
and saw how we both create a very unique
content in a very professional way.
00:21:35.405 --> 00:21:41.870
So it was so easy for me being a new SA
within Cloudinary just by reading some of
00:21:41.870 --> 00:21:44.310
the documentation, try the samples, right?
00:21:46.240 --> 00:21:50.950
Be able to achieve what you see
here in, in a very few days.
00:21:51.240 -->
00:21:51.790
Literally.
00:21:52.320 --> 00:21:58.925
Sam Brace: This was new to me because,
like I've always thought, this is my
00:21:58.940 --> 00:22:02.745
ignorance, is that I always thought of
Canva as being a very UI based tool,
00:22:02.745 --> 00:22:06.195
but as I started going down the rabbit
hole and being like, oh, but have great
00:22:06.195 --> 00:22:11.235
developer documentation and seeing
this area, it was very enlightening
00:22:11.235 --> 00:22:16.155
for me to be able to see this project,
but also to see the various layers
00:22:16.155 --> 00:22:19.515
that Canva has created to be able
to create these types of connections
00:22:19.755 --> 00:22:20.835
that you've gone and showed here.
00:22:20.835 --> 00:22:25.065
So I can see here on your screen the
way that they're calling this is a
00:22:25.065 --> 00:22:27.585
publication or a published extension.
00:22:27.885 --> 00:22:31.545
So what they're ultimately doing is
it's getting added to the published
00:22:31.545 --> 00:22:36.435
menu of Canva and it becomes an app just
like you chose it from in this space.
00:22:36.440 --> 00:22:38.665
And that's what they're encouraging
developers to be creating.
00:22:39.335 --> 00:22:39.875
Igor Vorobeychik: Exactly.
00:22:39.900 --> 00:22:47.340
So Canva has lots of out of the
box extensions, but it also allow
00:22:47.340 --> 00:22:50.510
developers to create their own.
00:22:50.860 --> 00:22:53.640
And there are several types of extension.
00:22:54.140 --> 00:22:56.410
There are content extension.
00:22:56.460 --> 00:23:01.210
For example, one of the next steps
maybe would be bringing assets
00:23:01.230 --> 00:23:05.490
from Cloudinary, and that would
be a content extension, right?
00:23:05.760 --> 00:23:09.930
So this is, would be probably on
the left when you do upload, that's
00:23:09.930 --> 00:23:11.790
what it called content extension.
00:23:11.795 --> 00:23:15.750
Where you're taking the extension
from your asset from right
00:23:16.080 --> 00:23:17.610
where you selecting your asset.
00:23:17.940 --> 00:23:18.780
Not necessary.
00:23:18.780 --> 00:23:20.130
You start from design.
00:23:20.130 --> 00:23:24.870
Maybe you want to bring in us another
type of extension is this is where you
00:23:24.870 --> 00:23:26.970
publish and it's a publish extension.
00:23:26.970 --> 00:23:32.370
So here you see my extension, but
if I do more, you will see that a
00:23:32.370 --> 00:23:36.030
lot of connectors are already there.
00:23:36.870 --> 00:23:43.650
And those can, some of them are
written by well known companies
00:23:43.650 --> 00:23:45.900
like Instagram and et cetera, right?
00:23:46.260 --> 00:23:50.720
But some of them, like mine was
written by developers, right?
00:23:52.830 --> 00:24:03.690
So there is lots of extensions and there
is a great developer documentation that
00:24:03.690 --> 00:24:10.210
allow you pretty much, very quickly
read about extension you want go
00:24:10.660 --> 00:24:14.910
with a quick start user guide, right?
00:24:15.390 --> 00:24:19.670
There are examples here, and I, by the
way, I choose Glitch, not just because
00:24:20.550 --> 00:24:26.280
it was also one of the easiest choices
because I pretty much maybe get a project
00:24:26.280 --> 00:24:29.615
that I could have just click remix, right?
00:24:31.755 --> 00:24:34.380
And then start develop my own.
00:24:34.380 --> 00:24:36.030
Becky Peltz: So its like
a quick start here, huh?
00:24:36.030 --> 00:24:39.960
They've given you kind of a quick
start for doing your extension.
00:24:40.440 --> 00:24:41.110
Igor Vorobeychik: Exactly.
00:24:41.110 --> 00:24:42.010
Becky Peltz: Giving you a sandbox.
00:24:42.990 --> 00:24:43.650
Igor Vorobeychik: Exactly.
00:24:44.250 --> 00:24:44.550
Yeah.
00:24:44.550 --> 00:24:50.100
So maybe this sample is much
simpler than the one that you see.
00:24:50.100 --> 00:24:55.605
Or actually, my example would be
a combination of lots of samples
00:24:55.620 --> 00:25:00.180
that you will, you may find, and
obviously a bit more customized
00:25:00.180 --> 00:25:01.860
for Cloudinary needs, right?
00:25:01.860 --> 00:25:03.690
Or for, with the Cloudinary in mind.
00:25:04.110 --> 00:25:12.660
But definitely the quick start user
guides here, and by the way, on Cloudinary
00:25:12.660 --> 00:25:18.570
documentation, you will find a lot of
also quickstart user guide samples also
00:25:18.570 --> 00:25:24.360
that use Glitch and some other systems
that just allow you to play with the
00:25:24.360 --> 00:25:31.100
code, how you implement I dunno, Product
Gallery Widget of Cloudinary etc...
00:25:31.120 --> 00:25:37.469
So it's today is very common where
developers can quickly progress
00:25:37.475 --> 00:25:45.284
from documentation to some online
sandbox where they can actually play
00:25:45.290 --> 00:25:49.304
with a tool before they, let's say,
purchase anything or before they
00:25:49.304 --> 00:25:52.364
decide or use this library another.
00:25:52.955 --> 00:25:58.905
So they, yeah, the, there is a very
short path today from documentation
00:25:58.935 --> 00:26:05.025
to actual actual sandbox and the
prototype which our developers can
00:26:05.025 --> 00:26:06.405
build and that's very exciting.
00:26:07.065 --> 00:26:10.125
Sam Brace: Now, Igor, one thing that
I know is a big thing that Becky
00:26:10.125 --> 00:26:14.445
and I always talk about in training,
especially with Cloudinary, and I
00:26:14.445 --> 00:26:16.935
wanna address it in your project
because I think you did a good job
00:26:16.935 --> 00:26:20.375
with being able to handle it well, is
something called environment variables.
00:26:20.380 --> 00:26:24.945
And then basically making sure that's
not exposed to the public users in any
00:26:24.945 --> 00:26:28.845
way through something called a .env file.
00:26:28.895 --> 00:26:30.824
Can you show me how you maybe did that?
00:26:30.830 --> 00:26:34.514
Maybe how Canva looks at that
concept inside of your project?
00:26:35.230 -->
00:26:35.690
Igor Vorobeychik: Yes.
00:26:36.760 --> 00:26:45.590
In order for us to build the extension,
we need at least a few things.
00:26:46.300 --> 00:26:51.900
One of them obviously if we want to push
asset to Cloudinary, we need to store
00:26:51.929 --> 00:26:54.300
Cloudinary application keys, right?
00:26:54.510 --> 00:26:57.650
Basically how we execute the APIs.
00:26:58.790 --> 00:27:06.580
So in my particular case,
what I was doing, I was using
00:27:06.580 --> 00:27:13.650
the .env library, right?
00:27:14.230 --> 00:27:22.080
Which is using env file that allowed
me to store pretty much different keys.
00:27:22.350 --> 00:27:24.570
So this is where I stored my keys.
00:27:24.570 --> 00:27:30.404
Now the interesting thing is if you will
come here and and remix this project.
00:27:31.804 --> 00:27:37.785
To make it of your own or you trying
to view it as a different user, you
00:27:37.785 --> 00:27:40.185
will not going to see this information.
00:27:40.185 --> 00:27:42.445
You see it's stripped out for you.
00:27:43.025 --> 00:27:46.635
To be honest, I was a bit
worried in the beginning.
00:27:46.635 --> 00:27:52.284
That's why I created, and I think in
the blog post I created a, what I called
00:27:52.355 --> 00:28:02.425
public endpoint just for blog purposes
where I actually, in the instructions
00:28:02.940 --> 00:28:07.590
tell you create a .env I just given
an extra layer of security there.
00:28:07.590 --> 00:28:12.600
I was afraid to store it there,
but Glitch takes care of it, right?
00:28:13.050 --> 00:28:14.080
No worries.
00:28:14.550 --> 00:28:20.670
There, let's go back to my
Cloudinary endpoint, and let's
00:28:20.670 --> 00:28:21.990
talk about the second key.
00:28:21.990 --> 00:28:26.730
Why do I have a, another value
here is the Canva client secret.
00:28:27.120 --> 00:28:32.070
So, Canva build with
security in mind, right?
00:28:32.130 --> 00:28:39.095
When you start developing
your application.
00:28:39.210 --> 00:28:44.430
And this is already, I already created,
I can create new app right there in the
00:28:44.430 --> 00:28:52.949
Canva UI so you will see that one of the
things is verification, and this is one of
00:28:52.949 --> 00:28:58.530
the actually things I really like, so your
end point, Canva actually wants to ensure
00:28:58.770 --> 00:29:06.760
that whatever you will develop be secure
for its users, that endpoint will actually
00:29:06.780 --> 00:29:08.880
will implement the security measurements.
00:29:08.880 --> 00:29:16.300
Even if you can run the security
tests and they actually will submit
00:29:17.400 --> 00:29:21.120
various client secret timestamps.
00:29:21.240 --> 00:29:25.260
They will try to fail you and you
should actually, your service should
00:29:25.264 --> 00:29:29.085
return a proper http response.
00:29:29.955 --> 00:29:32.685
If you do not, you will not
be able to, let's say, publish
00:29:32.685 --> 00:29:34.315
such extension, stuff like that.
00:29:34.315 --> 00:29:37.305
Becky
Peltz: Now, I noticed too that
there's a regenerate button there, so
00:29:37.305 --> 00:29:45.585
if anybody was trying to copy down your
key when you showed it with the .env
00:29:45.585 --> 00:29:45.875
Igor Vorobeychik: Obviously.
00:29:46.755 --> 00:29:47.685
Yeah, good point.
00:29:47.905 --> 00:29:48.745
Obviously right now...
00:29:48.745 --> 00:29:50.205
Becky Peltz: Cloudinary
has the same thing.
00:29:51.085 --> 00:29:51.575
Igor Vorobeychik: Yeah.
00:29:51.575 --> 00:29:55.514
Obviously right now everybody will see
this key and we are recording it, so
00:29:55.520 --> 00:29:59.325
obviously this is not something, so
after the call will regenerate a new
00:29:59.325 --> 00:30:01.935
one and then I will be able to use.
00:30:01.940 --> 00:30:04.715
But yes, the security
in mind, this is great.
00:30:06.795 --> 00:30:15.465
This is by the way where I point to
my own endpoint which is on Glitch.
00:30:17.320 --> 00:30:24.685
And basically your project
name will be the entry, right?
00:30:24.705 --> 00:30:29.675
The URL for your endpoint, right?
00:30:30.764 --> 00:30:38.105
And again awesome awesome very on
one hand is simple, but everything
00:30:38.145 --> 00:30:42.795
in Canva is very so first of all
you noticed that I had some user
00:30:42.795 --> 00:30:47.424
interface where I selected the folders.
00:30:47.715 --> 00:30:52.245
Now since Canva wants to control
kind of user experience, right?
00:30:52.250 --> 00:31:01.335
They don't want that different plugins
or extensions look slightly different.
00:31:01.335 --> 00:31:04.815
They want some sort of
unified look and feel, right?
00:31:05.245 --> 00:31:10.455
So they provide you pretty
much with the user interface.
00:31:10.460 --> 00:31:16.245
You just need to to write
couple of endpoints to feed
00:31:16.245 --> 00:31:17.325
the information to the...
00:31:19.005 --> 00:31:21.315
Becky Peltz: You're gonna start
out with an endpoint that is gonna
00:31:21.315 --> 00:31:25.545
go get you something, and then
therefore they're gonna have some
00:31:25.845 --> 00:31:29.205
UI that has lists or a single item.
00:31:29.815 --> 00:31:30.175
Igor Vorobeychik: Yeah.
00:31:30.555 --> 00:31:31.725
And yes, Rebecca.
00:31:31.725 --> 00:31:32.205
Absolutely.
00:31:32.205 --> 00:31:38.805
So when you said word get, and this
is exactly, actually, almost the name.
00:31:38.805 --> 00:31:43.995
Find and get the endpoint name.
00:31:43.995 --> 00:31:50.035
So even from the names of the
endpoint, which Canva ask you to
00:31:50.035 --> 00:31:56.415
actually to write, it's very easy
to, it's not some, special names.
00:31:56.685 --> 00:32:03.275
So for publishing, they using upload by
the way, I found that the upload endpoint.
00:32:03.905 --> 00:32:07.515
Is very similar to
Cloudinary upload, right?
00:32:07.515 --> 00:32:11.355
So it's an upload, which is mean
published, and this is exactly
00:32:11.355 --> 00:32:16.715
what you do when you so a lot of
similarity in terminology you say
00:32:16.715 --> 00:32:23.565
.And then yes, there are there is a
find that's basically something which
00:32:23.795 --> 00:32:26.025
loops through directories, right?
00:32:26.475 --> 00:32:29.535
So I used here a couple
of Cloudinary APIs.
00:32:29.540 --> 00:32:32.195
In this case I used the sub folder API.
00:32:32.195 --> 00:32:43.650
And then eventually there is a get, once
you find what you want, basically you are
00:32:43.730 --> 00:32:49.290
passing back the exact sub folder that you
decide to place your item there, right?
00:32:49.290 --> 00:32:51.239
The final URL.
00:32:51.480 --> 00:32:58.770
Now that was developed before
Cloudinary I think had dynamic folders.
00:32:58.770 --> 00:33:01.860
Now we have dynamic folders that
maybe would do it differently, but
00:33:01.860 --> 00:33:06.150
again, the concept of structure or
place your designs and organize it
00:33:06.179 --> 00:33:09.090
within the DAM still applies here.
00:33:10.409 --> 00:33:14.280
Becky Peltz: Yeah, and it looks like
inside there go and you get these
00:33:14.850 --> 00:33:18.840
resources and then you map them in your,
I think it would be down a little bit
00:33:18.840 --> 00:33:25.279
from what I'm seeing, maybe line 120 or
so where you were just, where you were at.
00:33:26.210 --> 00:33:28.290
You, so down there at Oh, up a little bit.
00:33:28.290 --> 00:33:31.020
I see like line 115 there.
00:33:31.110 --> 00:33:35.759
So you take what you get out of
the subfolder response and you
00:33:35.759 --> 00:33:39.540
map it to their object type id
00:33:39.980 --> 00:33:41.639
Igor Vorobeychik: I will pass, yeah.
00:33:41.639 --> 00:33:45.900
All this information to their object
so they can also build the UI, and
00:33:45.900 --> 00:33:53.870
eventually once something is selected,
then they actually can already call the
00:33:53.870 --> 00:34:02.489
upload API, and pass what was selected
because it was done by different endpoint.
00:34:02.929 --> 00:34:08.280
The define and they get the actual path,
let's say, where you want to store it.
00:34:08.280 --> 00:34:15.930
And actually those few lines
of code are responsible to
00:34:15.930 --> 00:34:17.790
push it to the cloud, right?
00:34:18.180 --> 00:34:22.770
And literally few lines
of code as what we upload
00:34:23.190 --> 00:34:31.650
I'm using the logs a lot in
this just to debug and see
00:34:31.650 --> 00:34:33.900
what information is sent to me.
00:34:34.130 --> 00:34:40.660
That's how I was able to understand
exactly what type of let's say body
00:34:43.415 --> 00:34:45.570
structure they sent to me, right?
00:34:45.600 --> 00:34:48.660
So I could access the
URL of the asset, right?
00:34:49.920 --> 00:34:52.980
I can get a design id, right?
00:34:53.010 --> 00:34:58.140
Canva, design id, which I
decided using as a file name.
00:34:58.560 --> 00:35:02.130
And because I'm using a default
upload preset, even if I will
00:35:02.130 --> 00:35:03.670
reuse the same design id.
00:35:03.720 --> 00:35:10.420
But there is a unique
unique
characters are added by Cloudinary,
00:35:10.440 --> 00:35:13.770
so I do not override, again, I
could have decided to override.
00:35:13.770 --> 00:35:15.900
It depends on the workflow.
00:35:16.260 --> 00:35:21.690
Now right before actually I do
provide some contextual metadata.
00:35:21.695 --> 00:35:26.819
I could have provided me maybe
create structure metadata.
00:35:27.360 --> 00:35:29.640
Now right before, actually...
00:35:29.640 --> 00:35:32.520
Sam Brace: Before you jump to that I
wanna point out something that I love
00:35:32.520 --> 00:35:35.940
what you did there, because if you
look at the context, if this is the
00:35:35.940 --> 00:35:39.740
connection of what we saw earlier in
your demonstration where when you added
00:35:39.740 --> 00:35:45.140
in comments then how did those become
searchable fields within Cloudinary
00:35:45.140 --> 00:35:46.580
when we were trying to find the files?
00:35:46.700 --> 00:35:49.160
And it's because of its plus
message that you see here,
00:35:49.160 --> 00:35:51.170
like the request body message.
00:35:51.170 --> 00:35:54.890
That's that direct connection for
us to know that we're applying
00:35:54.890 --> 00:35:56.120
this as context metadata.
00:35:56.125 --> 00:36:01.760
So it's, that was genius because
you could see people, adding lots of
00:36:01.760 --> 00:36:06.290
things, frankly, in the Canva UI to be
able to explain what's happening there
00:36:06.410 --> 00:36:09.500
and knowing that all of those become
searchable keywords for people to
00:36:09.500 --> 00:36:12.050
find that asset later with Cloudinary.
00:36:12.080 --> 00:36:14.240
That's a great feature
that you added in there.
00:36:14.470 --> 00:36:15.590
It's very smart.
00:36:16.290 --> 00:36:17.250
Igor Vorobeychik: Yeah, thank you.
00:36:17.250 --> 00:36:20.045
And my personal favorite,
actually, tags, right?
00:36:20.795 --> 00:36:23.740
Actually I had added just tags today.
00:36:23.740 --> 00:36:28.350
I when I joined the Cloudinary, I
didn't put much attention on the tags,
00:36:28.350 --> 00:36:32.640
but once I discovered the power of
Cloudinary tags, it just blew my mind.
00:36:32.640 --> 00:36:35.160
And also list APIs that are around it.
00:36:35.430 --> 00:36:42.390
Again, we probably need a different
session on those, but that's
00:36:42.390 --> 00:36:47.405
why I added this in another
line here, just to add the tags.
00:36:47.430 --> 00:36:52.410
And obviously now in this
case, you need to know the tag
00:36:52.440 --> 00:36:53.850
if you search by it, right?
00:36:53.850 --> 00:37:03.150
So if the design id is something
generated by Canva unique and basically
00:37:03.150 --> 00:37:07.590
has no particular structure it would be
hard for you to guess that one, right?
00:37:08.010 --> 00:37:12.840
So you probably, when you are using
the tags, this may be not the best
00:37:13.350 --> 00:37:16.625
field from design id from Canva to use.
00:37:17.375 --> 00:37:24.900
I would use here maybe something
more more human readable or
00:37:24.900 --> 00:37:26.940
understandable or guessable, right?
00:37:26.940 --> 00:37:29.160
Let's say some name or whatever.
00:37:29.160 --> 00:37:34.500
But the idea is that you can apply
tag and then doesn't matter how many
00:37:34.500 --> 00:37:40.230
variations you will create of the same
design, you can search by the same tag
00:37:40.230 --> 00:37:43.200
and then get all of those designs for you.
00:37:43.470 --> 00:37:47.520
So we can obviously very quickly
demonstrate the same, we'll
00:37:47.520 --> 00:37:50.010
just, let's say create v2, right?
00:37:50.490 --> 00:37:51.990
Version two, right?
00:37:52.440 --> 00:37:55.170
And then we will gonna share it again.
00:37:56.340 --> 00:37:59.520
And let's say, I'm gonna put
it even in the samples folder.
00:37:59.520 --> 00:38:02.340
I don't have to even put
it in the same folder.
00:38:02.790 --> 00:38:04.040
Different message.
00:38:04.670 --> 00:38:07.740
By the way, this message
in my case is required.
00:38:07.745 --> 00:38:09.450
You can make it not required.
00:38:09.455 --> 00:38:15.090
Just the configuration of the extension
is on the published extension.
00:38:18.660 --> 00:38:20.490
So now it's saving.
00:38:20.910 --> 00:38:25.290
I want to show you, by the way, that
when we saved all the information,
00:38:25.290 --> 00:38:26.910
I just put it in the log.
00:38:26.915 --> 00:38:28.290
Just easier to see.
00:38:29.190 --> 00:38:40.630
You will see here that I got all
the information from Canva the file
00:38:40.630 --> 00:38:47.009
name, the type, the design id, right?
00:38:47.580 --> 00:38:49.470
So that's the actual tag.
00:38:49.890 --> 00:38:54.649
And then I also store here
response from from Cloudinary.
00:38:57.915 --> 00:38:59.535
Now let's go back.
00:38:59.535 --> 00:39:01.905
Becky Peltz: So just to make it clear,
you, this is where you're calling
00:39:01.905 --> 00:39:08.955
our Cloudinary Upload API and pulling
something from Canva, which is pulled in
00:39:08.955 --> 00:39:12.155
by its design ID into use as file name.
00:39:12.705 --> 00:39:14.615
Igor Vorobeychik: I'm
not pulling it per se.
00:39:14.735 --> 00:39:19.075
It's more common when
it calls the endpoint.
00:39:19.285 --> 00:39:25.365
It passes in the message that passes
message body and message header.
00:39:25.635 --> 00:39:30.135
The header is used for
security to actually do some.
00:39:30.435 --> 00:39:35.025
You will see each method use
validation of this post message.
00:39:35.025 --> 00:39:37.315
That's what you use in the security.
00:39:37.320 --> 00:39:43.255
And remember the key which discuss
Canva id and the body is a JSON
00:39:43.275 --> 00:39:49.455
body object that you can get an
information from Canva take it from
00:39:49.455 --> 00:39:51.465
there and then pass it to Cloudinary.
00:39:51.525 --> 00:39:56.085
That probably would be more accurate
description of what happened.
00:39:56.355 --> 00:40:02.985
So if we go right now back to Cloudinary
to the, to
Cloudinary and maybe go
00:40:02.985 --> 00:40:08.175
to, I don't know, to advance search
and maybe right now know the tag, but
00:40:08.405 --> 00:40:11.265
let's say I'm just gonna apply the tag.
00:40:11.985 --> 00:40:14.115
So now I have two designs, right?
00:40:14.745 --> 00:40:18.535
Now this is v2 and this is
actually marked as a new.
00:40:18.555 --> 00:40:20.535
We see the nice preview here.
00:40:20.535 --> 00:40:23.685
This is v2, this is v1, right?
00:40:23.715 --> 00:40:26.655
Or basically our first creation, right?
00:40:27.045 --> 00:40:33.285
They have slightly different, I think
message one has a test and another
00:40:33.285 --> 00:40:35.445
has, ah, they both have tests.
00:40:35.475 --> 00:40:37.425
I guess I, in both cases, wrote tests.
00:40:37.815 --> 00:40:42.755
But the idea is that I
have two variations, right?
00:40:43.725 --> 00:40:46.845
But they all belong to the same design Id.
00:40:46.845 --> 00:40:49.995
Then maybe later I can do
something about it, right?
00:40:50.865 --> 00:40:55.815
Maybe in the future I will
open up Canva from Cloudinary
00:40:55.815 --> 00:40:59.175
and load the design id, right?
00:40:59.745 --> 00:41:04.215
Load design id, I just given the ideas
where we can bring it to the future.
00:41:05.275 --> 00:41:13.725
The most important that you can
tag, you can affect your file name.
00:41:14.505 --> 00:41:16.035
You can do lots of stuff.
00:41:16.395 --> 00:41:21.375
You can organize your content and most
important, you publish in it, in the
00:41:21.375 --> 00:41:23.595
multi-CDN environment of Cloudinary.
00:41:23.895 --> 00:41:29.445
And this later can be served in the
most optimal optimized format and
00:41:29.955 --> 00:41:32.825
quality, any type of transformation.
00:41:33.825 --> 00:41:37.170
Sam Brace: One thing I wanna do, let's
jump back to Glitch for a second cause I
00:41:37.170 --> 00:41:40.680
do want to unpackage one more thing that
happens to be in your code that I think
00:41:40.680 --> 00:41:44.370
is gonna be very helpful for people when
they're working between these two systems.
00:41:44.550 --> 00:41:46.860
Scroll down until we see
resource type, I think it's
00:41:46.865 --> 00:41:48.620
line 44 if I remember correctly.
00:41:50.300 --> 00:41:50.730
There we go.
00:41:50.790 --> 00:41:51.460
See it exposed.
00:41:51.620 --> 00:41:53.920
So Line 44.
00:41:53.990 --> 00:41:54.300
Resource type.
00:41:54.300 --> 00:41:58.035
So as we know, because we work
at Cloudinary, This is where
00:41:58.245 --> 00:42:00.285
we're saying, is this an image?
00:42:00.315 --> 00:42:02.625
Is this a video or is this a raw file?
00:42:02.625 --> 00:42:06.285
And raw file could be any file tape
that is not able to be transformed,
00:42:06.285 --> 00:42:09.975
meaning we're not gonna resize it
or crop it or change its format
00:42:10.275 --> 00:42:11.725
in other things that we can do.
00:42:11.955 --> 00:42:15.625
There's hundreds of things we can do
with it, but it's to say what I like
00:42:15.640 --> 00:42:19.510
that you've done here though, is you've
called our auto resource type situation.
00:42:19.510 --> 00:42:23.530
Because when someone is working with
a system like Canva, they're gonna be
00:42:23.530 --> 00:42:25.150
bringing forward images like we saw.
00:42:25.150 --> 00:42:28.990
We're gonna be bringing forward
JPEGs, PNGs that were created in
00:42:28.990 --> 00:42:32.170
Canva, and then make sure we're
deliverable inside of Cloudinary.
00:42:32.440 --> 00:42:36.340
But what's also possible with a system
like Canva is you might be bringing
00:42:36.340 --> 00:42:41.380
forward documents such as maybe a
PowerPoint file or something that's going
00:42:41.385 --> 00:42:44.800
to be, we consider them images the way
that we work from the Cloudinary, but
00:42:44.805 --> 00:42:47.020
PDFs could be considered documents too.
00:42:47.200 --> 00:42:50.410
So it's to say you don't have to think
about what's coming from a system, it'll
00:42:50.410 --> 00:42:54.100
just automatically detect it and make sure
it applies the appropriate resource type.
00:42:54.160 --> 00:42:57.310
So I thought that was very smart,
once again to make sure this was
00:42:57.490 --> 00:43:00.550
future-proofing, this, making
sure that all types of users could
00:43:00.555 --> 00:43:03.970
benefit from this when they're
connecting these two systems together.
00:43:03.975 --> 00:43:05.430
So that was a good call on your code.
00:43:06.160 --> 00:43:06.290
Igor Vorobeychik: Yeah.
00:43:06.290 --> 00:43:07.005
Thank you Sam.
00:43:07.005 --> 00:43:09.315
Yeah, and this was just for simplicity.
00:43:09.315 --> 00:43:12.045
You don't have to think what
type of the asset you have.
00:43:12.045 --> 00:43:18.585
And as you saw in when we are
actually posting something or let's
00:43:18.585 --> 00:43:27.715
say, and sharing, we can decide on
different type of format, right?
00:43:28.185 --> 00:43:31.185
And suddenly it can be
become a PDF, right?
00:43:32.675 --> 00:43:38.955
And obviously in order not to have
some if else statements or others,
00:43:38.955 --> 00:43:44.685
and maybe even on Cloudinary, you
can use PDF as image and as raw.
00:43:45.105 --> 00:43:51.855
So that's where maybe you will need
eventually get into the, those case
00:43:51.855 --> 00:43:57.885
or if statements, if you want really
let's say taking control, right?
00:43:57.915 --> 00:44:00.965
How you want those files be
accepted by Cloudinary, right?
00:44:02.025 --> 00:44:07.305
But if you don't, then auto is
a very good option to, to use.
00:44:08.235 --> 00:44:12.705
So now actually I'm gonna get back,
and this is going to be in this
00:44:12.705 --> 00:44:19.125
case could be a PDF, but also we are
going go to Cloudinary right now.
00:44:19.125 --> 00:44:28.075
Let's see, we're gonna go through
the Cloudinary and reload or refresh
00:44:28.115 --> 00:44:31.935
or now we have another asset, right?
00:44:32.655 --> 00:44:34.904
Image format, PDF, right?
00:44:35.884 -->
00:44:41.400
So, that's just the power of Cloudinary.
00:44:41.790 --> 00:44:42.390
Sam Brace: It is.
00:44:42.880 --> 00:44:46.890
Now one thing that I'm missing right
now in the code situation and, I'd love
00:44:46.890 --> 00:44:50.280
for you to see it cause we've referenced
this a few times, is this f_auto and
00:44:50.280 --> 00:44:51.990
q_auto that we keep talking about.
00:44:51.990 --> 00:44:56.850
And of course f_auto means automatic
format, so that way when you're getting
00:44:56.850 --> 00:45:03.090
these as JPEGs or PNGs from Canva,
we at Cloudinary can deliver them
00:45:03.150 --> 00:45:05.190
in the most optimal format possible.
00:45:05.190 --> 00:45:09.720
So it may not stay as that JPEG or
PNG, it might become a WebP as an
00:45:09.720 --> 00:45:12.960
example, or it might stay as that
if we see that as most optimal.
00:45:12.960 --> 00:45:16.680
But it's allowing Cloudinary to
help make the choice so that way the
00:45:16.680 --> 00:45:20.370
content is as lightweight as possible,
but it's only based on format.
00:45:20.400 --> 00:45:25.010
But, and q_auto is similar when it comes
to the compression side, making sure that
00:45:25.300 --> 00:45:29.125
we're providing the most optimal level
of compression based on the person's
00:45:29.155 --> 00:45:32.365
browser and and frankly, device as well.
00:45:32.725 --> 00:45:36.415
But what I'm wondering is how
are you applying this f_auto
00:45:36.415 --> 00:45:37.985
q_auto inside of your code?
00:45:38.525 --> 00:45:41.335
What's making that be
appended into the URL?
00:45:42.295 --> 00:45:42.585
Igor Vorobeychik: Sure.
00:45:43.515 --> 00:45:49.435
In my particular, there is various
techniques that you can use, right?
00:45:49.795 --> 00:45:56.155
I decided to use actually
another Cloudinary method, right?
00:45:56.335 --> 00:46:01.015
That is basically the URL the method
that allows me to build the URL.
00:46:01.045 --> 00:46:04.075
We also have a method that
allows you actually to build
00:46:04.105 --> 00:46:06.115
the whole image tag, right?
00:46:06.115 --> 00:46:12.115
If we want the whole image tag, I use
the URL here and within the URL, once I
00:46:12.175 --> 00:46:17.005
uploaded to Cloudinary and got back as
part of the result, a public id, right?
00:46:18.165 --> 00:46:24.285
If you remember, I told you that I
allow here to use a dynamic upload
00:46:24.285 --> 00:46:28.325
presets, which actually generates the
unique name for these uploaded files.
00:46:28.325 --> 00:46:29.835
It adds some characters.
00:46:30.105 --> 00:46:34.275
So I do not know, at this stage,
what will be the public id.
00:46:34.275 --> 00:46:36.045
That's why I need the response.
00:46:36.315 --> 00:46:39.855
Once the Cloudinary uploaded
and I'm gonna get the public id.
00:46:39.855 --> 00:46:42.935
Now, once I get the public
id, I can build the URL.
00:46:43.295 --> 00:46:48.435
And here again you can use
any of your requirements.
00:46:48.435 --> 00:46:52.545
I do here very bare minimum,
00:46:52.605 --> 00:46:58.815
I saying use version I don't have
to use version if I don't want to.
00:46:59.365 --> 00:47:07.000
I would like to use transformation.
00:47:07.020 --> 00:47:10.060
In this case, I'm saying I
would like to use quality fetch
00:47:10.110 --> 00:47:12.230
format, which is auto, right?
00:47:12.540 --> 00:47:16.590
I could have specified particular
format I want to use, right?
00:47:16.860 --> 00:47:21.240
I could have specified particular
quality I would like to use, right?
00:47:21.750 --> 00:47:32.570
I could have add all hundreds different
transformations which Cloudinary
00:47:32.570 --> 00:47:34.290
supports and generate URL, right?
00:47:34.800 --> 00:47:40.530
So this is something that can be I'm not
using here again, that was build when
00:47:40.530 --> 00:47:43.080
I just step into the Cloudinary world.
00:47:43.080 --> 00:47:45.510
You can use here name
transformations, right?
00:47:45.540 --> 00:47:51.070
Which is very powerful because
then you actually give something
00:47:51.360 --> 00:47:55.525
of another like encapsulation.
00:47:55.545 --> 00:47:59.625
So basically let's say if I would add
here a name transformation, then I could
00:47:59.625 --> 00:48:04.065
have used Cloudinary and build very
complex name transformation, right?
00:48:04.635 --> 00:48:09.555
And give it to the no code user, right?
00:48:09.555 --> 00:48:12.705
The user doesn't have to write
the code maybe later to change
00:48:12.705 --> 00:48:14.475
this name transformation, right?
00:48:14.475 --> 00:48:18.805
And use Cloudinary transformation
builder for that, right?
00:48:19.435 --> 00:48:24.105
Sam Brace: Hold on, Igor, I mean as
big as you can make this, the fact
00:48:24.105 --> 00:48:27.585
that you are even able to apply
just these two is so powerful too.
00:48:27.585 --> 00:48:32.195
So it's to say yeah, you can
always iterate, but this is pretty
00:48:32.475 --> 00:48:36.555
impressive in itself to be able
to add f_auto q_auto to every URL.
00:48:36.855 --> 00:48:39.555
And then Becky, make sure I'm
understanding this correctly.
00:48:39.560 --> 00:48:44.295
So if I'm looking at this flow that we
have here, we have it where we have the
00:48:44.300 --> 00:48:46.635
endpoint that's using the Upload API.
00:48:47.490 --> 00:48:50.730
And then we're calling, is this
the URL helper method that's taking
00:48:50.730 --> 00:48:54.540
place for all of this f_auto q_auto
and URL generation take place?
00:48:55.770 --> 00:48:56.220
Becky Peltz: Yeah.
00:48:56.220 --> 00:48:56.640
Yeah.
00:48:56.640 --> 00:49:01.830
So the Uploader, the API returns
a promise and Igor's dealing that,
00:49:02.190 --> 00:49:06.750
dealing with that, using the, then so
he gets the upload result back after
00:49:06.750 --> 00:49:11.960
the upload is successfully done and now
he has access to the upload response,
00:49:11.965 --> 00:49:14.640
which contains lots of information.
00:49:15.240 --> 00:49:18.870
And some of that information
is that public id.
00:49:18.875 --> 00:49:23.970
So upload Result public ID is the
unique identifier from Cloudinary
00:49:24.030 --> 00:49:27.960
upload result format was the original
format that he used to upload
00:49:28.440 --> 00:49:30.480
version is the result version.
00:49:30.690 --> 00:49:36.570
So he's able to pull in data out of the
response and use that to generate a unique
00:49:36.570 --> 00:49:42.570
URL from the Cloudinary URL and there are
other kind of, I call 'em helper methods.
00:49:42.570 --> 00:49:43.590
This one builds a URL.
00:49:43.595 --> 00:49:45.780
There's one that will
build you an image tag.
00:49:45.960 --> 00:49:48.420
There's one that will build
you a video tag and they
00:49:48.425 --> 00:49:50.550
basically just produce strings.
00:49:50.610 --> 00:49:55.500
And then once you request that
string in your browser, it goes
00:49:55.500 --> 00:49:59.170
through a lot of processing and
eventually gets served off of a CDN.
00:49:59.370 --> 00:50:04.380
So lot, a lot of things going on
once you've got a Cloudinary URL
00:50:04.410 --> 00:50:05.910
that you can take advantage of.
00:50:07.110 --> 00:50:07.560
Sam Brace: I love it.
00:50:07.600 --> 00:50:09.330
This is absolutely fantastic.
00:50:09.930 --> 00:50:13.200
Igor, you of course you wrote this or
there's so much we can unpackage, but
00:50:13.410 --> 00:50:16.680
whatever big things do we wanna make sure
that people understand, like maybe was
00:50:16.680 --> 00:50:18.630
there any roadblocks that you came across?
00:50:18.630 --> 00:50:22.560
Was there any big learnings that you came
when you were building this project that
00:50:22.560 --> 00:50:26.930
is worth unpackaging for the audience?
00:50:26.930 --> 00:50:29.700
Igor Vorobeychik: Some little
things which I found is maybe
00:50:29.700 --> 00:50:36.060
that I couldn't actually find in
documentation or wasn't wasn't clear.
00:50:36.750 --> 00:50:45.600
For example, when I used the subfolders
API of Cloudinary the Cloudinary has
00:50:45.600 --> 00:50:51.540
also root folders of something API,
which I didn't want to use both.
00:50:51.570 --> 00:50:55.920
And then I found the way, if I will just
pass the back slash, that's actually give
00:50:55.925 --> 00:50:58.720
me a route, the little things like that.
00:50:59.940 --> 00:51:06.600
Also I found a bit not a clunky,
but I spent some time on the not
00:51:06.600 --> 00:51:13.350
necessarily on Cloudinary end, but on
the Canva around the validation, right?
00:51:13.410 --> 00:51:18.760
All of these validation of security
which implemented here, which I
00:51:18.760 --> 00:51:21.630
advise to go and look at, right?
00:51:22.010 --> 00:51:23.480
A bit more closely.
00:51:25.470 --> 00:51:26.100
What else?
00:51:26.100 --> 00:51:34.200
The rest is a, I wouldn't say
that other things are basically
00:51:35.010 --> 00:51:36.990
wasn't that hard to implement.
00:51:36.990 --> 00:51:44.110
And again even if you new to node JS,
if you are new to Cloudinary, new to
00:51:44.110
--> 00:51:50.850
Canva, you should using this blog and
those few resources put this together
00:51:50.850 --> 00:51:57.705
in several days and already have
your own Canva published extension.
00:51:57.885 --> 00:52:00.675
Now, my extension is not public extension.
00:52:00.975 --> 00:52:08.625
This extension is of the it's
a team team extension, right?
00:52:08.925 --> 00:52:13.745
So when you publish it, you basically
do not have to go through scrutiny
00:52:13.745 --> 00:52:18.615
of the Canva, which should make it
available for millions of users.
00:52:18.615 --> 00:52:22.695
Obviously there are there are some
things that you will have to fulfill,
00:52:23.025 --> 00:52:29.345
but so it's a bit easier to build
your prototype to play with it.
00:52:29.825 --> 00:52:34.485
And then obviously expose
it within your organization.
00:52:34.905 --> 00:52:37.630
So that's what I was using here.
00:52:37.690 --> 00:52:40.875
I found this a very easy way of.
00:52:42.165 --> 00:52:45.105
If you, let's say, building a
new version, which you wanna
00:52:45.105 --> 00:52:47.025
point to, different end point.
00:52:47.025 --> 00:52:50.980
Maybe this is fraud and you
wanna point to staging, right?
00:52:50.980 --> 00:52:52.715
Or maybe you have pro too.
00:52:53.125 --> 00:52:57.465
Canva have out of the
box, create new version.
00:52:59.535 --> 00:53:04.065
Now it's become draft of
the new version, right?
00:53:04.065 --> 00:53:07.475
Which you maybe can repoint
to some other place.
00:53:08.404 --> 00:53:16.875
You maybe even want to let's say, remember
I told you I'm forcing the message, right?
00:53:16.965 --> 00:53:19.245
Maybe you don't wanna
force the message, right?
00:53:20.315 --> 00:53:26.145
Maybe you want to use different
not allow, maybe PowerPoint
00:53:26.145 --> 00:53:28.725
whatever extension, right?
00:53:28.755 --> 00:53:34.265
Maybe you want to reconfigure
it as well, right?
00:53:34.950 --> 00:53:39.600
And the interesting thing is using the
same client secret, if you using the same
00:53:39.600 --> 00:53:43.830
endpoint, you just may be messing up with
the descriptions with the UI, it doesn't
00:53:43.830 --> 00:53:46.140
have to be changed within the code, right?
00:53:46.650 --> 00:53:47.800
So those type of things.
00:53:48.390 --> 00:53:50.400
And then you can even preview it.
00:53:51.570 --> 00:53:58.860
So right now I actually can maybe
preview and you see now, I mean they
00:53:58.860 --> 00:54:02.400
have right now two names I probably
should have named the second one.
00:54:02.405 --> 00:54:03.750
This might be different.
00:54:04.200 --> 00:54:11.400
But if I'll choose this one I by mistake,
choose the designer, which I need to buy.
00:54:11.670 --> 00:54:17.620
So let's use something free and choose.
00:54:17.720 --> 00:54:21.250
And you will see right now that I
don't have this PowerPoint, right?
00:54:22.030 --> 00:54:22.620
Selected.
00:54:22.680 --> 00:54:27.360
I don't have this message as
something I have to use, right?
00:54:27.870 --> 00:54:30.690
And in this case, I'm using the same.
00:54:31.080 --> 00:54:33.330
So actually there is some error.
00:54:33.330 --> 00:54:34.950
I need to go dive.
00:54:34.950 --> 00:54:42.030
Maybe there was actually change in these
secret key and et cetera, et cetera.
00:54:42.210 --> 00:54:43.710
Sam Brace: Right, but
you can test it and...
00:54:43.710 --> 00:54:44.610
Igor Vorobeychik: Yeah, exactly.
00:54:44.610 --> 00:54:45.150
Exactly.
00:54:45.150 --> 00:54:47.940
And this is where the logs
are coming into place.
00:54:48.150 --> 00:54:52.170
And there I should, or some
public ID invalid name.
00:54:52.170 --> 00:54:54.240
So actually it was Cloudinary error.
00:54:54.800 --> 00:55:00.780
Probably not do doing a good job
on the on these naming convention.
00:55:01.110 --> 00:55:05.480
But again, this is how you are
debugging the stuff actually
00:55:05.640 --> 00:55:07.320
intentionally wanted to show you.
00:55:07.320 --> 00:55:15.460
So this is how you getting help from what
are doing and perfecting your integration.
00:55:15.819 --> 00:55:21.690
And the great thing is the the Canva
also makes it very easy for you
00:55:21.690 --> 00:55:23.910
to basically publish your draft.
00:55:23.910 --> 00:55:26.580
Now I have my new draft version, right?
00:55:27.090 --> 00:55:29.999
Which I can continue to edit, right?
00:55:30.819 --> 00:55:36.090
Or maybe I want to delete it, and once
I'm done, I will be able to publish
00:55:36.090 --> 00:55:40.690
it and it'll override my extension
because this is a new version of v2.
00:55:41.395 --> 00:55:47.485
So, again love what Canva did around
extension love what they did around
00:55:47.915 --> 00:55:53.370
around security and even more excited
about the Cloudinary, what we now,
00:55:53.370 --> 00:56:00.130
how we can help all these millions of
Canva users to publish their designs
00:56:00.670 --> 00:56:09.180
to deliver them across the globe in
the most unified and optimized way.
00:56:09.180 --> 00:56:11.715
Sam Brace: And to encapsulate everything.
00:56:11.715 --> 00:56:15.885
What I am really happy about of course,
is that not only will people have this
00:56:15.885 --> 00:56:20.295
podcast episode to be able to reference,
to understand all of the ins and outs of
00:56:20.655 --> 00:56:25.495
doing this, but you also have a fantastic
blog post that's published on Cloudinary's
00:56:25.515 --> 00:56:28.125
main blog that highlights all of this.
00:56:28.125 --> 00:56:33.735
It has clickable, usable links to be able
to get access to a lot of this so you
00:56:33.735 --> 00:56:37.905
can remix exactly everything that you've
gone ahead and built as anybody that's
00:56:37.905 --> 00:56:39.755
working between these two platforms.
00:56:39.760 --> 00:56:44.385
So it's a, you have plenty of resources
available to the world to be able to
00:56:44.385 --> 00:56:50.115
make this Canva, Cloudinary connection,
a real thing within their organizations.
00:56:50.145 --> 00:56:52.845
So you've really empowered a
lot of developers here at Igor.
00:56:52.905 --> 00:56:53.715
This is fantastic.
00:56:54.315 --> 00:56:54.675
Igor Vorobeychik: Thank you.
00:56:55.725 --> 00:56:56.235
Excellent.
00:56:56.265 --> 00:56:59.655
Sam Brace: So Igor, we're gonna let
you go, but have a wonderful day.
00:56:59.715 --> 00:57:01.125
This is wonderful to have you here.
00:57:01.275 --> 00:57:03.285
And then me and Becky are gonna
say some nice things about you.
00:57:03.285 --> 00:57:05.205
So yeah, have a wonderful one, Igor.
00:57:05.444 --> 00:57:06.205
Igor Vorobeychik: Thank you, Sam.
00:57:06.305 --> 00:57:07.095
Thank you, Becky.
00:57:07.275 --> 00:57:07.845
Have a good day.
00:57:07.935 --> 00:57:08.705
Yeah, bye-bye.
00:57:08.815 --> 00:57:11.105
You too.
00:57:11.585 --> 00:57:13.665
Sam Brace: Becky, what's
your key takeaways here?
00:57:13.665 --> 00:57:17.265
There's a lot of things that we can
unpackage of this project, but what are
00:57:17.265 --> 00:57:18.545
the things that are standing out to you?
00:57:19.855 --> 00:57:24.525
Becky Peltz: I think the way that the
documentation for Canva is set up,
00:57:24.645 --> 00:57:26.660
that they give you a Glitch starter.
00:57:26.710 --> 00:57:30.185
You can take that and then just play
around with all of the different,
00:57:31.255 --> 00:57:37.005
certainly Igor's talk, generate a lot
of ideas on built based on what he
00:57:37.005 --> 00:57:40.545
did and then what else you can do as
far as you could maybe start bringing
00:57:40.545 --> 00:57:46.755
video in then you could bring, stuff
from Cloudinary into Canva and just
00:57:46.755 --> 00:57:49.325
lots of different permutations there.
00:57:50.565 --> 00:57:52.415
I think.
00:57:52.845 --> 00:57:54.810
It looks like a fun playground.
00:57:55.770 --> 00:57:56.040
Sam Brace: I agree.
00:57:56.040 --> 00:57:59.160
Becky Peltz: I would probably look
into, building out some serverless
00:57:59.610 --> 00:58:03.300
functions too, because as long as they
all are posted at the same domain and
00:58:03.300 --> 00:58:07.700
you have that base URL, you can do
that in a serverless mode as well.
00:58:07.700 --> 00:58:11.880
So lots of interesting paths that
a developer might take with this.
00:58:12.720 --> 00:58:13.560
Sam Brace: Yeah, I agree.
00:58:13.560 --> 00:58:17.700
And I think you're touching on something
that I think is really inspiring to me
00:58:17.790 --> 00:58:22.230
and it's a move that I've seen Cloudinary
starting to do with more quick starts,
00:58:22.230 --> 00:58:25.260
more ways to try it, exploring code.
00:58:25.560 --> 00:58:30.210
And Canva has something very like-minded
where we have a lot of ours tied to
00:58:30.210 --> 00:58:34.620
Repl.it, which is a similar service with
some differences of course, but similar
00:58:34.620 --> 00:58:36.120
service to what Glitch is providing.
00:58:36.450 --> 00:58:39.510
And we have a lot of that in our
documentation for people to try it out,
00:58:39.510 --> 00:58:43.560
to actually, let me quickly show our
audience what I'm talking about here,
00:58:43.560 --> 00:58:47.130
but if we pop over to our documentation,
you'll see that we have quick starts,
00:58:47.130 --> 00:58:52.930
very similar to what they had here, where
we can test out the node SDKs right from
00:58:52.950 --> 00:58:58.590
this area with a overall similar service
to what they're providing for this.
00:58:58.590 --> 00:59:01.890
So people can expand and try
things out in a safe space.
00:59:02.220 --> 00:59:07.290
So it is where I like that Canva and
Cloudinary are doing something very
00:59:07.290 --> 00:59:12.270
similar in that space, but it's where
they're also encouraging everything that
00:59:12.270 --> 00:59:17.160
Igor did is they want more developers to
create connections between this system and
00:59:17.160 --> 00:59:19.450
that system and the other system to Canva.
00:59:19.720 --> 00:59:24.540
So if it's inspired from a business
perspective that they've embraced
00:59:24.540 --> 00:59:27.930
the creator and the developer
within their overall product,
00:59:27.930 --> 00:59:29.110
which is very very cool to see.
00:59:30.050 --> 00:59:30.460
Yeah.
00:59:30.880 --> 00:59:35.850
And I think a good developer experience
is the one where there's less code.
00:59:36.180 --> 00:59:41.340
So anytime they can supply you
with a nice set of code that you
00:59:41.340 --> 00:59:46.000
can just put your specialty stuff
on, that's a good experience.
00:59:46.070 --> 00:59:49.980
And they're definitely in the
right place as Cloudinary is too.
00:59:50.700 --> 00:59:51.210
It is.
00:59:51.210 --> 00:59:55.840
And it was smart for Canva to use
Node as a starter, frankly, because,
00:59:56.250 --> 00:59:59.490
think a lot of our coursework was
written in Node intentionally, because
00:59:59.640 --> 01:00:05.490
it is a framework, it is a way for
people to be able to do things truly
01:00:05.490 --> 01:00:08.790
front end, back end because of the
JavaScript connection between all of it.
01:00:09.120 --> 01:00:13.570
So it is where it's, if it's a smart
space for them to be in and, but it's
01:00:13.590 --> 01:00:18.150
also to say that if someone were to try
to replicate what Igor did, possibly
01:00:18.150 --> 01:00:20.260
in other SDKs, it might be possible.
01:00:20.265 --> 01:00:23.080
So version, there's lots of
connectivity there too, which is
01:00:23.430 --> 01:00:23.840
Becky Peltz: Yeah.
01:00:24.440 --> 01:00:29.990
Just go home and talk to Chat
GPT-4 and he'll give you probably
01:00:30.090 --> 01:00:31.500
three or four ways to do it.
01:00:32.490 --> 01:00:35.550
Sam Brace: Oh man, we like, it
wouldn't be a podcast if we didn't
01:00:35.550 --> 01:00:37.080
mention Chat GPT in it, right?
01:00:39.270 --> 01:00:40.070
No, absolutely.
01:00:40.850 --> 01:00:44.430
But great stuff and to
highlight of course, everything
01:00:44.430 --> 01:00:45.600
that we have talked about.
01:00:45.600 --> 01:00:49.980
Once again, on
cloudinary.com/blog,
you'll see Igor's post, we'll have that
01:00:49.980 --> 01:00:53.520
of course in the show notes with all the
associated links if you wanna follow along
01:00:53.520 --> 01:00:54.960
with everything that happened to be there.
01:00:55.410 --> 01:00:57.510
So wonderful space for you to be at.
01:00:58.230 --> 01:01:01.590
And of course, before we do let our
audience go, we would do wanna point
01:01:01.590 --> 01:01:05.670
out that this is not the only Cloudinary
podcast episode that has been out there.
01:01:05.670 --> 01:01:09.180
We have many, we have years now
that we have produced of this.
01:01:09.180 --> 01:01:12.960
So you can always find every
and all episodes of the
01:01:12.990 --> 01:01:14.400
podcast programs we produce.
01:01:14.405 --> 01:01:18.600
There's two: DevJams, as well as MX
Matters, and you can see those at
01:01:18.600 --> 01:01:23.610
cloudinary.com/podcasts and that's where
you can dive into the episodes, watch
01:01:23.610 --> 01:01:29.370
and listen, and also have links to any
of the associated podcast services that
01:01:29.375 --> 01:01:34.980
we happen to be subscribed to, such as
Spotify, Apple Podcasts, Google Podcasts,
01:01:35.100 --> 01:01:39.030
YouTube, as well as our own training
resource, the Cloudinary Academy.
01:01:39.510 --> 01:01:44.640
And without making sure that we don't
continue the conversations, we have to
01:01:44.640 --> 01:01:48.840
continue the conversations and if someone
has questions about anything we've covered
01:01:48.840 --> 01:01:52.950
at any program, or frankly, anything
that is tickling their brain about what
01:01:52.950 --> 01:01:57.540
Cloudinary can provide, they can always
go to community.cloudinary.com, where
01:01:57.540 --> 01:02:01.770
you'll find our overall community forum
and it's associated Discord server for
01:02:01.770 --> 01:02:03.420
you to continue with conversations.
01:02:04.050 --> 01:02:10.550
So this is all good stuff
now, Becky, any final thoughts
01:02:10.550 --> 01:02:12.390
about the Igor conversation?
01:02:14.040 --> 01:02:14.420
Becky Peltz: No.
01:02:14.420 --> 01:02:18.825
It's great to have Igor on and to
be able to share some of the work
01:02:18.825 --> 01:02:20.685
that our own employees are doing.
01:02:21.385 --> 01:02:24.795
It's, there's a lot of creativity
in the company and it's nice
01:02:24.795 --> 01:02:26.535
to be able to pass that around.
01:02:27.315 --> 01:02:28.005
Sam Brace: Absolutely.
01:02:28.185 --> 01:02:28.855
Absolutely.
01:02:30.155 --> 01:02:34.205
One last thing that we do wanna
point out here is, this is actually
01:02:34.525 --> 01:02:37.065
somewhat of a bittersweet episode
for us, because this is gonna be
01:02:37.095 --> 01:02:40.905
Becky Peltz last episode on DevJams.
01:02:40.925 --> 01:02:44.100
Becky's moving on to some brand new
adventures, which we're really excited
01:02:44.120 --> 01:02:47.715
for her to be a part of, and it's been
amazing to have her as my co-host since
01:02:47.720 --> 01:02:49.845
we've launched this overall effort.
01:02:49.845 --> 01:02:53.385
But it is to say that this will
be the last time you have Becky
01:02:53.385 --> 01:02:55.680
on as our official co-host.
01:02:56.180 --> 01:03:00.225
Becky, I wanted to say thank you for the
many years of helping our developers,
01:03:00.225 --> 01:03:04.005
helping out the overall community
to understand what is available with
01:03:04.005 --> 01:03:06.345
Cloudinary and expanding their knowledge.
01:03:06.345 --> 01:03:08.175
So thank you for being a part of this.
01:03:08.910 --> 01:03:11.850
Becky Peltz: Hey, it's been my
pleasure and I'm happy to be here.
01:03:12.190 --> 01:03:16.280
I'll have to check out what
you've got going on next time.
01:03:17.550 --> 01:03:18.060
Sam Brace: Absolutely.
01:03:18.450 --> 01:03:19.110
Absolutely.
01:03:19.290 --> 01:03:22.950
And that's to say that we are still
absolutely continuing the DevJams program.
01:03:22.950 --> 01:03:27.270
We'll be out once again in the next
few weeks with a future episode where
01:03:27.275 --> 01:03:31.080
we're talking with another developer
that is doing some amazing, innovative,
01:03:31.080 --> 01:03:33.960
inspiring things with the overall service.
01:03:33.960 --> 01:03:37.290
So don't worry, even though Becky won't
be with us, we're still gonna be here.
01:03:37.290 --> 01:03:39.960
And of course, hopefully, Becky,
you're cheering for us from
01:03:39.960 --> 01:03:41.550
sidelines on this overall case too.
01:03:42.720 --> 01:03:43.140
Excellent.
01:03:43.230 --> 01:03:46.800
So on behalf of everybody here at
Cloudinary, thank you for being a
01:03:46.800 --> 01:03:50.430
part of this episode and learning more
about what our services can provide
01:03:50.730 --> 01:03:52.950
and we'll see you at the next one.
01:03:53.400 --> 01:03:54.060
Take care everybody.