Building

Things and Stuff Wiki - An organically evolving personal wiki knowledge base. An on-the-fly taxonomy containing a patchwork trail of topic outlines, descriptions, notes, stubs and breadcrumbs, with links to sites, systems, software, manuals, organisations, people, articles, guides, slides, papers, books, comments, videos, screencasts, webcasts, scratchpads and more. Content is orientated towards mostly free/libre/open, mostly Linux. Quality and age varies drastically. Sometimes old things are first, sometimes last. Use the Table of Contents menu to navigate long pages. Zoom in if text is too small. Dead link? Wayback Machine. I probably need to fix the theme CSS after an update. See also libreav.org. Chat to msg me (not checking tho atm). e

Profiles

Install Profile in Drupal 7 is actually a few files: mysite.profile, mysite.info, mysite.install

Developing installation profiles
Install Profile Packaging
Packaging a profile on drupal.org (make file -> install profile)

Make install profiles inheritable

Articles

http://designhammer.com/blog/workflow-and-tools-developing-install-profiles-and-drush-make

Inheriting your Drupal profile from an existing distribution

Profiler

Enables the use of .info like syntax for profiles.

Profiler
- Readme
- Examples

https://drupal.org/project/profiler_builder

Aegir workflow

It's not best practice to try and store build .make and .profile/.info in the same repo. This would require one to set the profile download in the make file the be the same repo, thus causing Drush to download all .make projects twice.

Instead, a stub build .make file that points to said repo will download all properly. technique copied from mig5.

My profiles

See my Github

Base dev - old

to check;

Features

Features provides a UI and API for taking different site building components from modules with exportables and bundling them together in a single feature module. A feature module is like any other Drupal module except that it declares its components (e.g. views, contexts, CCK fields, etc.) in its .info file so that it can be checked, updated, or reverted programmatically.

Bundling site settings using Features

A new paradigm for overriding Drupal Features

Extras

http://drupal.org/project/features_extra

Installation

You use Features like Modules. They can downloaded using Drush or be called by a distros .make and .info. Features can also be sourced from a Feature Server.

Install from a Feature Server:

drush dl feature --source=http://www.darrenmothersele.com/fserver
or drush dl features_links --source=http://community.featureservers.org/fserver

Modules

http://drupal.org/project/ftools - gives the ability to remove elements from a feature and put them back to the DB. also Adds a submit button in the recreate feature form named "auto create feature" which downloads the feature tarball, un-tars it and put the files in the right place in one click. required web server directory permissions.

http://drupal.org/project/features_orphans - simply lists all Features-Exportable components that have not been exported to a feature.

http://drupal.org/project/uuid_features - provides a mechanism for exporting content (nodes, taxonomy, fields) into a features module. What's that you say? You thought features was only for configuration? This module is meant to be used in the cases where certain pieces of content straddle the line between pure content and configuration.

http://drupal.org/project/context_spaces_features - creates a condition for Context based on active Features in a given space

D6

http://drupal.org/project/modes - one-at-a-time meta features.

http://drupal.org/project/faccess - per feature user permissions

http://drupal.org/project/features_clone

Feature Server

Feature Server (fserver)

Distributed Feature Servers in Drupal, Dev. Seed, June 24 2009
Recipe For a Feature Server, Dev. Seed, June 26 2009

Directory of Public Features Servers

Git

Features to Git allows trusted users to write features directly to disk, commit them to git and push them to a remote. This makes it possible for site builders to be able to manage features in git without having to get their hands dirty on the command line.

Kit

Kit is a specification, a set of guidelines that facilitates building compatible and interoperable Features.

Debut

Debut is a set of baseline Drupal 7 Features designed to work independently yet integrate seamlessly together. Building on the Kit feature specification.

Debut Article: An article content type including media and block display.
Debut Bio: A user bio profile that can be displayed alongside e.g. blog posts showing the author's real name and bio.
Debut Blog: A Blog content type and recent blog post block display.
Debut Comment: Commonly needed functionality for commenting including comment notification, CAPTCHAs, and login enhancements.
Debut Event: An Event content type and calendar displays.
Debut Forum: Forum functionality integrating Drupal core Forum module and Advanced Forum.
Debut Highlighted: Highlight selected site content with slideshow.
Debut Link: A link content type and associated displays for presenting links to other sites.
Debut Media: media handling and display using the Media module.
Debut Section: Nested landing pages for the main sections of a site (using Book module).
Debut SEO: search engine optimizations including metatags.
Debut Social: A social media feature integrating some of the most commonly needed social media functionality.
Debut WYSIWYG: Input formats and accompanying editors, along with input formats per role.

Candidate

Other

Dashboard Views - A collection of preconfigured Views to add to the dashboard of your Open Atrium groups. Currently includes: Book pages (with "Add Book page" link), Member Listing (including admin vs. user status), Projects (Case Tracker or Case Tracker Plus), Shoutbox

Ideation - A crowd-sourced suggestion box, which allows users to: suggest ideas, vote on and discuss already submitted ideas, surface most important/best ideas, as well as start discussions around ideas.