Feature #38585
Re-arrange "status" tab
| Status: | Accepted | Start date: | 2012-07-03 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Fabien Udriot | % Done: | 0% |
|
| Category: | - | |||
| Target version: | 1.3.2 | |||
| Votes: | 0 |
Description
It has been said by customers that the tab "status" - which is displayed by default - looks a bit geeky and displays too technical information.
I would suggest to move information related to "Newsletter validity" into its own tab "Validity". Furthermore, I would add a few instructions within the tab "status" to guide the user when the newsletter has never been sent.
History
Updated by Fabien Udriot 12 months ago
- Assignee set to Fabien Udriot
Updated by Fabien Udriot 12 months ago
- Status changed from New to Needs Feedback
Updated by Adrien Crivelli 11 months ago
Guiding user is a good idea, it's quite "rough" for now.
However I would not hide the validation message in another tab, because it's specifically something we wanted to expose when mocking up the GUI for this extension. Users must be aware that their newsletter is of poor quality if it's the case. So I would rather improve the current layout/messages than hide it altogether (maybe collapsing things ? or a "dumbed down" version ?). The ticket #29610 was created quite a long time ago for that and we could continue the discussion over there (splitting this ticket in two).
Updated by Fabien Udriot 11 months ago
I have the following concerns with the tab "status":
- The content is slow to render because of analyzing the output.
- Information is not really relevant towards editors users because it is not their purpose and also because they can't do much (except perhaps content from RTE). It is more something targeting admin user in my eyes.
If we keep this info on the first tab, then I would go for a button <check newsletter quality> or something like that which would display a report on-demand. What do you think?
Updated by Adrien Crivelli 11 months ago
- Target version set to 1.3.1
I am not 100% convinced that user, even "simple" editors, should be ignorant of the quality of their work, even if they cannot do much by themselves about that, they can at least contact for help.
The latency is a very good point though, and the on-demand validity check seems to be a good compromise for everybody. Still visible, but not too much "in the way".
Updated by Adrien Crivelli 11 months ago
- Status changed from Needs Feedback to Accepted
Updated by Adrien Crivelli 2 months ago
- Target version changed from 1.3.1 to 1.3.2
Postponed to next version, so we can release 1.3.1 earlier.