UI

Hi, I would like to revamp the user experience and the interface for Drupal Ladder.
Stumbled upon an issue created a few years ago, is dormant at the moment(https://www.drupal.org/node/1504476). can someone help me with the status, as well as the migration status for D8.

Queremos melhorar o site da comunidade portuguesa http://drupal-pt.org
Para isso queremos as vossas ideias e contributos.
A proposta é fazer uma reunião de kickoff segunda, 10 de Abril pelas 21h com os seguintes objectivos:
- saber quem tem disponibilidade e interesse em participar

My users are finding the admin interface quite cumbersome. For example to approve members it takes 5 or 6 clicks, including some settings that are not very intuitive for an average user (click next to the user, go to "choose an operation" VBO dropdown, select "modify membership status", click "execute", etc etc) Whereas my users are perhaps used to adding/removing people via something like facebook with one click add/remove.

So i'm just wondering if others have run into this issue before and any suggestions for solutions and simplifications of the user interface?

Has anybody used Semantic UI for their Drupal site? I just came across this http://semantic-ui.com/ as a possible replacement for Twitter Bootstrap and wanted to see if anybody has any examples. I've been playing around with it some and will post mine when I'm done.

Hi Guys,

Hope this is the right place to post some thoughts on UX/I in Drupal 8.

If not, please point me in the right direction. Thanks.

Views
(Not a huge issue for us who understand views, but might help some newbies):

This discussion seeks to expand on existing discussions and activities to define guidelines for the Human Interface of Drupal 8.x

The genesis of this discussion is an observation that the current User Interface Standards don't provide any guidance on this subject.

It appears there are a couple of new use cases for icons within the Drupal UI related to the following;

• Dialog Boxes
• Toolbar Module
• Overlay

I believe we can expand on the existing documentation and provide core developers and UI designers with important standards.

I saw a demo of the Views 3.0 module today at Berkeley Drupal Users Group (BDUG) today. The presenter noted that if a page that is part of a tabbed-pages view differs from the default of the view, the differing options are displayed in the Views UI as italics. I haven't seen the view source of the page, so it may well be empasis tags.

But the larger issue, is marking content with italics or emphasis to distinguish that it has a certain quality, e.g., not a default value, considered sufficient for accessibility, without some other indication that would be read out, e.g., an asterisk?

Who:
My name is Gabriel Massaki and I am studying Computer Science at the University of Campinas (Brazil).
My e-mail is "gabrielmwb at gmail.com" and my nickname on IRC "Gabriel_Massaki".

I live in Brazil, so it'll be "Winter of Code" for me, I study at night so during the day I will have time to work on the project.

Have you contributed to a open source project before?
No, but I always wanted to contribute, because I like the philosophy of open source projects.

Why do you want to do a project involving Drupal?

I recently installed Alpha 14 and created a Drupal 7 Beta 1 platform. I tried to create a site and did not see my D7B1 platform. I thought that Aegir was somehow not seeing the platform. Eventually, I realized that Aegir only shows the platforms that match the profile selected on the Site creation form. Well, that is not obvious.

I spent some time reviewing UI design work on Views 3 (And Acquia Gardens "Data pages") UI concepts:

• "Views 3 UX Season is open", February 2010, Yoroy
• "Views 3 UX workflows and ideas, round 1", April 2010, Rasskull
• "View3 UI explorations, part 2", July 2010, Yoroy
• Acquia Gardens "Data Page" concept mockups, Jeff Noyes?
• "More Views 3 concepts", July 2010, Jeff Noyes

NOTE: I have not read all of (or even very much of) the related discussion, so am likely missing important developments.

There are some great "sky-high" ideas in most of these. However I think it's likely that all of them will run into issues as or more significant than the current UI, in that either;

• They will be be too restrictive upon advanced functionality and features and make them difficult or hacky to include in the (in the case of Gardens, that is likely intentional, as advanced features are probably not supported);
• They will have similar types of unforeseen issues to the current UI. Subtle and seemingly minor nuances or even features that actually make a big impact on the UX.