d7ux

In order to be more efficient in our approach in identifying issues, we have created a simple google spreadsheet. The intent is for everyone in the community to be able to log issues easily. Over the period of time we will be able to prioritize and solve these usability issues.

I hear you guys, this is a very 1.0 way of doing it, but at least it is a start! right?

So when you get annoyed with something, make a difference, log the issue.

Here is the google spreadsheet: https://docs.google.com/a/acquia.com/spreadsheet/ccc?key=0Ai6zQDgsPhvldH...

Hi all,

Most of us is very enthusiastic about the user experience improvements for Drupal 7. The restructure and renaming is very welcomed and I am sure it will make it much easier for newbies to get started.

There is though one area that I still see as untouched, namely the Modules list page. After installing a number of modules it is quickly becoming a bit of a chaos list, especially since a lot of modules aren't using the "package" field in the [module].info file and thus their module end up in the Other category.

After discussing the d7ux overlay accessibility issue with several at Drupalcon, and mentioning the issue in my lightning talk at the Core Developer Summit I noticed that an Allow users to opt-out of the overlay issue had been opened in the bug tracker. Overlay is a contentious topic for some in our community, and I will not rehash all of the pros and cons for Overlay's inclusion in core. I will however attempt to concisely present an argument for Overlay being disabled in all Drupal 7 core installation profiles.

Hi folks,

This morning I took a first look at the d7ux administration theme "Seven" from the perspective of a screen-reader user. Overall I found the theme enjoyable, but there is more work to be done to ensure that the theme is truly accessible.

You can read my blog post about the accessibility of Seven at http://openconcept.ca/blog/everett/first_glance_accessibility_evaluation...

I have been harboring some growing concerns about the direction of the plugin manager integration proposals for Drupal core almost since their inception, but have not been able to make an informed opinion on the subject until I had properly reviewed the proposed system on a much deeper scale.

While my impressions of the project and the current implementation are fairly negative, I have aimed to frame my criticisms in a positive constructive manner because I believe that the goals of the project are worthwhile, and that for a large section of users this could be a very flexible and usable solution.

Unfortunately a lot of my concerns have been well founded, and I believe that the implementation of this system needs to be taken in a different direction for it to be able to succeed in its goals, while not negatively affecting projects like Aegir, Open Atrium and many other ‘serious developers’.

We've just added a new video to the YouTube Channel which we refer to in this post - check it out now:
http://www.youtube.com/watch?v=ShBPEL_ckJw

Over the past week or so Mark and I have been working out the details that go on the panels of the Audience Matrix that we shared with you last week (http://www.disambiguity.com/understanding-our-audience-part-1-drupal7-ux...) (or dress-up-doll document as it has otherwise been named). We’ve made a few changes and added a bunch of definitions.

Here’s what we’ve come up with so far:

ROLES: