Our UX Principles: 1. Make the most frequent tasks easy and less frequent tasks achievable. 2. Design for the 80% 3. Privilege the Content Creator 4. Make the default settings smart
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_2_0
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_2_0
Description: Any large lists of people are managed in this section, including site administrators, site members (authenticated users), event attendees and group memembers.
Current thinking/roadmap:
Shows lists of people divided into tabs like Admin (site admins), Members (authenticated users), Events (event attendees), Groups (group members) etc.
Management tools for each type of ‘person’ is shown in their corresponding tab. For example ‘roles’ would be shown with Admins, ‘Broadcast’ tools would be shown with Event Attendees etc.
Note that roles, permissions and user settings will be migrated into the Modules & Configuration section of the site so that this section is focussed on ‘everyday’ usage and Modules & Configuration will hold the less frequently accessed functionality.
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_7_0
updated 7 June
Proposed Experience Architecture, large image here
updated 5 June
Walkthrough of an updated approach for the Site Builder.
Description: Structure will contain two main sections, a ‘Site Builder’ tool that will make creation of a reasonably sophisticated website relatively easy for non-technical people, and the Taxonomy interface.
Current thinking/roadmap:
The Site Builder is intended to help people new to Drupal make a site using Drupal in less than 30mins. Not necessarily the final site they want to launch with but to ‘make something’ successfully
The site builder is essentially a ‘magic user experience layer’ over the toolset that Drupal developers currently use to build a Drupal site.
The rapid site building is accomplished through the design and inclusion of a collection of sample sites, including the content types, pages and functionality most likely to be required. Novice users can choose one of these and do minimal editing to get to a finished site. Advanced users will create their site from scratch
Blocks, Views, Content Types are created using this interface, as the user defines the content to be shown on each page.
The site builder will support a range of levels of expertise – starting with the novice Drupal user and right along the learning curve to expertise
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_6_0
Description: Refers to the ability for users to be able to edit/manipulate content from the website page, potentially using a combination of ‘in line’ editing where appropriate, and triggers to launch editor tools in overlays.
Current thinking/roadmap:
On clicking the ‘Edit’ button in the header, regions of the page would be defined as clickable (eg. nodes, blocks, navigation). Depending on which was selected, the appropriate editor tool would be shown
Nodes would be able to be edited inline (special handling for images?), blocks, views, navigation would launch an overlay with form based editor tools
Clicking ‘Edit’, ‘Save’ or a click in clear space would switch out of edit mode (auto save)
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_5_0
Add Content Page – what you’d see if you clicked on ‘Add’ in the header. (larger image here)
All the configuration associated with the creation of a piece of content goes onto the Meta page, keeping the content creation page as streamlined and focussed on pure content creation as possible. The Meta page is also designed to streamline this process by pulling the most used configuration elements to the front of screen and hiding the more complex and lesser used configuration options. (Larger image here)
What you see if you choose Content from the global navigation or Find Content from the second level of navigation. Shows all content (including ‘orphaned nodes’) and can be easily ordered, filtered and searched. Incorporates the ‘flooded state harmonicas’ interaction style proposed by yoroy. (Larger image here)
Wireframes with some annotations available here (note that the designs above are more recent than the wireframes
Status: These wireframes have been pass onto Acquia for development, prototype for testing coming soon.
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_4_0
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_3_0
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_2_0
Description: A global header which would be shown when logged in to the site (for admin roles (site owners) but not site members (people who ‘sign up’ or ‘register’ to a site).
Global navigation is: Content, Structure, People, Appearance, Modules & Config, <Your Name – Profile>, Log out, Help
Current thinking/roadmap:
The top line of navigation is the global Information Architecture and navigation for the adminstration interface. The second line are a short selection of iconographical shortcuts that are customisable per role for fast access to most common tasks
Users are able to toggle the header to show only the top line navigation if preferred.
No use of javascript flyout menus, although admin menu module could be installed to override this if preferred.
The header will remain at top of screen all the time (even when scrolling)
Outstanding issues:
creation of library of icons. Need to define a short list of required icons and perhaps commission a designer to create custom icons for use in this theme (recommended re: GPL)
Please feel free to add your thoughts as comments below or if you’d rather publish them elsewhere you can have them the pipe by using this tag #d7ux_1_0
To help facilitate the aggregation of discussion around the many and varied aspects of the D7UX project we’ve devised a bit of an infrastructure, which you’ll find below.
Each of the pages below includes an overview of the current state of play and a link to aggregation of discussion around related issues.
1.0 Header (#d7ux_1_0)
2.0 Dashboard (#d7ux_2_0)
(includes widgets for dashboard)
3.0 My Profile (#d7ux_3_0)
4.0 Content (#d7ux_4_0)
(includes Add/Find content and Comments)
5.0 Edit On Page (#d7ux_5_0)
(includes inline editing and other edit/manipulation interfaces on the web page itself)
6.0 Structure (Direct Manipulation Tool) (#d7ux_6_0)
(includes Build/Edit ‘page’, Editors for Block, Content Type, Navigation, Views, and Terms/Categories)
7.0 People (#d7ux_7_0)
(includes add/edit/delete users, roles & permissions, workflow <- moved to Modules & Config)
8.0 Modules & Configuration (#d7ux_8_0)
(all less frequently used config/setting functionality, site settings, module management)
9.0 Appearance (#d7ux_9_0)
(includes find theme, theme builder) 10.0 Configuration (#d7ux_10_0) amalgamated with modules
11.0 Help (#d7ux_11_0)
(includes in context help)
12.0 Palettes & Templates (#d7ux_12_0)
(refers to the palette tool used as an element esp. in Structure) retired this concept
13.0 Installation (#d7ux_13_0
14.0 Accessibility (#d7ux_14_0)
Get your thoughts here:
If you want your thoughts on any of there issues to be picked up, please tag your blogpost, flickr image, youtube video etc. with the tags above (there are also more granular tags for each section if you *really* want to be specific). You can tag your submission with multiple tags if appropriate.
The tagging isn’t particularly human-friendly, so sorry about that. We’ve gone with machine-friendly tags to assist with aggregation and to help encourage humans who are participating to be more precise than we tend to be with more semantic tags
Recent Comments