A new feature for SilverStripe should be ...

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.

The move to ReactJS and GraphQL makes the UI components more modular and reusable, which provides some opportunities to reassemble them in a more mobile friendly fashion. Overall, the frontend code powering the CMS UI will need to get lighter, there's simply too much JavaScript being parsed and executed on page load. This will be partially resolved once we complete the transition from Entwine/jQuery to ReactJS, but more optimisation work is likely needed.

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.

8 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Ingo Schommer shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

1 comment

Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Paul Clarke commented  ·   ·  Flag as inappropriate

    One of the last areas that requires further responsiveness is the history of pages and this is on the agenda to be updated.

Feedback and Knowledge Base