Using the DEIMS profile

Here you will find some documentation pages to use the features that the Drupal Ecological Information Management System (DEIMS profile) offers. If you are looking for a how-to install guide, please follow this link.

There are several DEIMS-specific tasks you may want to read about.

ThemeKey

Themekey is a powerful theme switching system. You can create all kinds of recipes to

  • Install
  • Mobile Detect
  • Properties
  • Operators
  • Configure
  • Theme Switching Chain
  • Redirecting Rule Chain

Settings

General Tab

These are some general settings for how rules interact with cache, authenticated, and anonymous users.

Framework Organization

This section describes the various parts of the framework, their purposes, and the modules that implement them.

Discography Entities and Fields

Within Drupal, discography information is saved inside an entity type. Usually, that entity is a node type, but it could be a custom entity type, or a system of related node types (like Pushtape Discography), and it can have different kinds of fields.

The Discography Framework provides one field, and two node types:

  • Track Field: This is a field that holds information about a single track. You can add this field to any content type (such as an audio node). In addition to the multiple built-in formatters and widgets, the field is fully themeable using a template.

    Both the Release Node and Track Node modules are dependent upon the Track Field module.

  • Track Node: This is provided for sites that focus on tracks, rather than albums or releases. It is essentially a node wrapper for a single instance of a Track Field. Of course, site administrators can also add whatever fields they want through the Fields UI, just like any other node type.
  • Release Node: This node type handles information for a single discography release. It is probably the most important part of the framework, from the user's perspective.

Track Field guide

The Track Field has several different widgets and formatters, so that it may be used in a variety of situations.

Widgets

Widgets are ways that the field can be presented to the user when editing the field. The Track Field provides these widgets:

  • Form fields: Presents plain ol' Drupal form fields.
  • Table: The fields are presented in a table format.
  • Form fields, single track: Same as the Form Fields widget, but provides additional fields that are unnecessary when entering tracks on a release. Used by the Track Node module.
  • Table, single track: Same as the Table widget, but provides additional fields. Used by the Track Node module.

Formatters

Formatters are ways that the field can be presented to the user when viewing the field. Formatters are also integrated with the Views module. The Track Field provides these formatters:

  • Theme Template (default)
    Uses a theme template to display the tracks. The theme template is called
    discog-field-track.tpl.php, and may be overridden by any theme developer.
  • Formatted Text: Displays tracks as text, wrapped in HTML tags. Empty fields are not displayed.

Contributing to Symfony Documentation

THIS PAGE IS A WORK IN PROGRESS... It should have more information shortly!

This document covers updating documentation (online and API) for the Symfony component of Drupal (adopted in Drupal version 8).

Background and Overview

In Drupal version 8, the Drupal Core project adopted several third-party libraries into its source code, including the Symfony web development framework. The Symfony library is under directory core/vendor/symfony in the Drupal core source code (version 8), and other PHP-based libraries are in other directories under core/vendor. There are also third-party JavaScript libraries in Drupal, such as JQuery (which has been part of Drupal for many versions); these have traditionally been located in the "misc" directory, mixed in with Drupal-native JavaScript libraries.

If you find an error or omission in Symfony's documentation and would like to contribute to the Drupal and Symfony projects by fixing it (or at least pointing it out), the basic steps are the same as contributing to the Drupal API documentation:

Pages

Subscribe with RSS Subscribe to RSS - documentation