Suggested commit on all UMN 2015-tagged issues: Issue #xxx by [standard list], Bojhan, eliza411, ivanstegic, LewisNyman, lunk_rat, nickrosencrans, stpaultim, Mark LaCroix, webchick

Just before Twin Cities DrupalCamp 2015, a group of Drupal contributors participated both in-person (@LewisNyman, @Bojhan, @webchick, @eliza411, @stpaultim, @ivanstegic, @lunk_rat, and others) and remotely in Formal usability testing of Drupal 8 at the University of Minnesota Usability Lab.

Seven participants tested Drupal 8, all with a background in web development, some with prior Drupal experience and some without, but all new to Drupal 8. A set of scenarios were prepared that lead participants through a variety of content authoring and site building tasks:

- Add an about page and add it to the main navigation
- Create a content type with fields
- Test the mobile content authoring/editing experience
- Place a pre-configured block in the left sidebar (or create one in Views).

(We also tried to test Quick Edit, but sadly no one found it! Sniff!)

This issue will attempt to collate the 100+ issues we found during testing, categorized, and prioritized according to their overall usability impact. (Note that Usability priorities do not always reflect the Drupal core definitions of issue priority and therefore may actually be classified as different priorities in the issue tracker.)

Each of these needs to be "issue-ified" and tagged both "UMN 2015" and "Usability." We will attempt to do this at the sprint on Sunday.

Table of Contents

Mental model

Description Issue UX priority
Drupal uses weird words for everything, making Drupal extremely difficult to approach for new users. #2513398: Conduct a full-scale terminology review of Drupal (Fix Drupal terminology so that it is more accessible to users) critical
Wayfinding, or clues on how to get started, were lacking. Task-based headings and navigation — verbs — would have been more helpful than the nouns presented. "This is a jambled-up hardware store with no wayfinding. I have to go through every aisle looking for electrical outlets. #2634854: Add "Admin Toolbar" module to core toolbar critical
"Expected structure to present a hierarchy, instead of presenting a list of equal choices. ""Larger categories should not be equal to smaller categories."" When using a tool like Drupal, there are certain concepts that are key. But when looking at links and structure, everything appears equal." #2518960: Emphasize the most important items on the 'structure' page critical
Compared to Wordpress, "You don't have to figure out how to place your block inside your view inside your region inside your homepage." "If all you use is Drupal, you're not going to be able to make any other kind of website." #2820235: Add inline entity form to core as experimental critical
Dependence on previews led to inefficiency. "Until I saw them, I was never sure if I did the right thing." The inability to see the work in a realtime preview was frustrating. critical
"Order of operations are backwards! For example, dependencies and prerequisites for structuring taxonomy/content/etc. are reverse from the way users conceptualize it. (e.g. creating terms before adding a field for terms) "I have to go to the Block page and abstractly add a block." #2635710: Add option to automatically create an entity reference view when a new content type is created critical
User expected a much more fleshed-out basic install. Made Drupal appear limited in functionality. #2527954: Add a 'Standard + demo content' profile critical
The user saw a page shown on the front page, and got alarmed thinking it was accidentally created as the site's homepage. #2514794: Frontpage view is confusing when only one node is promoted to the default front page critical
"The new standard for the homepage is a big fat image, and an endless scrolling list of news is outdated. It was scary, and led users to feel like whoops! I broke the homepage." #2514794: Frontpage view is confusing when only one node is promoted to the default front page major
Where did my content go?! #2513402: Any time a user creates a thing and saves, display a link to the thing created in the status. major
Reluctance to get too deep into Drupal for fear of breaking the installation prevented the user from exploring or trying new things. critical
Desire to approach sitebuilding in a hierarchical manner led user to try building the site menu first. Inability to simply add a tab let user to reject Drupal. major
"When I get frustrated with stuff, I like to get into the part where I can write the code and tell it exactly what I want to do." The administrative interface seemed too helpful for users who want to fine-tune. major
Distrust in Drupal led user to depend on external services and embeds to get Drupal features done. "Drupal isn't robust enough to handle complicated things." major
We ship with a configuration interface and no content manager role/workflow. People who maintain content are intimidated by a new installation, because they see a full administrative suite with no context that lets them see their role. "We dumped a content editor into an admin 2 interface." major
"Teaser was confusing. "Well … and that's just bad content strategy."" normal

