Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
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.
Comments
Comment #1
cilefen CreditAttribution: cilefen commentedThis is UX Critical but I think it is supposed to be Major here.
Comment #2
larowlan*cough* github.com/larowlan/default_content was built for snowman, which is basically what this is
Comment #3
Bojhan CreditAttribution: Bojhan as a volunteer commentedI am not sure how actionable this is for the 8.0 release, moving it to 8.1
Comment #4
tkoleary CreditAttribution: tkoleary at Acquia commented@larowlan
Was there actual content created for Snowman? That is the hard part, I think.
Comment #6
yoroy CreditAttribution: yoroy commentedComment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedWould 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...
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.
Comment #8
yoroy CreditAttribution: yoroy commentedAbsolutely, it's about more than sample content alone. I think we currently lack the heuristics for deciding what the featureset(s) should be.
Comment #9
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.
Comment #19
quietone CreditAttribution: quietone as a volunteer commentedDoes the new install profile demo_umami, that was added in #2809635: Create experimental installation profile, Jan 2018, fix this issue?
Comment #24
quietone CreditAttribution: quietone at PreviousNext commentedThe 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.