CMS UI optimised for mobile devices
With the 4.0 release, we've made the CMS UI work well on smaller screen sizes ("responsive"). Some UX flows have been simplified with less available screen space (e.g. moving buttons into a "more options" group). But overall, it's still the same CMS as you'd use on the desktop. That's great for power users since they can access the full set of functionality. But it tends to get in the way if you just want to perform a quick action on the go. A few examples:
- Receive a Slack notification about a blog post draft. Easily review the draft and publish it.
- Review the latest publications, and a concise overview on what content has changed
- After creating a draft on desktop, continue editing a page on your phone
- Edit rich content on a phone with ease, without being stuck in tiny text selections
Some of these aspects are related to rich text editing (TinyMCE functionality etc), some require entirely new features like a CMS dashboard.
This approach might take the shape of specialised views in the current CMS frontend code, but a fully decoupled Content/CMS API would also allow to build this as a separate (web) app.
Paul Clarke commented
One of the last areas that requires further responsiveness is the history of pages and this is on the agenda to be updated.