Blocks

Description Issue UX priority
The idea that there was an existing library of blocks was completely lost to the user. #2512456: Implement the new block layout design to emphasize the primary interaction of placing a block critical
"I would expect to click something like, [Configure this page]. Or hover over something and click, [Add a block here]." Tried to add a block from the pencil icons." #2061679: Add a tour for the improved block admin UI at admin/structure/blocks. major
Users wanted to add blocks from regions, both on the front-end, and from the back-end block admin form. #2513520: Add a contextual link to add a block to a region
#2513528: Add a link to add a block in empty regions on the Block layout page.
major
When placing a block, users expected to be able to add a block through the add block button and then fill in the body, including dynamic blocks. major
Order of block placement/configuration form is not intuitive. Cache settings is too prominent. Region (primary action) is at the bottom. #2361921: Re-order the 'place/configure block' form so it's focused on the task at hand. major
Regions were understood as blocks; for example, "Primary menu" being interpreted as the primary menu, not as a region in which you can place a menu. #2513526: Rename the menu regions major
Disabled as a region makes no sense. It is an action you take on the block, not a place to put it. #2513534: Remove the 'disabled' region from Block UI normal
The "demonstrate block regions" link was completely missed. If that had been used, the user might have better understood block regions. #2514150: Advertise the block region demonstration in a more prominent way normal
User went to appearance looking for blocks. "I'm looking for layout." #2513556: Add a link to the Block Layout page on the Appearance page#2811175: [plan] Add layouts to Drupal normal
Expected blocks are draggable. (mental model from panelizer) minor

Content creation

Description Issue UX priority
Finding where to get started creating a basic page was difficult. #2377543: Add "Add" item to toolbar. critical
"I would like to see what this would look like if I'm not logged in." The status of what was being displayed, that of an unpublished preview, was not clear. major
When you click back on the browser during node preview, when node preview is required, the save and publish button does not appear major
There's no way to save from the preview. normal
Save button was expected on the right sidebar, like it is with Wordpress. normal

Content types

Description Issue UX priority
User is looking for the word "Forms" when they actually need to create a content type. Users cannot tell a content type is the container that fields are being attached to. #2528340: Improve description text for 'Content types' item on the Structure page critical
After adding a content type, user is brought to the Manage Fields page. Since this page does not have the content type name in the header (header just says "Manage fields"), the user believed that they failed to create the content type. "This page has nothing to do with what I just did. Whatever the helpdesk said didn't work." #2514218: [regression] Pages Manage Fields, Manage form, Manage display should include name of content type or entity normal
User did not get the connection that creating content types and fields were creating entities on the back-end database, despite knowing what a data model was. major
Accidentally requiring preview leads user to lose the ability to save changes without any visible way to undo that setting, or even to know it's set. major
After creating the content type, user did not know how to find the form. The link exists … but there's no trail. major
The difference between ① Manage Display, ② Manage Form Display and ③ Main Tab was hard to understand. #2521780: The 'Edit', 'Manage display' and 'Manage form display' tabs were hard to understand major
It was not clear that the content type admin page and the content creation page were two completely-different things. normal
When user changed the content type name, the old name was showing in the breadcrumb. #2513570: Changing name (label) of content type is not reflected in breadcrumb link text normal

Field UI

