documentation

Style Guide: Helper functions

Style Guide uses the following helper functions to generate content:

  • styleguide_list() - return a simple array of words
  • styleguide_word() - return a random word or words.
  • styleguide_header() - return a random table header array.
  • styleguide_rows() - return a random table row array.
  • styleguide_lorem() - return Lorem Ipsum text, used to generate words and phrases.
  • styleguide_paragraph() - return HTML paragraph(s) of random text
  • styleguide_image() - provide a default image for display.
  • styleguide_sentence() - return a random sentence.
  • styleguide_form() - return a sample form, showing all form elements.
  • styleguide_pager() - simulate Drupal pagination
  • styleguide_links() - return an array of random links
  • styleguide_menu_item() - return a random menu item
  • styleguide_ul_links() - return a links array for theme_links()

Style Guide: API

To change the list of items displayed by Style Guide, third-party modules
can implement following hooks, located in styleguide.api.php:

  • hook_styleguide()
  • hook_styleguide_alter()
  • hook_styleguide_theme_info_alter()

hook_styleguide()

hook_styleguide() allows you to define an array of items to render for theme testing. Each item is rendered as an element on the style guide page and should be keyed with a unique identifier. This value will be used to create a named anchor link on the Style Guide page.

Read more

Style Guide

Style Guide provides a visual testing page for Drupal themes. Quickly compare the display of common elements across your themes, and verify that your new theme addresses all common style elements.

Overview

The Style Guide module creates a preview page for displaying common theme elements in all active themes for your Drupal site. The module comes with previews for common HTML elements, such as tables, forms, links and lists. The Style Guide module creates an API and preview page for displaying common theme elements. Use it to preview items such as tables, menus, and lists in your custom themes.

Purpose

The purpose of a visual style guide as both a general theming and development tool is to ensure that common site elements are styled in a consistent and intentional way. For further reference see

Installing Style Guide

See Installing contributed modules

Using Style Guide

    Read more

    OG Tasks Documentation

    OG Tasks provides a mechanism to create tasks to be run for a group, either automatically on creation, or optionally once the group has been created.

    Tasks are defined by way of a hook function, hook_og_tasks_info(). This function takes two parameters: $entity_type and $entity. Both of these parameters refer to the OG entity. The type is often "node" or "taxonomy_term", and the entity itself as an object is passed into the second param. They can be used to set up different tasks for different types of OG objects, for example.

    The hook_og_tasks_info() function should return an array of og_tasks objects.

    A typical hook_og_tasks_info function will look something like this:

    <?php
    /**
    * Implements hook_og_tasks_info().
    */
    function my_module_og_tasks_info($entity_type, $entity) {
     
    $tasks = array();
     
    $path = drupal_get_path('module', 'my_module');

     
    // Navigation menu.
     
    $tasks['menu'] = new og_task(array(
       
    'title' => t('Create Navigation'),
       
    'description' => t('Creating a menu that is associated to the site that will drive the navigation.'),
       
    'required' => TRUE,
       
    'callback' => 'my_module_og_task_create_menu',
       
    'file' => $path . '/includes/menu.inc',
       
    'completed' => my_module_has_menu($entity),
      ));

      return
    $tasks;
    }
    ?>
    Read more

    Drupal Malayalam toutorial

    Drupal Malayalam toutorial PDF document.
    {Uq]Â F¶ tIm−âv amt\Pvaâv knÌw: Hê ]cnNbw
    iÐw, Nn{X§Ä, Ne ̈n{X§Ä XpS§nbh DÄs ̧sS FÃmhn[ I1⁄4}«À ^bepIfpw
    IrXyamb coXnbn ]cn]men¡m3 D]tbmKnç¶ I1⁄4}«À A1nt¡jëIfmWv,
    tIm−âv amt\Pvaâv knÌw F¶dnbs ̧Sp¶Xv. ]cn]mençI F¶XpsIm−v,
    \nÀ1⁄2mWw,{]kn2oIcWw,]cnjvIcn ̈
    ]Xn ̧v
    {]kn2oIcWw,]p\x{IaoIcWw
    FìXpS§nb FÃm {]{InbIfpw hnh£n¡s ̧«n«p−v. tIm−âv amt\Pvaâv knÌw
    Fì]dam shdpw ASnØm\kuIcy§Ä am{Xw Hê¡n ̄ê¶ Imenbmb Hê
    sh_vsskäv F¶v (sh_vsskänsâ AØnIqSw) hnh£n ̈m AXn sXäv ImWnÃ.
    DÅS¡w Ft ̧mgpw sskäv \nÀ1⁄2nç¶hêsS Cã ̄n\ëkcn ̈mbncnçatÃm.
    CXpaqew, sh_vsskäv \nÀ1⁄2mW{]{Inbbn IqSpX {i2sImSp¡msX \ap¡v,
    \1⁄2psS sh_vsskänsâ DÅS¡ ̄nsâ KpW\nehmc ̄n IqSpX {i2n¡m3
    ]äpì Fs¶mê kuIcyw IqsS D−v.

    User / Field instructions for Edit Entityform Type form

    Entityform user documentation (version 7.x-1.0-rc2)

    This document will provide instruction regarding what information should be supplied to each question on the Home » Administration » Structure » Entityform Types » Edit "Form Name" form.

    We have documented all of the fields on the Edit Entityform Type edit screen. While you can read all of the user documentation, you can click on the below links and it will take you directly to the instructions for the specified field.

    Read more
    Subscribe with RSS Syndicate content