-
Notifications
You must be signed in to change notification settings - Fork 58
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
Editor width #302
Comments
Alternate idea: expansion up until each page is the same size as a google docs window (816px?) - meaning in split view the page would be 1632px total. Reasoning - I think gdocs did a good job choosing a wide enough view for reasonable wrapping/viewability, but slim enough that it still feel like a page instead of an infinite canvas. Strong preference to not add additional UI complexity / user choice without a strong use case |
this could be good -- tbh I mostly use it in the 1up view because my eyes read markdown better than the formatted view at this point: so it looks like this: but we can probably responsively increase pane width overall -- would love a session with a UX person to help us dial this in (thumbs down to adding another toggle for this, I think) |
It was bugging me too ... I quickly chose option (1) as it was fastest to do. #308 I'll leave this issue open for now ... feel free to leave comments on how you like it, and we can try different things out. Until now, I've mostly been neglecting the front end / CSS stuff - but now that I've got the pinner working, I can spend some cycles on it as we get ready to test it out. |
Description
Editing in a 1920x1200 res (15" laptop) window is hard:
Better to do something like this:
Suggestions
(1) change css
removing
.mw8 { max-width: 64rem; }
does the trick.pros: easy, quick.
cons:
(2) slim/wide toggle button
Maybe make a button that toggles between the slim vs wide version.
Pros: flexible, user choice
cons:
Related things
The text was updated successfully, but these errors were encountered: