tbf we've been trying to kill it for a long time, look at every dev product ever
In short, nobody can commit to, change, or meaningfully adjust this repository while adhering to its license.
That's the thing I miss with Canva right now. Yes there are API & MCP options (4 different ways even I think, it's pretty messy), but it's just not sufficient. Ideally you can fully vibe code a poster or a video from the context of your repo, which has all the context and assets, then edit the result online in their point-and-click editor.
If something was easy for someone to spin up there's little reason to build on their work rather than just make your own thing you fully control.
Ideally for who?
Maybe I'm reading too much into it, but this seems to be a tool for people who at least have a slight intention of producing something coherent, consistent and generally nice looking. What you're suggesting is to turn this "tool for a human" into a slop producer, so it's able to produce as much content as fast as possible, with as little human input as possible. Couldn't you fork this and implement this "slop factory feature" yourself instead of asking this tool to be re-built from the ground up to cater to this?
Canva is so bad. It's impossible to align stuff properly. Text rendering is awful. Official builtin templates have horrible kerning. It's genuinely one of the worst graphic editors I've used, and I'm not even remotely a professional designer. I don't want a "Canva alternative", I want a normal editor.
THAT ASIDE, it might be worth focusing on UX. This looks vibe coded, maybe it isn't.
- The UI is broken in a few places (the tools text in the shapes menu)
- Consider prioritising more important tools based on available space in the ui, the header is a bit cluttered.
- Some of the tool menus are awkward to use, like in Canva those are in a side bar and when they open the have panels that don't disappear when their parent looses focus. Probably worth making sure you're not using their exact icons as well as these look pretty similar.
- Your add page button is creating an awkward scroll which you could probably limit by exposing add page in a way that didn't do that. Maybe remove the add page button below the canvas, as you already have an add page button in the bottom left, you should have more vertical space for the design as a result.
- You've got several different export sharing options in the header side by side. Might be worth collapsing that into a menu to minimise clutter. Both tools like canva and more professional tools layout their UIs like this. By all means do don't it just because they are, but there is some rational here why they would.
- There are two places in the header that talk about the save state on the left and the right (one saying saved, the other saying saved in the browser). Consider having consolidating that.
- do you really want to place the copy "Sign up to keep it forever" next to the sign up button? do you have any reason this is likely to stand out from the rest of the UI features there? I reckon if not get rid of it. Or if it's that important get rid of anything competiting for its attention which right now is a lot of things.
- you have a ellipses for a menu with a ton of options, in most software this is aligned to the left. If you've removed other things frmo the the head it may make sense to break that up in submenus so those pieces of functionality is more discoverable.
- Your commment functionality requires sign up to use, keeping it there may help lead to signs ups, but if you're designing this as an open source tool, maybe you're less interested in growth hacking, it might make sense to remove it from the header as well when the user isn't signed in (at the same time keeping it there signals to people weighing up your product that that feature exists.
- you have 2 layers of headers, is it worth utilising horitonzal space for some of your buttons and put them in the right hand side?
Hopefully you can feed the above back into your agent on a loop lol.
Think of the apps you could have written for yourself in the time you spent writing this ;-)
People who have jobs, lives, other stuff to do in other words, keep sending me 'the latest new bla' many times per day, every day. All products that will be gone tomorrow.
I mean, AI made my own canva because my wife uses it and hates their support, bizarre amounts of long standing critical showstopper bugs and attitude to long standing members. So I hope they do get vibecoded to death, however, I would not release such a project until after a year of testing and fixing, which is where our version is about. Canva in the basis, like Miro etc is a one shot with Opus 5.5: it works fine-ish. But you will need months of grind to get it so people will want to use it.
Edit: in the vibecode age, 2000 commits would be the minimum to consider a project maintained. And then I do have a script to analyse the 'effort' of an average commit because some people fake commits with crap to inflate the number.
There are many too many new projects (OSS and closed) that have AI in them and existing projects (Linux, etc.) that are getting tainted by AI.
I think this is a lost cause.
This also works with paid closed source software today.