There is a registry relating gadgets to menu router paths. On an applicable menu router path, an add link will go to the More Widgets tab with the applicable widget(s) ready to drag to another tab.

Comments

drumm’s picture

Assigned:Unassigned» drumm
drumm’s picture

Issue tags:+drupal.org redesign

Tag

lisarex’s picture

I've linked this from the Redesign project #661532: Meta issue for Dashboard because this issue was tagged 'drupal.org redesign'

techsoldaten’s picture

@drumm - mind elaborating on this concept? I want to understand what you were talking about a little better before I close out this ticket.

This is clearly a UI and functionality point.

M

techsoldaten’s picture

Priority:Normal» Minor
drumm’s picture

Many pages in the prototype, like https://infrastructure.drupal.org/drupal.org-style-guide/prototype/event..., have a green add to dashboard link in the top-right of the page. The interaction that happens hasn't been well-specced by the prototypes, so we have to do something good.

I was thinking of associating widgets with pages by menu router paths. When clicked, it will get to the same workflow as the 'Widgets' tab on the dashboard as quickly as possible.

techsoldaten’s picture

@drumm - okay, trying to address the gaps in the prototypes. Here is the workflow I am thinking about:

1) On any node or block (or other content item dashboard supports), there can be an add to dashboard button.

2) When clicked, this button will add the item to the user's dashboard.

3) When the item is being added, the user will select the dashboard to display the widget (in the case the user has multiple dashboards).

4) When the item is being added, any contextual settings will be preserved. So, in the case of a block about a specific project, the block would appear on the user's dashboard and display information about that project.

Does that sound about right?

This would work well in the case of nodes and blocks, but I get concerned about menu router paths in general. Are you saying that any path from the system is potentially a widget?

M

techsoldaten’s picture

Assigned:drumm» techsoldaten
Priority:Minor» Normal
drumm’s picture

1) We don't want those links cluttering the page, there is one add link for the whole page. This may present multiple options for which widget to use.

The menu router paths would be for mapping which page(s) a widget is offered on. But, if we only do blocks, we can hook into the block rendering process and detect what blocks show up. A similar push model could be used for panels pages. I'm not 100% on menu router paths, but they do identify pages.

3) Ideally this selection has the same UI as adding a widget starting from the dashboard and clicking the Widgets tab.

drumm’s picture

Issue tags:-drupal.org redesign

untag

reneve2010’s picture

Subscribe