Description Issue UX priority
The options under the Add field drop-down describe the data you want to store, but the user was imagining the widget it would produce. #2539740: Provide users with a visual way to understand and build content types (dream fields) as an experimental module. critical
Too many options in the dropdown of field types. #1953836: Replace "Select a field type" with a hierarchical select major
Field type names are ordered alphabetically, not according to how often people might use them. User 2 didn't see "text" for a long time. #2539740: Provide users with a visual way to understand and build content types (dream fields) as an experimental module. major
(List fields) The key|label entry field is freetext, which doesn't give little guidance toward the expected input. #2521800: List(text) key|label entry field is freetext, which doesn't give guidance towards the expected input. major
User deleted the field in order to change multiple value settings, not realizing you can go back and adjust the values. #2524322: Users deleted a field instead of going back to change their settings #2513688: Live preview in Field UI "Add field" screens normal
(With a List (text) field) When entering no allowed values, there was no validation error and no way to tell what it would do. So when creating content, the select list said "none" … which led user to delete the whole field and start over. normal
User didn't realize that the body field is added by default on new content types. normal
When creating fields, the default value option was so prominent, it was perceived as a preview. Users expected to fill it out. #2513688: Live preview in Field UI "Add field" screens normal
"I don't know what a view mode is." normal

Taxonomy

Description Issue UX priority
After choosing a term reference, you have to choose a term reference again. #2516886: Remove the entity type from entity reference settings, if an entity has already been selected critical
The mismatch between taxonomy term becoming entity reference led user to lose the very concept. major
The "Vocabulary" selection in entity reference was meaningless. User clicked "Tags" just to make the error go away. And there's no way to add a new vocabulary from then on. major
When adding taxonomy terms from the term admin, user missed the message that a new taxonomy was created. #2524268: Make the "New term created" message more noticeable. normal
When creating a taxonomy term, it did not default to autocreate terms. normal
Widget settings exposes SQL syntax to the user: "CONTAINS" normal
Without noticing taxonomy terms are all in one bucket, users go too far in implementing them. e.g. User 2 used taxonomy terms instead of users, which was our expected behavior. major
When trying to add a term that does not exist, Drupal returned an error: "Asian Carp entity does not exist." If the site went live this way, it would have been more severe. normal
Widget settings exposes SQL syntax to the user: "CONTAINS" #2513612: Make the autocomplete form option text for an entity reference not be all caps normal
Labels for vocabulary vs. automatically creating new are shown under the same heading. So they seem to be the same thing. #2522950: Taxonomy term reference settings form: "Vocabularies" and "Create referenced entities..." look related normal
Description Issue UX priority
The label of the link on Menus did not trigger the user to type a title there. major
Removing the node ID (1) breaks the URL because Drupal thinks it's a manual URL. If the user hadn't thought to put it back, the installation would have been completely stuck. "Huh… I guess you need that." #2520416: Autocomplete node ID numbers are confusing, only display when required major
User changed the actual menu title to reflect the desired menu link name, "About". Menu settings was mis interpreted as a way to add a new link. #2520232: Separate the menu settings from the 'add link' button major
All options on the Menu link add page were overwhelming, when all the user needs is to change one thing. #2519362: Redesign the menu link add form to be less overwhelming normal
Weight was confusing. What do I put here to get what I want? Help text didn't explain weight. "Well… I'll put 1 here then." normal
"Tools menu sounded pretty handy! But it didn't do anything useful." normal
Experience with Wordpress led user to interpret Menus options as if there was only one menu on the site. #2513606: Menu admin UI should guide new users to add links to "Main navigation" menu normal
(bug, needs steps to reproduce) The home link magically vanished. N/A

Quick Edit

Description Issue UX priority
Not a single participant was able to find the quick edit functionality. Pencil Icon did not make sense. What does it do? #2761985: Refine/finalize design to discoverable Quick Edit feature major
Selecting/deselecting the view pencil icon was not an expected interaction. major
Expected hover text on the pencil icon. normal

Contact forms

