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.
Since UX is a big issue, perhaps it would be a good idea to explain the Installation Profiles when the user has to select either standard or minimum. Right now everyone is properly selecting "standard", because it is impossible to tell from the installation screen the consequences of either choosing standard or minimum.
Comments
Comment #1
arianek CreditAttribution: arianek commentedtags/status
Comment #2
markandphil CreditAttribution: markandphil commentedThis made us surprised as well. Makes no sense to have these choices without explaining the context of each. A google search also produces no results on their differences either.
Comment #3
Carolyn CreditAttribution: Carolyn commentedThe difference between the two profiles is mentioned here: http://drupal.org/node/251031
I don't see a page in the handbook that goes into all the details. I compared the two profiles and this is what I found.
The Standard profile has several core modules enabled. It has more default configuration set up, including several default admin tools. This profile does more to show what core can do, and can save site building time by having defaults for common use cases.
The Minimal profile has only a few very basic modules installed. This profile is useful if you only want very specific features, or if it will take more work to undo the defaults provided with the Standard profile.
Here are the details.
This table shows what extra modules will get enabled with the Standard profile:
Note: There are core modules not enabled in either profile, and those are not included in the table. It is correct to say that Database Logging and Block are the only two modules that are enabled in Minimal. The other modules are required by Drupal. Update Status depends on the user choosing updates during installation.
Structure
Content types
Minimal - There are no content types to start.
Standard - 2 premade content types, Basic Page, and Article
Basic Page - not promoted to front page, comments disabled, author and date not set to display, rdf mapping 'foaf:Document'
Article - a default taxonomy named "Tags" enabled. Set to display author and date info, comments enabled. Comes with an image field. The image field has an rdf mapping of 'og:image', 'rdfs:seeAlso' and the tags field has a rdf mapping of 'dc:subject'
Menus
Both - 4 default menus. The Navigation and Management menu blocks appear by default in Bartik's first sidebar, and the user menu is printed in the upper right.
Minimal - The menu module is not enabled. Menus cannot be added or edited under Structure > Menus until the Menu module is enabled.
Standard - Default home link in the Main Menu
Blocks
Minimal - The default Bartik theme has the following blocks enabled:
System help in the Help section
Main page content in the Content section
Navigation, User login, and Management in the Sidebar first section
Standard - The default Bartik theme has the following blocks enabled:
System help in the Help section
Main page content in the Content section
Search, Navigation, User login in the Sidebar first section
Powered by Drupal in the Footer
Appearance
Minimal
Bartik is the default theme and the default admin theme
Standard
Bartik is the default theme
Seven is set as the admin theme, and set to appear when editing or creating content
Global and Bartik initial theme settings are the same.
Configuration
Account settings
Minimal - no default roles, no default admin role
Standard - There is a default role for administrator, who is set as the default admin role. User pictures are enabled.
Text formats
Minimal - One Plain text format (default with drupal)
Standard - 3 text formats, Plain text, Full HTML, and Filtered HTML
Media
Standard - has three default styles: thumbnail, medium, and large (Minimal does not have the Image module enabled.)
Database tables installed
Minimal - 48 tables installed in the database
Standard - 73 tables installed in the database
Should the Install UI just have a succinct summary, or should it also link to a page with more details?
Comment #4
ldpm CreditAttribution: ldpm commentedI've added those comments to the installation profiles page:
http://drupal.org/node/306267
Comment #5
arianek CreditAttribution: arianek commentedcarolyn that is fantastic!!!!!
one thing though, i think it could stand to be in its own page - a second child page to http://drupal.org/documentation/install/run-script
opinions?
Comment #6
lucy CreditAttribution: lucy commentedAnd what about giving the user some information about other install profiles too? At least link to the page with their listing. Or some kind of preview of most used or safe or reccomended.
It would save time and give right direction to somebody who tries to build a small shop for example. He comes to Drupal as most flexible, cool etc., but does not know which modules are safe choice to start with and does not know anything about install profiles. (Who reads docs before first error, huh?;)
It could be also a new path to learn Drupal and make it more selfexplaining. And I believe that implementing this carefully, it won't distract users from the installation process. Or it will, but in the right time - time to choose some profile and prevent hours of setup later.
Comment #7
watbe CreditAttribution: watbe commentedI have a suggestion to add a link to the child page http://drupal.org/node/1127786 in the paragraph titled "1. Choose which profile to use for the installation (standard or minimal)." in http://drupal.org/node/251031
The run-script page is designed as a step-by-step guide and most users would not scroll to the bottom to look for an elaboration on the default installation profiles provided.
Comment #8
jhodgdonI am pretty sure that everything discussed here has actually been done.