colbyfayock
Joined 7 years ago
Karma
95
Submissions
45
Member since
Oct 18
Recent submissions
Comment · 2 years ago
Comment · 2 years ago
it's not uncommon for Open Source projects to rely on non OSS services. the project itself is Open Source which is where the designation comes from
as far as free, it's absolutely free to spin up. it does require registration (like any other service), but Cloudinary has a generous free tier. it was made pretty clear on the website and repository it relied on that service
just for transparency, i work at Cloudinary, but I stand by the above whether it was Cloudinary or another service
Comment · 2 years ago
will be adding more features, including search, over time!
my first past was mainly focused on initial organization and editing, including Creations (which i was most excited about)
Comment · 4 years ago
Bridges the gap of trying to use Cloudinary in Next.js
Particularly important with Next.js 13 which removes the globally configurable loader and removes the built-in Cloudinary loader (amongst others).
- Automatically optimize images and deliver in modern formats
- Remove backgrounds from images
- Dynamically add image and text overlays to images
- AI-based cropping and resizing
- Transform images using color and effects
- Generate Open Graph Social Media cards on the fly
- Drop-in Upload Widget
Comment · 4 years ago
Colby from Cloudinary here what framework / tooling are you using? Sorry you haven't had a great experience with the UI, but if you stick around with Cloudinary, I would suspect there's a lot of solutions where the processing / uploading can be automated, such as using a Cloudinary plugin within a headless CMS (like Contentful) where you just use a URL or plugins like the Gatsby plugin: https://github.com/cloudinary-devs/gatsby-transformer-cloudi... (only supports images so far)
If you're on the Netlify side of things, I have a plugin there that automates images https://github.com/colbyfayock/netlify-plugin-cloudinary/
There's a ton others too: https://cloudinary.com/documentation/cms_ecommerce_integrati... https://cloudinary.com/documentation/partner_built
Hope that helps, happy to brainstorm other ideas as well!
Comment · 5 years ago
Definitely agree!
WRT deploying Next.js apps, I typically go static first because it makes it easier, exporting it to static files
But there are some other options I've found:
Next.js on Netlify works great if you want to deploy to Netlify: https://github.com/netlify/next-on-netlify
I haven't tried this, but an option to deploy with AWS Lambda and Serverless Framework https://codedaily.io/tutorials/184/Deploy-a-NextJS-App-With-...
there's no reason someone couldn't swap out the underlaying tech and take advantage of the UI, but it's a big undertaking