-
-
Notifications
You must be signed in to change notification settings - Fork 135
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
Indicator for the Workspace state #3803
Comments
Some more UX/UI ideas (disclaimer: I'm not a designer, nor UX expert. at all.):
Two really rough suggestions just to communicate the direction (I guess an indicator should rather be a small badge/icon instead of this huge buttons, but I didn't want to overstress my Photoshop skills): |
I like the idea that we see directly the current selected workspace, but the top bar becomes really overloaded. The state and the workspace are important, and the dimension and the publishing as well. But I am also not a designer ;) |
That's true. Maybe the indicator could just be a simple icon on the publish button with more details & options in the dropdown.. |
I created a rough first draft of the feature here: #3665 To avoid confusion I would suggest only adding a small button if the workspace is outdated. If the personal workspace is up to date the button would not do anything anyways. The Icons is something I made up on the fly, but if an actual person who can do icons wants to have a go, feel free 😄 Also, the whole padding/sizes and newlines styling stuff is not finished, this is something like a mockup. Normal status, personal workspace is up to date Personal workspace is outdated Clicking on the button opens a popup: Personal workspace is outdated and in error state |
@pKallert You're amazing, I like the approach! From those modals one option should be to go to the workspace module, but we can always add that later |
TL;DR The Backend should provide an indicator of the current workspace state, especially when conflicts happened
A workspace in Neos 9.0 can have one of the following three states:
UP_TO_DATE
- This is the case if the contentStream of the base workspace IS EQUAL TO the sourceContentStream of this workspace's content stream, i.e. there no new events on the base workspace (By definition, a base workspace (like "live") is ALWAYS UP_TO_DATE)OUTDATED
- Can have two reasons: a) The base content stream has been rebased, b) The base content stream has new eventsOUTDATED_CONFLICT
- a special case of OUTDATED, but then an error happens during the rebasingSee WorkspaceStatus enum for more details.
The
OUTDATED
state means, that a rebase is required (Currently that is triggered by logging-out and -in again).In the
OUTDATED_CONFLICT
the current workspace can't be published. So new changes will be lost.With 9.0 there won't be a (fully fledged) conflict resolution because that's very intricate, but we are considering ways to at least partially apply changes and/or be able to "stash" the pending changes so that they don't have to be discarded.
In any case, we should provide the user an early feedback of the workspace state, especially for the latter two cases.
The text was updated successfully, but these errors were encountered: