Make the CMS work for mobile

[bdougie]

- Do you want to request a feature or report a bug?
Enhancement: It would be nice to quickly check in on a post on the CMS from my phone

- What is the current behavior?
The current UI has no consideration for mobile and non-usable from a mobile device.

- If the current behavior is a bug, please provide the steps to reproduce.
Look at the https://cms-demo.netlify.com/ from your phone.

- What is the expected behavior?
The editor can be ignored for now because it would require a larger scope. However, the editorial workflow and list of posts could be tweaked quickly fit on a mobile screen. Even it was just a list of post.

I recently had a situation where I was AFK and needed to ship a blog post from my phone. My only option was logging into GitHub and merging the PR, but it would have been nice to just hit publish from the CMS

- Please mention your node.js, and operating system version.
iPhone 7

[sachgits]

am so waiting for this too

[erquhart]

@rafaelconde 🙏 🙏 🙏

I'd at-mention @danielpost but he's not a collaborator. Maybe I should add him as a collaborator...

[erquhart]

Oh snap it worked! Going to add him anyway :)

[danielpost]

@erquhart Sweet, thanks!

I'm too busy for the next ~2 weeks but I'm going to take a crack at designing potential interfaces for the CMS over the summer.

EDIT: With that being said, I think it's important to prioritize properly. Do we want to optimize the current state of the app for mobile, or do we want to wait for the new design? Do we start working on a mobile version when the main parts of the new design aren't even set in stone yet? I'm guessing #180 is a better place to discuss those issues though.

[erquhart]

@danielpost super excited that you're looking into this! I think it'd be okay to do this as a part of the greater design improvement effort, since it's slated for 1.0.

[tech4him1]

The main improvement that I see on this is just to make it responsive -- most of the general UI as it stands should work fine on mobile. @erquhart Do you think this should be done mainly after the general UI improvement, or as part of it?

[erquhart]

A little of both, there will be some basic effort to ensure that things are more or less responsive, but actually optimizing for mobile will probably happen post-1.0, as it goes beyond just the UI. The markdown editor, for example, might need a bit of work to function properly on a touch device.

[erquhart]

So this isn't addressed in 1.0, but it's sort of better. The real reason we aren't pushing mobile is that there are technical issues beyond layout responsiveness - for example, Slate doesn't officially support touch input. Making the CMS work on a mobile touch device will require a good amount of effort, but it's definitely something to push for.

[01ivr3]

there appear to be some traction for adding mobile support to Slate
ianstormtaylor/slate#1656 (comment)

[tech4him1]

Updated Slate mobile issue: ianstormtaylor/slate#1720.