Work in progress.
Externals are not supported by git.
This guide is intended to help orient a developer on the customizations and structure of the Open Source Design Pattern library as implemented in Drupal 5.x.
This guide assumes you have some understanding of Drupal or plan on learning it yourself. As such, this document will not cover topics that can be learned elsewhere, instead will focus on OSDPL specific details in Drupal.
The following is an outline of the repository structure for the OSDPL:
./drupal-5.x /files (directory for all uploaded user content) /sites /default /modules (Contains external references to modules hosted elsewhere or in the ./vendor directory. Does not actually contain any physical files at this time, just references to other resources.) /themes (Contains the theme currently used and modified for the OSDPL) ./vendor /drupal-contrib (Contains specific versions of contributed modules /akismet used by the OSDPL and not hosted in an SVN repository /5.x-1.1 elsewhere. Externals properties in /cck_blocks /drupal-5.x/sites/default/modules reference these files.) ...
SVN repositories for Drupal and modules:
Work done to the OSDPL can be contributed back using two methods:
All OSDPL related bugs and tasks are tracked in the Fluid Project Jira bug tracker. If you are looking for things to do, this is a good place to start.
Caution is required if updating Drupal core or contrib modules, and you will also need commit access to the Fluid OSDPL repository. (If you do not have commit access, then please send a message to the Fluid-work mailing list requesting the update to Drupal).
Using the Repo structure above as a reference:
To summarize, Fluid should only manage a Drupal module only if that module does not appear in a SVN repository elsewhere.
Design patterns, when authored, can take on 4 different states selected using the CCK form: Private Draft, Open for Comments, Request for Review, and Published. These states are defined using the Workflow_NG module and the different actions taken for each state change can be seen by accessing the Rule Configurations.
Private Draft: The node is only visible to the content author and administators. No one else is able to view or edit.
Open for Comments: Registered users or higher can view and comment on the design pattern. Anonymous / unregistered users will not be able to see this content.
Request for Review: Viewable and editable by Pattern Editors or higher. Registered users and anonymous users will not be able to see this content.
Published: Viewable by everyone.
Four basic actions are done for each event fired in the Workflow:
Items 1 - 3 help implement the access rules for the given state.
Note: When switching states to "Comments", "Review Request", or "Published", the content is actually published in Drupal (i.e. node status is set to 1). This is so that registered users can comment if in the "Comments" state, and pattern editors view and edit in the "Review Request" state.