The Installation Profiles intro paragraph could use some revision in keeping with the MBD editorial guidelines. (Obviously the current content came directly from the existing Install Profiles page and no one has taken a pass at revising it yet.) Rather than starting with the developer-centric "Installation profiles are a feature in Drupal core that was added in the 5.x series," we should start with the definition of an installation profile and what it can do for you.
Here are some pages I found with more user-friendly descriptions of installation profiles that could be mined for and improved intro paragraph:
From http://groups.drupal.org/node/1041 (geared at art & music but could easily be altered to be more general):
What's an install profile and why is it important?
An install profile is a way of pre-configuring drupal right out of the box for a specific purpose or community. You can think of it as a template for a new drupal site. After you install drupal, the site will be pre-configured and customized out of the box (i.e. it will install and configure modules for you). The whole idea is to help you get from point A to B much faster. So if you are a band or musician looking to use drupal, you don't have to worry about figuring out how to download, install, and configure each module from scratch. You pick the install profile closest to your needs, and wham! Instant, functional site, with virtually no setup. Of course you will still have to know how to configure and customize Drupal to fit your specific needs if you want to make changes, but it sure will save a ton of time during installation and setup.
This is important for art and music communities - especially those that are non-technical - because it provides rapid deployment of very useful Drupal sites and minimize the headaches associated with installation.
From http://www.lullabot.com/articles/5-step-drupal-distributions (the article is mostly about creating a profile but has a good definition:
An installation profile is basically nothing more than a list of required modules and a variety of configuration code which gets performed during installation to give Drupal a bit more oomph out of the box.
From http://drupal.org/node/159730:
An installation profile is a simple file that tells the Drupal installer to enable a set of core and/or contributed modules, as well as to configure some default settings. ... For example, an installation profile for "Drupal band sites" might automatically install modules for e-mail newsletters, events and downloadable audio files.
It also looks like we should consider this thread as we create the language to describe installation profiles.
Comments
Comment #1
drummEdit here: http://drupal.org/admin/content/taxonomy/edit/term/96?destination=admin/...
Will show on http://drupal.org/project/installation+profiles and http://redesign.drupal.org/project/installation+profiles
Comment #2
drummComment #3
lisarex commentedI have revised this copy and it's ready for review.
Comment #4
Anonymous (not verified) commentedI created this fork of bmann's post on github:
http://gist.github.com/534151
review, revise, etc
Comment #5
lisarex commentedCool, I liked a lot of that phrasing and have incorporated it.
Comment #6
boris mann commentedHmm, weird -- I thought I submitted what I posted. http://gist.github.com/534056
Thanks @banghouse @lisarex - I think we are good to go for now. I edited the docs as well with some links. http://drupal.org/node/159730
Comment #7
Anonymous (not verified) commentedNP. Let me know if my input is useful elsewhere. I'll be happy to add my thoughts.
Comment #8
lisarex commentedComment #10
lisarex commentedThe description was really long when viewed in situ, and I noticed the handbook page version had links and whatnot. Plus, it probably makes sense to link to the handbook in the description, so I've revised/shortened this:
I also updated the handbook page.