Support for dynamic collections like blog posts
Currently this handles pages well, but it struggles with identifying individual posts inside a collection folder in my repository.
Add a staging environment toggle
It would be better if the edit requests went to a staging URL first rather than immediately attempting a merge to main in GitHub.
Pick which collections and fields a client can edit
Editing permissions apply to the whole workspace today, so every site gets the same levels. Sites differ, and so does how much of each one a client should handle. It would help to set per site which...
Interface language
Not all of our clients work in English. The editor and the chat replies are English only, so the tool has to be explained to them before they will touch it. It would be great if a client could use...
Reusable image library
When a client swaps a photo, they upload it again even when that same photo is already on the site. It would help if they could pick from the images already used, instead of hunting for the file...
Scheduled publish
Some changes have to go live at a set time, like new prices on the first of the month. Publish now is the only option, so somebody has to sit and wait for the right moment.
Jekyll support
A lot of the older client sites we look after are Jekyll on GitHub Pages. Connect does not recognise them, so the only way to give those clients an editor is to rebuild the site first.
Bitbucket support
All of our client repos sit in Bitbucket, so I cannot connect a single site today. GitHub and GitLab are both there already, so Bitbucket is the only thing keeping us out.