Follow-up to #2497361: [meta] Fix issues found during UMN Usability Testing 2015

Problem/Motivation

User expected a much more fleshed out basic install. Made Drupal appear limited in functionality.

Proposed resolution

Add a new install profile that is Standard, plus some demo content.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

cilefen’s picture

Priority: Critical » Major

This is UX Critical but I think it is supposed to be Major here.

larowlan’s picture

*cough* github.com/larowlan/default_content was built for snowman, which is basically what this is

Bojhan’s picture

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

I am not sure how actionable this is for the 8.0 release, moving it to 8.1

tkoleary’s picture

@larowlan

*cough* github.com/larowlan/default_content was built for snowman, which is basically what this is

Was there actual content created for Snowman? That is the hard part, I think.

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

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now 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.

yoroy’s picture

Issue tags: +ux-workflow
vilepickle’s picture

Would it be better to have not only demo content, but more/different modules enabled than just what standard does? If so, what modules?

Just comparing the existing profiles...

  • Standard: Most immediately useful things are enabled, some things you don't want are enabled
  • Minimal: Almost an "oh crap, I didn't realize that wasn't enabled" level of nothingness is enabled

It would actually be very useful to go into detail on what these profiles have enabled, what to expect, etc. when installing.

I can also see other levels as a possibility, maybe more than 3 being useful if they actually got into more detail. Really I'd love to see the whole default install profile thing fleshed out more.

yoroy’s picture

Absolutely, it's about more than sample content alone. I think we currently lack the heuristics for deciding what the featureset(s) should be.

tkoleary’s picture

@vilepickle @yoroy

True, there is more to it.

I think perhaps even more important than modules is content model. We need to think about which content types and relationships should be there that would be broadly useful.

For example I think a great many sites across a variety of industries would benefit from:

Content type: Event
Contains:
-Name
-Date/time
-Venue, which references location
-Register, which links to Registration form

Content type: Location
Containing:
-Location Name
-Address (uses address field module)
-Hours of operation

Form: Registration form
Captures:
-Name
-Address
-email
-Phone
And gets saved to content type "Person" with term "Event attendee"

Content type: Person
Contains:
-Name
-Address
-email
-Phone
-Term: attribute (Eg. Event Attendee)
-Is User? (boolean)
-User id

The presence of these would enable default content that included a view of events, A view of locations, A view of registered attendees, etc. etc.

Without some basic structure like this you could make a list of events with times and dates and locations in the body of a node but you'd be teaching the user the wrong thing about Drupal.

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.

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.