Continued from #569190: D7UX: Dashboard contents, here we discuss the different possibilities for showing recent stuff on the dashboard. Look at each of these and decide which pattern fits best for:

- content
- comments
- users.

You'll see that different entities want different data and operations to be shown with them. Once decided on a direction for each, we'll split off in even further issues to implement each seperate block.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

yoroy’s picture

yoroy’s picture

FileSize
7.08 KB

HTML source for the above screenshot attached.

seutje’s picture

subscribe

yoroy’s picture

Dashboard items should not only provide status info but also have actionable items connected to that status.

Which makes the case for using tables (so that we can add operation links) instead of item lists.

For content and comments I'm still undecided if we need to show the author name. It's useful if there are many authors (this is quicker the case with comments than with content), but is repetitive noise in single admin/creator scenarios. Of course the author name would only be linked if the profile may be viewed by the current user.

Which means continued work on options D and E.

Oh, and let's not talk about bulk operations here, I thought about them, but let's keep that task for the overview pages and keep these widgets as simple-yet-useful as possible.

yoroy’s picture

What's not clear from the prior screenshots is that the operation links really are in there (html demo shows them only on hovering the table row)

dashboardwidgets

Bojhan’s picture

So given the space for this, I think the first one of E is definitly favourable. I suppose this will live on the left - and its contents can be fairly flexible. For example I imagine configuring this to hold comments.

yoroy’s picture

Worked on this a bit with Bojhan in IRC:

dash4

Dave Reid’s picture

Subscribing.

webchick’s picture

Hm. I think the all-in-one block might be a bit too fancy; would require some JS for dynamically updating the link URL and I'm not sure how it would work for accessibility. Plus, ideally, these blocks could be re-used both in the dashboard and other places, when they make sense.

But in the meantime, E. seems like a really good direction. Could someone start working on a patch?

Dave Reid’s picture

Yeah, an all-in-one block is probably going to make this a lot harder. If we want to accomplish something now separating by type would be best. I'll start working on an implementation.

Bojhan’s picture

Yup, thats fine.

seutje’s picture

separate blocks seem better yea, let contrib handle the fancypants :P

yoroy’s picture

Sure, we should start there. Unblocked the issue for recent content block for the actual implementation work:

#337947: Correct whitespace issue for 'recent content block' in dashboard

yoroy’s picture

Status: Active » Fixed
Issue tags: +ui-pattern

Fixed for, adding ui-pattern tag to find it again if we want further documentation.

Status: Fixed » Closed (fixed)
Issue tags: -Usability, -dashboard, -ui-pattern

Automatically closed -- issue fixed for 2 weeks with no activity.