Update Status Page

EclipseGc@drupal.org's picture
public
group: Usability
EclipseGc@drupal.org - Mon, 2008-09-15 05:05

OK, so I've spent a bit of time rethinking the update status page... I think it's time for some feed back.

I've broken it into 4 areas: Critical Updates, Available Updates, New Versions, and Up To Date.

Critical Updates are those which need updating right now.
Available Updates are those for which an update exists but is not mandatory.
New Versions would be like an upgrade from imagecache to imagecache 2.
And Up To Date is obvious.

I don't have core showing on here, but it would appear in the category that applies to it (only ever Critical, New Version or Up To Date).

Please let me know what you think.

Eclipse

PS: it's been mentioned that the big red X should probably be changed to an exclamation point. I tend to agree with that.

AttachmentSize
update status156.34 KB

In the quite-usual case,

markpeak's picture
markpeak - Mon, 2008-09-15 06:36

In the quite-usual case, drupal site will have some numbers of module and good admin tends to update them when possible. So the 'Up-to-Date' section will be very long (see admin/build/modules - the same length). How does your proposal solve this problem?

I don't have solution either. Let's think:

  • Not to show 'Up-to-date' at all
  • Tab for 'Update' (all other three types) and 'Up-to-Date'

Could we use any best practice from Firefox Add-ons manager?


It needs some spatial

rowanw@drupal.org - Mon, 2008-09-15 08:58

It needs some spatial contrast between the tables, and the range of font styles, sizes and colours needs to be toned down. There's so much information on the screen and it's all presented in a different way - very confusing.

I think it would help if you could explain what's wrong with the current update page as well.

yes, please explain what you are trying to fix first

yoroy's picture
yoroy - Mon, 2008-09-15 09:03

I've been talking with EclipseGc about this in IRC a bit. I'm not sure anymore if this is the modules page or the update status page or a proposal to merge the two.

A rundown of what is broken now and what is in your proposal that fixes this would be very helpful.


Explanations

EclipseGc@drupal.org's picture
EclipseGc@drupal.org - Mon, 2008-09-15 14:59

First let me start by saying that I'm not sure that there's any need to have "Up To Date" modules be hidden. You're not the first to suggest this, but under the existing system ALL modules ALWAYS show... I think this is actually a good thing as it leaves no questions in the users mind about the status of their module. Also I've done a bit of work to collapse these line items' size so that it's easier to see at a glimpse exactly what is going on.

What I wanted to fix on this was basically that the existing system jumbles everything together, up to date and critical updates are right next to each other meaning that the users have to be their own filter and basically they get a little pretty color to make things a little easier. I think we can all agree that's sub-optimal.

As far as all of my different text, I had a concern that people would not understand the different between available updates and new releases. Webchick had suggested this approach, and the significance of it has needed explaining to numerous active drupalistas, so I felt that the information I provided next to each major area was pertinent and necessary. With the exception of this text, I don't feel like the page is any more text heavy that the existing system, and it visually sorts and divides the existing system to work much better.

With all that said this is JUST the update status page, my mockups for the modules page itself will be forthcoming yet. (I have a lot of work yet to do) My only other thought for more visual separation is that we could collapse ALL the categories and put numbers on them that denote how many modules in each section there are that need updating or are up to date. This would be nice for a quick "HUD" sort of interface, but it would also mean clicking just to see what needs updating which I'm not hot on.

Eclipse


I'm -1 for extra clicks,

catch's picture
catch - Mon, 2008-09-15 15:31

I'm -1 for extra clicks, unless it's vertical/tabs summaries with a list of each module in the section or something - but that could wait for that specific patch to land.

In general this looks good to me - having critical updates up top is very useful. I often use the 'up to date' area to check which particular version of a module I'm running - i.e. there are occasions I want to be running -dev due to fresh bug fixes and that sort of information is easiest to get from this page. Also, if every module is up to date, and we hid up to date modules, we'd have an empty page instead of nice reassuring green, don't like the idea of that.


exactly

EclipseGc@drupal.org's picture
EclipseGc@drupal.org - Mon, 2008-09-15 16:12

your comments reflect my own feelings quite closely. You said more concisely what I tried to say in the above post.


Some thoughts

alpritt - Mon, 2008-09-15 16:18

ditto on -1 of extra clicks. Apart from the extra work, it breaks the find function built into the browser.

I don't quite understand why the current organisation is suboptimal as it is very simple to scan (although perhaps it is less so if you have colour blindness; I don't know). One negative with the revision is that if you were looking for a specific module (as in the scenario catch mentions above), you may now have to look in four separate areas until you find it since the modules will move around. Something to consider.

You seem to have lost the 'recommended version', 'development version' and 'also available' titles. What is your thinking here?

Have you considered removing the 'includes' text? Is it useful in this context?

The exclamation point is used for another status already if I remember correctly.

Under 'new versions' there is an entry that says 'up to date', which seems a bit bizarre.

Nice

gaele's picture
gaele - Mon, 2008-09-15 17:07

I like the horizontal separation in importance and the vertical separation between module names and version/download information.

That said:

  • The explanations ("Apply immediately" etc.) seem to me like Drupal form field descriptions, so I'd style them alike (gray, below the title). That way you can get rid of the colons.
  • As rowanw suggested, separate the four tables
  • I'd align the current and available version numbers. This will make it easier to see the version difference.
  • Available version number and Release notes link to the same page. Remove the link from available version number.
  • The four categories are labeled Critical updates (I believe we don't do title case?), Available updates, New versions and Up to date. Labels on the right don't match. They are either Update available or Up to date. This seems wrong. Perhaps get rid of the labels on the right all together?

Be concise

gaele's picture
gaele - Mon, 2008-09-15 17:12

Also: "There are currently no non-critical updates available for any of your modules." That's twelve words.
Better: "None".
Maybe even better: leave it empty.


3 kinds?

markpeak's picture
markpeak - Mon, 2008-09-15 20:30

Are 4 kinds of update too many?

What I want to know

  • "Update it immediately right now or your system might be unsecure" = Critical update
  • "Something newer is out. Nice to update/upgrade it" = Available Updates, New Versions
  • "It's fine. Don't need to do anything" = Up-to-date

How about merge Available Updates and New Versions together in the same category and distinguish them by icon or something else?


Updates available can mean a

catch's picture
catch - Mon, 2008-09-15 20:52

Updates available can mean a lot of different things though:

  • There's an alpha available, try it out if you like.
  • There's a completely new version of your module with a ton of bug fixes, refactoring and new features
  • There's an RC available which is more stable than the old 'stable' version you have, you should probably upgrade
  • I fixed a typo which was causing a fatal error in the last release
  • I fixed a bug which won't affect you because it was in some update from before you even installed the module.

etc. etc. ad nauseum. Having said that, there's few maintainers I trust to indicate this in version numbering, so I almost always look at release notes (and sometimes issue queue and the code directly) to see which one it is, and I don't think having one or two types in the UI can get around this, much as I'd like it to.


My point is... whatever

markpeak's picture
markpeak - Wed, 2008-09-17 08:11

My point is... whatever kinds of update, they're all update notification.

I try to be Drupal user/newcomer and what I want to know is just 'do I need to update it?' My goal is to reduce UI clutter on the update page. Let only crucial information be shown.

Critical/security-related update are important since it might affect the system and everyone should update it suddenly. The other kinds of update are 'nice-to-have' but not necessary.

Anyway, should we include Alpha update to the user?


Columns

rowanw@drupal.org - Tue, 2008-09-16 10:45

I was thinking about how the information could be presented evenly across the page to reduce the amount of eye and hand movement required by the user. In Eclipse's example there is vast amounts of unused space in the middle of the page, while the information on the left and right looks like it's being pushed out of the way. The importance of the information also seems to be determined by how big and bold it is, which gives it an untidy appearance.

I decided to create my own mock-up (see attached) from Eclipse's example and factored in what myself and others have suggested already. I think the download link should be more obvious, but I can't think of a solution.

Feedback is definitely welcome.

I think you might need to

markpeak's picture
markpeak - Wed, 2008-09-17 08:07
  1. I think you might need to emphasis more on 'current version' so that user can compare between 'current' and 'available version'. A new column for 'current version' between 'module' and 'latest version' might help.

  2. What I really like in current Drupal update status is the color background in each update. Your mockup move the color to table head, which is harder to distinguish at glance. How about table head as gray and move red/yellow/green back to the cell.


I'm really not hot on this

EclipseGc@drupal.org's picture
EclipseGc@drupal.org - Thu, 2008-09-18 19:08

I'm really not hot on this as it feels REALLY text heavy. I'll work some more on this this weekend (hopefully) and we'll see if we can keep this ball rolling.


keep pushing on this, please!

adrianrf's picture
adrianrf - Mon, 2008-12-01 10:25

your direction is very good, imho.

if one runs a lot of modules, scanning the Updates list means a lot of scrolling to find if any of the modules need further investigation. as it stands now, there's a definite info overload issue.

whether or not these areas are collapsed, bubbling all Criticals to the top, with red "LED" icons would be a win; then sorting all out-of-date/beta available etc. to a second chunk for further evaluation and marked with amber icons; finally listing all the current items with the same green icons of today. sub-sorts could just be alpha by name, as now.

a graphical summary at the top would be cool too; a count of modules in each colorcoding category would rock -- e.g. red: 0 amber: 3 green: 15.

am so not a visually-accomplished person, I won't try to render this; but something like a stacked histogram that lets you see in one glance, at the head of the page, that the overall module status is 100% Green, the way I like it; [vs. a chunk of amber, and/or especially a chunk of red;] would be a huge time- and hassle-saver.

to really take the biscuit, perhaps clicking on any of the colored histogram chunks could scroll you directly to the top of the respective sort area...

cheers,

Adrian
Adrian Russell-Falla
412 NE 57th Ave
Portland OR 97213-3716 USA
+1-503-381-4678 :mobile/Jajah | +1-503-235-9570 :land/Jajah
adrianrf :GTalk/Skype/iChat | zxadrian :AIM | 478122434 :icq