New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the CMS work for mobile #441

Open
bdougie opened this Issue Jun 2, 2017 · 10 comments

Comments

Projects
None yet
7 participants
@bdougie
Contributor

bdougie commented Jun 2, 2017

- 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.

img_1018 png
img_1019

- 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

@bdougie bdougie added the improvement label Jun 2, 2017

@sachgits

This comment has been minimized.

sachgits commented Jun 24, 2017

am so waiting for this too

@erquhart

This comment has been minimized.

Member

erquhart commented Jun 28, 2017

@rafaelconde 🙏 🙏 🙏

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

@erquhart

This comment has been minimized.

Member

erquhart commented Jun 28, 2017

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

@danielpost

This comment has been minimized.

danielpost commented Jul 1, 2017

@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

This comment has been minimized.

Member

erquhart commented Jul 2, 2017

@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.

@nytyp nytyp added the area: design label Aug 15, 2017

@erquhart erquhart added this to the 1.0.0 milestone Sep 8, 2017

@erquhart erquhart added this to Sprint 3 (10/12 - 10/25) in Sprint Planning | Sprint 6 (11/23 - 12/6) Sep 13, 2017

@erquhart erquhart removed this from Sprint 3 (10/12 - 10/25) in Sprint Planning | Sprint 6 (11/23 - 12/6) Sep 13, 2017

@erquhart erquhart added this to Ready for Assignment in Sprint Planning | Sprint 6 (11/23 - 12/6) Oct 11, 2017

@tech4him1

This comment has been minimized.

Collaborator

tech4him1 commented Oct 12, 2017

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

This comment has been minimized.

Member

erquhart commented Oct 23, 2017

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 erquhart removed this from the 1.0.0 milestone Oct 25, 2017

@erquhart erquhart removed this from Ready for Assignment in Sprint Planning | Sprint 6 (11/23 - 12/6) Oct 25, 2017

@erquhart

This comment has been minimized.

Member

erquhart commented Dec 9, 2017

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.

@erquhart erquhart changed the title from Mobile Considerations in the design to Make the CMS work for mobile Dec 9, 2017

@erquhart erquhart removed the help wanted label Dec 19, 2017

@01ivr3

This comment has been minimized.

01ivr3 commented Mar 16, 2018

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

@tech4him1

This comment has been minimized.

Collaborator

tech4him1 commented May 9, 2018

Updated Slate mobile issue: ianstormtaylor/slate#1720.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment