Distributions provide site features and functions for a specific type of site as a single download containing Drupal core, contributed modules, themes, and pre-defined configuration. They make it possible to quickly set up a complex, use-specific site in fewer steps than if installing and configuring elements individually.
Turning pressflow into fastflow by adding configuration the CDN module for "parallelizing requests across hostnames", the cookie domain will appear as editable as well, with a suggested domain based on the CDN rules to not serve any static resources from as the "cookie domain".
Eventually I'd like to add install wizard support for a bunch of SEO modules, the module that runs all those web accessibility tests, and s default mobil domain setup & configured theme. I'll figure it all out eventually I'm sure, having "FastFlow,Mobile,Accessibility,SEO" distribution.
This installation profile was created in 2011 to help (primarily) Roman Catholic Parishes in the U.S. provision a website quickly, using sensible defaults and Drupal/web/SEO best practices. The profile provided a baseline website that parishes could use or emulate in building their own online presences.
This sets up the Project* modules for the Drupal.org use case.
Clone the '7.x-1.x' branch of this project using the instructions found in the 'version control' tab above, and then use the drush make build-projectinstall.make --prepare-install --working-copy d7project command to download Drupal 7 core and all the modules needed for this installation profile into a folder called 'd7project' inside your current working directory.
While working on a project with the Palmetto Technology Hub, a couple folks from #chsdug found there are no great open source systems to run a multi-user, client-facing helpdesk. Most open source options haven't been updated in 2 years or longer. All the proprietary options that are halfway decent are expensive.
As a result, we're building a distro called FLOSSDesk. The goal is to use core and contrib code whenever possible to ease upgrades and ongoing management.
Case creation by agents or clients
Internal and external case notes, with a single chronological view of a case
Automatic email to client or agent when external notes are added to a case
Reply-by-email to notifications, with attachment handling
Notification to old agent when a case is taken over by a new agent
Ability to change case attributes (severity, status, assignment) without going into the node edit form
View of "My Cases" for clients
Views of "My Assigned Cases" and "All Open Cases" for agents and managers
In development and planning:
Automatic service level management and escalation notifications