Description Issue UX priority
There is no link, anywhere, to a contact form once a user creates it. #2513396: There is no link, anywhere, to a contact form once a user creates it. major

Configuration management

Description Issue UX priority
"Configuration Management" sounds more important and appealing than it really is. User went there hoping for more. #2513568: Relabel "Configuration Management" normal

Content listing page

Description Issue UX priority
The action button looks like a submit button when it's close to other form settings. User started typing content into fields meant to filter the table. #2521808: Visually encapsulate the content listing filter to distinguish it from the 'add content' action link major

WYSIWYG

Description Issue UX priority
When pasting from Word, the line breaks get entered twice for some reason. User went into Source Mode to fix this. #2516932: When pasting from Word, empty paragraphs were created major
"Looks like your clipboard was copied from Word. Do you want to clean it before pasting?"
[OK] [CANCEL] (Also, what happens if user clicks cancel?)
normal
Bulleted list pasted in from Word (2010) as characters, not as a <ul>. normal
User had to create a second-level heading using HTML because there was no option available. But the WYSIWYG editor then stripped that out of the code. User 2 bolded the text and skipped the accessibility-friendly standards. #2521906: Add default configuration to support h2-h6 level headings normal
No box to enter a caption when caption option is checked in image dialog. normal
Image size field is too prominent. #2519862: Remove the width/height inputs from EditorImageDialog minor
The text doesn't wrap in the Source view on Firefox. minor

Help

Description Issue UX priority
Help topics sorted alphabetically by module prevents user from learning workflow. "It just jumps around from the obtuse to the very basic." #2516902: Introduce a visual hierarchy to the help page. critical
The help system is not task driven, like users would expect. Neither "Content Type" nor the word "Forms" appear on the Help topic page, because they're not modules. critical

Toolbar

Description Issue UX priority
Toolbar active tab state wasn't clear. User couldn't tell the Manage tab was open. #2523062: Tweak the active styling of the toolbar tab to be more noticeable normal
Didn't notice the toolbar. (mobile) #2516938: Set the toolbar to position fixed on mobile major

Bartik

Description Issue UX priority
Bartik's default typeface seemed a little strange when using Chrome on Windows 7. normal
The target for the Add Content link was too small. (on default front page) (mobile) #2524272: Make Bartik sidebar menu blocks finger-friendly normal
Options to view/edit/delete and the selected option was highlighted in white, which seemed backwards. (mobile) minor
Description Issue UX priority
Search error presented was, "Must include a positive keyword with three characters or more." - word 'positive' is a problem. #2513586: Remove the word "positive" from the "Must include a positive keyword with three characters or more." error message normal
When attempting to search for something, "UP?" did not count as three characters. #2513590: Include special characters like ? in character count of search terms. Or, allow fewer than 3 normal
Expected when searching for a user to show content by that user. normal

Views

Description Issue UX priority
Loading up the Views Edit UI was frightening to the user, who did not want to see any of this, let alone try changing of it. The pencil icon was cognitive dissonance compared to exposing what seemed to be advanced, dangerous options. "This makes me want to never touch Drupal again." major
"How does one delete a field?" (views) major
How does one add a field? (views) major
When checking the "More" link, the error offers no ways to recover if the view includes no page display. User had to abandon and try again. normal
The block the user created did not contain users; it contained information about users. It was just a list of member-for's. #2321645: Default entity view for User should show user name normal
"""What do you want to display?"" the Views page asks. The user selected ""user entities"".
""How do you want to display it?"" the Views page asks. But the options presented included no context around it. There wasn't enough information to make an informed decision. (Distinction between field vs. teaser or whatever is not clear.)"
normal

Mobile

Description Issue UX priority
Mobile browser zooms in beyond the padding. User had a hard time scrolling without that padding. #2516918: Prevent mobile browsers from zooming on all form inputs major
"Display of preview bar on mobile was broken — items overlapped." #2524284: The spacing of the buttons in the preview bar is cramped on narrow screens normal
(In iOS) User tried to bold two things. The first word bolded just fine, but when trying to highlight a new word, user had to try twice. normal
"Manipulating text on a small viewport was troublesome. ""If I try and scroll up to the formatting buttons, I'm afraid it'll lose my selected text.""" normal
Attempted to boldify text by tapping the word and using iOS controls. minor
Expected text can be doubletapped on mobile. minor

