[Feature] New Post Settings Menu #3822

Closed
ErisDS opened this Issue Aug 19, 2014 · 12 comments

Projects

None yet

7 participants

@ErisDS
Member
ErisDS commented Aug 19, 2014

The new PSM design is being constructed here: https://github.com/TryGhost/Ghost-UI/issues/99, markup is here.

It looks like this:
image

And works like this:

The new menu is more complex that the old version, as it has extensible sub-screens. There will likely be a number of child issues to implement the advanced functionality in Ember, as well as to implement each of the new features:

These sub issues are ready to start

@ErisDS ErisDS added this to the 0.5.x Feature Release milestone Aug 19, 2014
@morficus
Member

I'm actually quite excited for this :-D

@PaulAdamDavis
Contributor

I've done a quick & dirty implementation of this, just to see how it feels. (It's not functional)

In doing that, I've had a good think about how this should be handled. It should be a similar way to how the mobile navigation is done – i.e. slide out from behind the <main> element, something like this:

<div id="container">

{{#unless hideNav}}
    {{partial "navbar"}}
{{/unless}}

<main id="gh-main">
    ...
</main>

{{outlet rightSidebarOrSomething}}

{{outlet modal}}

</div>

psm-again

@novaugust
Member

Super pretty drawing.

I think the gif would be more useful if it was in the context of the entire screen

@novaugust
Member

More seriously, I think we want a second outlet here, following the modal pattern. That way, we're ready to go for other sidebars down the road, too

<div id="container">

{{#unless hideNav}}
    {{partial "navbar"}}
{{/unless}}

<main id="gh-main">
    ...
</main>

{{outlet offscreen-sidebar-menu-thing-sometimes-used-by-psm-but-also-but-other-things-too-maybe-later}}

{{outlet modal}}

</div>

Like that.

update maybe we could come up with a better name, but whatevs

@PaulAdamDavis
Contributor

@novaugust Outlet! Yes. That's what I was thinking of.

@PaulAdamDavis
Contributor

What I'm not sure about though, (and this is a design decision... cough @JohnONolan) is if the PSM should move the publish bar (tags) footer to the side as well, or just the editor. Or can both happen? A second outlet has utility in many places I imagine.

@ErisDS ErisDS referenced this issue Aug 26, 2014
Closed

[Feature] Post Cover Images #3885

1 of 4 tasks complete
@JohnONolan
Member

Same as mobile menu - the entire screen moves over

@ssachan
ssachan commented Aug 29, 2014

@JohnONolan - just a thought. Having both the editor and the preview screen consumes a lot of space. Why cant this be a tabbed interface...like it appears on the mobile/tablet devices right now. People will write their content, click on the preview tab and switch to the preview div.
I think we'd want to show the post settings section at all the time and have that system scrollable instead of opening another div on the right

@ErisDS ErisDS added the feature label Sep 2, 2014
@ssachan
ssachan commented Sep 5, 2014

@ErisDS : Any comments on the note I left. I think that approach will require less coding as well. More than the preview, I believe our users would want the post settings tab displayed at all time

@ErisDS
Member
ErisDS commented Sep 5, 2014

@ssachan customising the interface for your users is something I'm sure will be possible with apps at some point.

@halfdan
Member
halfdan commented Sep 5, 2014

@ssachan The split editor is a central piece of Ghost. It doesn't require less/more coding having it alongside the new PSM. I can't speak for all users, but from a UX perspective it doesn't make much sense having the PSM open at all times as you're only going to edit the settings at the beginning/end of writing your post. Having the splitscreen editor gives you a distraction free writing experience.

@ssachan
ssachan commented Sep 5, 2014

@ErisDS : hmm okay
@halfdan : There'll be less coding if we are avoiding all the transitions. We can get rid of the settings button thats to the left of the update posts button...something thats not intuitive for a first time user. If you are coming from a wordpress background, they use metaboxes very heavily and I wouldnt want them to be two clicks away.
Anyway ... we can always come back to stuff like these

@ErisDS ErisDS closed this Sep 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment