Decide on direction for default install profile
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | install system |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | default.profile, installation profiles, Needs usability testing, Usability |
Jump to:
webchick asked me to start an issue for deciding what we're going to do with the default install profile, as it is starting to block other issues such as #79582: Add an initial "welcome" node in default install profile
I've been wanting to do a "Community in a Box" as the default install profile, and have documented that on a g.d.o. wiki page http://groups.drupal.org/node/21013 (I also have some D6 code for experimentation in a Google Code SVN repo at http://code.google.com/p/drupal-oob/ - I haven't begun on a D7 trial yet, but can switch to focusing on that).
I suggest we either directly edit that g.d.o. wiki page OR have other people create their "alternate vision" for what Drupal's default profile should do out of the box.
Aside #1: not checked in anywhere, but I was very easily able to make a "Photos" component using Features. This feels like the right way to do these kind of bundled components, whether it is Photos, Multi User Blogs, or Forums.
Aside #2: we probably need a new component for issues - default.profile and minimal.profile
#1
Create some sort of wizard/buttons that one can select and choose the profile (get list from d.o), download the profile & install. That way we can ship with anything... this is of course pending on #395480: Plugin Manager in Core: Part 4 (installation profiles). All the complexity's aside, asking the user is the best way to go if we don't go the download route. Ship with like 5 simple default profiles (instructions on how to get more complex), first one being minimal.
Is there any way to get the php memory limit? That way the admin knows what he has to work with and the requirements for each part in the wizard.
#2
Sorry, but that's not a realistic proposal. And, we'll STILL need at least one default install profile that is actually bundled into Drupal. And ... until I see more evidence of people actually building more install profiles, then proposing to ship with 5 or download them from Drupal, it's not going to work.
EDIT: I realize I may have been too harsh. What I am trying to stay focused on HERE is to actually get a new, default profile in place to make a great out of the box experience when Drupal 7 ships.
I think Plugin Manager absolutely should support install profiles, but let's keep that discussion at #395480: Plugin Manager in Core: Part 4 (installation profiles)
#3
Hm Boris this does not stir the masses as it seems. Weird. So is momentum on this issue somewhere else?
Every minor text change gets 85 comments.
#4
@eigentor I fear that, in essence, the dev community is focused on building better frameworks to build stuff, but not on UX of out of the box experience.
#5
OK.
What can I do to help pushing this?
I edited the wiki in one point: I think Article should continue being promoted, as this is Drupal's basic blog functionality which is not bad IMHO. If we remove it Blog must be presented in a different way. Because if nothing gets promoted by default, uhm...
As to Photos: due to Quicksketch's endavour I think we will have Imagefield, Imagecache and filefield/imageapi in core.
How about creating a bit of random fun for the "photo" content type? I think of the following: Making a main image floated left (and if we find a way, add an ability to make it float right by choice) with a sensible margin (5 15 5 15 has proven to be a good practical value for me). This would need two imagecache presets. Should talk to Quicksketch about the chances of his plans about this, but it might give him further motivation.
And what about the wizard? I guess it must be coded, right?
As a daring thought it might be to pursue the thought of an "advanced" install profile that uses quite a bit of contrib - a bit like Acquia Drupal. The almost given fact that we will have Plugin Manager in Core makes Room for that vision. I know chances are not too big to get this in, but if we start now, maybe 10% are there. Great victories have been archieved with smaller chances. This could be a _true_ community in a box then.
Who else is on this track?
#6
Re: article -- yes, promoted by default, but not *published* by default. Anyone can submit an article, but only editors or admins can set them to published right away.
Re: image / photos. Yes, just as I was thinking -- Article would have such a small main image in the teaser (150px?), larger version (250px?) in full. Photos would be larger than article images (350px in teaser, centered, with text underneath, 550px in full post). So, 4 image presets.
The wizard is not particularly hard, but yes it needs coding.
Re: advanced -- no one, ever, has been blocked from creating more contrib install profiles.
Re: who else is on this track. No one is working on this.
#7
I'm really interested in this -- if we get some ideas then maybe I can get prototyping; I've done profiles before but this sounds really neat.
#8
@lunaris check out the wiki link - we (or at least I :P) know what we want to build, it just needs building, testing, and patches submitted.
#9
#10
Bump. Four weeks left to decide on which modules to enable/disable in the default install profile. Everybody interested, review http://groups.drupal.org/node/21013, it still is the most concrete proposal we have.