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
Description: Includes the design of the installation process as well as install profiles
Current thinking/roadmap:
continuing the work done to date to streamline and improve the usability of the install process
add creation of dummy content as part of install process
development of install profiles for most common/likely site requirements
consider optional user of wizard
*
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_12_0
Description: A design element we’re considering for use in D7 that users will be able to move around the screen and drag off elements (that we’re currently calling ‘templates’ and ‘bits’)
Current thinking/roadmap:
we were thinking of something pretty similar to what was shown in the Buzzr prototype recently
*
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_12_0
Description: where you go if you need help to build/manage your site
Current thinking/roadmap:
haven’t really given this section a whole lot of thought yet but thinking about crossover with d.o documentation
also thinking about contextual help
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_11_0
<a href=”http://www.d7ux.org/project-framework/”>go back to Project Framework to view all project components</a>
Description: A more ‘technical’ section of the admin, predominantly for site administration purposes. Content creators should not need to go into this section in order to add/edit/delete content. You should be able to get a simple site up and running without going into this section.
Current thinking/roadmap:
probably not significantly different to the current
Aggregated Feed (Pipe) of Related Discussions
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: This section allows users to choose/edit and perhaps ‘build’ a theme for their site
Current thinking/roadmap:
ideally, users would be able to choose from a number of great themes from this location
they would also (ideally) be able to build their own theme using a range of preset variables (grids, colours, type, etc.)
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 section of the site for modules to be installed, updated and configured, and other site configuration activities.
Current thinking/roadmap:
put all the ‘config’ type stuff in one place so that you don’t have to know if it’s a module or not to find it
retain the current ability to sort by module or task (not currently shown in wireframe)
nest modules with dependencies under the module-of-dependence
make it obvious at a scan of the page if updates are required
recommended modules (possibly top 10-15 most installed modules?) to help point newcomers towards necessary modules as quickly as possible.
streamline permissions
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,
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
Screenshots updated 4 June 09
Shows the ‘Meta’ header.
Shows the Hover State.
Shows Edit In Place.
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)
Status: Handed on to Acquia for development
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. ()
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. ()
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 ‘e proposed by .
Wireframes with some annotations (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
Recent Comments