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

cilefen CreditAttribution: cilefen commented
Priority: Critical » Major

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

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
CreditAttribution: larowlan as a volunteer commented

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

Bojhan’s picture

Bojhan CreditAttribution: Bojhan as a volunteer commented
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

tkoleary CreditAttribution: tkoleary at Acquia commented

@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

yoroy CreditAttribution: yoroy commented
Issue tags: +ux-workflow
Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

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

yoroy CreditAttribution: yoroy commented

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

tkoleary CreditAttribution: tkoleary at Acquia commented

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

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.

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

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.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.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

quietone’s picture

quietone CreditAttribution: quietone as a volunteer commented

Does the new install profile demo_umami, that was added in #2809635: Create experimental installation profile, Jan 2018, fix this issue?

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Status: Active » Closed (outdated)

The has been no discussion here for seven years, except for me to ask if this resolved by the demo_umami profile.

The proposed resolution is to add a new profile which is standard plus some demo content. I do think that demo_umami fulfills that. Therefor I am closing this as outdated.