A powerful media API for websites and mobile apps alike, Cloudinary enables developers to efficiently manage, transform, optimize, and deliver images and videos through multiple CDNs. Ultimately, viewers enjoy responsive and personalized visual-media experiences-irrespective of the viewing device.
There are many situations where partners send you photos, video footage, art, or any other media that you then have to upload to Cloudinary. This process can lead to extra, time-consuming manual work and result in a lack of accountability.
This project is designed to build you a minisite without adding users, writing a single line of code, or sending a ticket to IT - freeing you up to do other higher-value work.
(For Developers: Go ahead and use the Cloudinary Upload Widget or upload files using AJAX techniques. If that applies to you, feel free to skip the rest.)
You'll need a Cloudinary account.
Don't have one? You can create a free Cloudinary account here.
Use the console to define the options that apply to your uploads. You’ll only need to modify three fields to get started, but there is much more functionality and value that can be explored in the documentation.
- Upload preset name - Used to identify your preset; not visible in the minisite but accessible via HTML inspection.
- Signing Mode - Change to unsigned. This allows unauthenticated users to upload assets.
- Folder - Specify the Media Library folder where you would like to have the uploaded assets. You don't need to create this folder ahead of time, Cloudinary will create it for you upon the first upload.
NOTE: Do not point the unsigned uploads to any sensitive folder, like the uploads_minisite. Also, use folder permissions to limit other users in your organization from deleting or creating unauthorized minisites.
Edit the template sample_uw.json from this repo. At a minimum, edit these fields:
- title
- subtitle
- uploadPreset - the one you used in the previous step
- disclaimer
- editable_smd
There are plenty of additional options to adjust, like colors, fonts, and upload sources in the template. Save the template using a meaningful public name, for example, “photographers.json”. Any name is valid, as long as the extension is kept “.json”. Create a top-level folder named “uploads_minisite” in your environment. Upload the JSON file to this folder. Adjust the public_id of the JSON file to match the folder structure, e.g., “uploads_minisite/photographers.json”.
If you’ve included editable_smd in your configuration, you can pass values via the URL, like so: editable_smd: ['photographer'] https://upload-minisite.cloudinary.us/<your environment id>/photographers?photographer=Jane
Make sure that you can access the JSON from a web browser as https://res.cloudinary.com/<your env id>/raw/upload/uploads_minisite/photographers.json
Immediately see the results at https://upload-minisite.cloudinary.us/<your environment id>/photographers.
This is a live upload minisite demo that was created by uploading this JSON to Cloudinary.