Comments

webchick’s picture

Wrong tag. :)

cilefen’s picture

What makes you think there will be any? ;-)

webchick’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes
eliza411’s picture

Issue summary: View changes
webchick’s picture

Ugh, thank you. I still struggle with saying things correctly. :(

jhodgdon’s picture

Note to coordinators/committers for this effort:

We have gone through *every* hook_help() and updated it over the past couple of months. With few exceptions, I think the help now matches the UI. So, when UI is updated, please also update the hook_help() so it stays correct and matches how Drupal actually behaves. This almost never happens and it needs to. Thanks!

webchick’s picture

Roger that! :)

webchick’s picture

Issue summary: View changes

Moving to tables instead of lists for better scannability.

lunk_rat’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes

Ok calling it a night. ~50 down, ~90 to go. ;(

LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
ivanstegic’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes

Passing the baton to @Michelle. ;)

LewisNyman’s picture

Issue summary: View changes
Michelle’s picture

Issue summary: View changes
Michelle’s picture

Issue summary: View changes
ivanstegic’s picture

Issue summary: View changes
Michelle’s picture

Issue summary: View changes
ivanstegic’s picture

Issue summary: View changes
lunk_rat’s picture

Issue summary: View changes
lunk_rat’s picture

Issue summary: View changes
lunk_rat’s picture

Issue summary: View changes
ivanstegic’s picture

Issue summary: View changes
lunk_rat’s picture

Issue summary: View changes
ivanstegic’s picture

Issue summary: View changes

Done for today! Great sprint guys :)

lunk_rat’s picture

Issue summary: View changes
lunk_rat’s picture

Issue summary: View changes
webchick’s picture

Category: Task » Plan
Status: Postponed » Active

Just switching this to a Plan, since this issue itself is not actionable. Also marking active, since the testing already happened and there *are* actionable things referenced from it right now!

For anyone following along, @Michelle did AMAZING work making sure all of the issues we found during UX testing are in the issue summary. YAYYY! The next step is going to be to create issues for all of these, with the proposed suggestions from the spreadsheet in the issue summary of those issues.

I feel like at least some of those issues will need to be created by someone who saw the UX testing in person (we're working really hard to get the videos of these sessions posted publicly, which should hopefully happen sometime this week/next so others can see too), but there are also lots of problems that are pretty straight-forward and clear. So please feel free to take an row in a table which doesn't have any issue linked and add one! (Tag "UMN 2015" and "Usability" please)

webchick’s picture

Issue summary: View changes

Big update, putting everything into categories, sorting within those categories by priority, adding a table of contents.

webchick’s picture

Issue summary: View changes

Smart quotes will be the death of me.

lunk_rat’s picture

Issue summary: View changes
lunk_rat’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes

Based on discussions with the team, adding a suggested commit message to the issue summary for all UMN 2015 issues, based on the criteria of:

1) Sat through at least one of the 3 grueling days
2) Actively participated during the UX testing (note-taker, scenario-writer, etc.)

darol100’s picture

Issue summary: View changes
andypost’s picture

line 5&6

Change the order of the structure page so it's not alphabetical.

comment and content types are needs ordering at least - #2230177: Without Field UI comment module presents a poor UX

LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
LewisNyman’s picture

Issue summary: View changes
webchick’s picture

Issue summary: View changes

Adding https://www.drupal.org/u/mark-lacroix to the recommended commit message. He is doing yeoman's work to ensure we can get WebEx videos into a standard format while preserving participants' anonymity.

cilefen’s picture

