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.
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
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.
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.
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
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.
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)
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)