Public

Reportedly the e-mail to organic group (but not vice versa?) functionality has matured in several modules and is working. At the time of this posting the blog author's own module didn't have a proper official release.

http://api.drupal.org/api/function/hook_node_access_records/7
http://api.drupal.org/api/function/hook_node_grants_alter/7

A "sustainable" theme is one that can grow seemingly effortlessly as the site grows. It saves time reducing theme work in the long term, and allows developers to change and add new sections that just "look right" right away.
Agenda

Using the custom theme of a large website as an example, I will go over:

Mastering version control is what enables developers to create more robust projects. It helps to preserve not only your code base, but each incremental step to get there, allowing you to recover old code and revert code you no longer want.

Agenda

This session will be an introduction to the concept of version control, and how to put your custom Drupal theme in version control.

Drupal Design Camp Boston attendees will learn and share knowledge about Drupal’s powerful templating system. Over the two days, you can expect to gain knowledge on how to use starter themes, custom templates, modify code that Drupal produces, and how use jQuery and JavaScript to enhance user experience. Also, Drupal fundamentals are part of the framework.

So, how does one create a tag? Just git tag v1.0.0 right? WRONG. You usually don%u2019t want to do that. In fact, some suggest that this command does the wrong thing by default. Without arguments, git tag creates a %u201Clightweight%u201D tag that is basically a branch that never moves. Lightweight tags are still useful though, perhaps for marking a known good (or bad) version, or a bunch of commits you may need to use in the future. Nevertheless, you probably don%u2019t want to push these kinds of tags.

A website going into detail of all the typical workflows you encounter when managing a project using Git. Branching, tagging, fetching, rebasing, finding information... you name it, this website has it.

This module provides two additional Views display plugins, "Profile" and "Node content". These displays do not display on a page but get "attached" to either a user page or nodes of specified types. These views are not stored with the user or node, the way viewreference.module would, so they can be globally-reconfigured.

The node content display can be reordered on the "Manage fields" tab if CCK is enabled. If not, it will have a weight of 10 so it floats to the bottom of the node.
Usage tips