Issue summary: View changes
cilefen’s picture

Issue summary: View changes
lunk_rat’s picture

Issue summary: View changes
webchick’s picture

In awesome news, the critical blocks issue we identified in testing was just resolved! :D #2512456: Implement the new block layout design to emphasize the primary interaction of placing a block And in fixing it, we took out #2513528: Add a link to add a block in empty regions on the Block layout page. in the process.

Other issues recently fixed include:

Off to a rockin' start. :D

Also, the videos have been processed and we should have a blog post up soon with a better summary and pointers to that.

daffie’s picture

@webchick: When all or most issues are fixed are you going to do another usability testing to see it is now good enough.

webchick’s picture

The University of Minnesota has tentatively offered to host us next year for another round of UX testing, so we could know for sure then. However, in the meantime, I'd prefer us to embrace more informal usability testing in between rounds of formal testing. I just do not personally have a lot of experience in this area, beyond having read http://www.sensible.com/rsme.html and gone "YES!!" all the way through. :)

Gábor Hojtsy’s picture

@webchick: while certainly not that professional, it is possible to do usability testing with a good script and google hangouts on air (for video and audio recording). We used that setup for several rounds of multilingual usability testing (see https://groups.drupal.org/node/271918). I think you considered that good enough of a testing setup to not test the features this time, so such a setup would be good to retest things. A good script is definitely useful, Dharmesh and Lisa helped us a lot back then with that, unfortunately neither are active in the Drupal community anymore :/

mbrett5062’s picture

I have recently opened an issue Add an extra "Save" button to the top of long admin list pages (Modules, Blocks, Permissions, etc).

I think it may be worthy of consideration as an improvement. While I did not see mention of it as an issue in the usability testing, I think it could still be helpful.

LewisNyman’s picture

The script we used for the UMN study should be freely available to copy and edit. @webchick @bojhan is there a canonical link to it? We should be able to provide a script for less formal testing.

webchick’s picture

It's in the issue summary (albeit buried) at https://docs.google.com/document/d/19GAnkMk6UBkRLR-LgojdU4KNY_RCVKIORinr....

We will make a canonical page for this under https://www.drupal.org/usability-tests but that's blocked on a blog post generally announcing all the things, including videos. Hoping to get to that this week.

ivanstegic’s picture

Issue summary: View changes
dasjo’s picture

tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

tedbow’s picture

Does anyone know which version of Drupal's were using?

In reviewing a child issue #2361921: Re-order the 'place/configure block' form so it's focused on the task at hand. I assumed they were using drupal 8.0.0-beta12 because it came out right after the testing but they were likely using beta11.

I think it is important so that we know which UI they were dealing with. I would update the issue summary if I knew the version.

Gábor Hojtsy’s picture

I fast-forwarded through https://events.drupal.org/barcelona2015/sessions/making-drupal-better-ou... (video recording) and did not find the information. However there are participant video snippets, so you maybe able to tell from the state of the UI there. (Or from the session if I was not attentive enough and it is indeed covered).

tedbow’s picture

@Gábor Hojtsy thanks for linking this.

for my purposes in #2361921: Re-order the 'place/configure block' form so it's focused on the task at hand. it least confirm that testing was done before the "Place Block" button next to each region and when the list of blocks was on the right
https://youtu.be/E31e5hzHMOE?t=19m

But I guess the fact that #2512456: Implement the new block layout design to emphasize the primary interaction of placing a block was a child issue of this also would tell me that

webchick’s picture

Version: 8.1.x-dev » 8.2.x-dev
Issue summary: View changes

Adding Quick Edit visibility issue.

Bojhan’s picture

@tedblow This was before those changes. The list of blocks was on the right in the testing.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

Issue summary: View changes
tkoleary’s picture

tkoleary’s picture

Issue summary: View changes

Added layout issue from ideas queue #2811175: [plan] Add layouts to Drupal

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.