J. Renée Beach jessebeach

## formerlatter.txt
Former and latter fun!

 * It is up to the class implementing this interface to manage where the
 * information comes from. For example, field.module provides an implementation
 * based on two levels of configuration. It allows the site administrator to add
 * custom fields to any entity type and bundle via the "field_config" and
 * "field_instance_config" configuration entities. The former for storing
 * configuration that is independent of which entity type and bundle the field
 * is added to, and the latter for storing configuration that is specific to the
 * entity type and bundle.

## gist:5fb25fb97a28f382af5e
<ul class="dropdown-menu" role="menu">
            <li class="heading cfx">
              <span class="left">Google Apps Domain</span>
              <span class="mid">Users</span>
              <span class="right">Status</span>
            </li>
            <li class="cfx">
  <a href="/settings/domains/1/dashboard">
    <span class="left">backupifydevman1.com</span>
    <span class="mid">9</span>

## gist:dc16a6ca5e9d92a9f66d
HTTP/1.1 200 OK
Content-Type: application/json
Link: <http://api.example.com/person.jsonld>;rel="http://www.w3.org/ns/json-ld#context"

{
  "n": "Jenny Gallegos",
  "photo_link": "http://www.example.com/img/omjennyg"
}

Example taken from: Richardson, Leonard.  "Restful Web APIs".

## admin.inc
// Add preview controls
    $form['displays']['preview_controls'] = array(
      '#theme_wrappers' => array('container'),
    );


    // Add a checkbox controlling whether or not this display auto-previews.
    $form['displays']['preview_controls']['live_preview'] = array(
      '#type' => 'checkbox',
      '#title' => t('Auto preview'),

## list with dividing line
<!DOCTYPE html>
<html>
 <head>
   <meta charset="UTF-8" />
   <title>Untitled</title>
   <meta name="viewport" content="width=device-width" />
   <style type="text/css">
     li {
       clear: left;
       display: block;

## acquia_base.info
name = acquia_base
description = Default XHTML starterkit for <a href="http://drupal.org/project/omega">Omega</a>. You should not directly edit this starterkit, but make your own copy. Information on this can be found in the <a href="http://himer.us/omega-docs">Omega Documentation</a>.
core = 7.x
engine = phptemplate
screenshot = screenshot.png
base theme = omega

; REGIONS

; REQUIRED CORE REGIONS

## gist:979735
name = acquia_com
description = Acquia.com theme. Sub-theme of acquia_base
core = 7.x
engine = phptemplate
screenshot = screenshot.png
base theme = acquia_base

; JAVASCRIPT

scripts[] = 'js/acquia-com.js'

## gist:979738
name = acquia_base
description = Acquia properties base theme. This theme should be sub-themed. It should never be published on its own.
core = 7.x
engine = phptemplate
screenshot = screenshot.png
base theme = omega

; JAVASCRIPT

scripts[] = 'js/acquia-base.js'

## proxy.html
<!DOCTYPE html>
<html>
 <head>
   <meta charset="UTF-8" />
   <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
   <title>Untitled</title>
   <meta name="viewport" content="width=device-width" />
   <!--[if lt IE 9]>
   <script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
   <![endif]-->

## minimal plugin
(function ($) {} (jQuery));
	Former and latter fun!

	* It is up to the class implementing this interface to manage where the
	* information comes from. For example, field.module provides an implementation
	* based on two levels of configuration. It allows the site administrator to add
	* custom fields to any entity type and bundle via the "field_config" and
	* "field_instance_config" configuration entities. The former for storing
	* configuration that is independent of which entity type and bundle the field
	* is added to, and the latter for storing configuration that is specific to the
	* entity type and bundle.
	<ul class="dropdown-menu" role="menu">
	<li class="heading cfx">
	<span class="left">Google Apps Domain</span>
	<span class="mid">Users</span>
	<span class="right">Status</span>
	</li>
	<li class="cfx">
	<a href="/settings/domains/1/dashboard">
	<span class="left">backupifydevman1.com</span>
	<span class="mid">9</span>
	HTTP/1.1 200 OK
	Content-Type: application/json
	Link: <http://api.example.com/person.jsonld>;rel="http://www.w3.org/ns/json-ld#context"

	{
	"n": "Jenny Gallegos",
	"photo_link": "http://www.example.com/img/omjennyg"
	}

	Example taken from: Richardson, Leonard. "Restful Web APIs".
	// Add preview controls
	$form['displays']['preview_controls'] = array(
	'#theme_wrappers' => array('container'),
	);


	// Add a checkbox controlling whether or not this display auto-previews.
	$form['displays']['preview_controls']['live_preview'] = array(
	'#type' => 'checkbox',
	'#title' => t('Auto preview'),
	<!DOCTYPE html>
	<html>
	<head>
	<meta charset="UTF-8" />
	<title>Untitled</title>
	<meta name="viewport" content="width=device-width" />
	<style type="text/css">
	li {
	clear: left;
	display: block;
	name = acquia_base
	description = Default XHTML starterkit for <a href="http://drupal.org/project/omega">Omega</a>. You should not directly edit this starterkit, but make your own copy. Information on this can be found in the <a href="http://himer.us/omega-docs">Omega Documentation</a>.
	core = 7.x
	engine = phptemplate
	screenshot = screenshot.png
	base theme = omega

	; REGIONS

	; REQUIRED CORE REGIONS
	name = acquia_com
	description = Acquia.com theme. Sub-theme of acquia_base
	core = 7.x
	engine = phptemplate
	screenshot = screenshot.png
	base theme = acquia_base

	; JAVASCRIPT

	scripts[] = 'js/acquia-com.js'
	name = acquia_base
	description = Acquia properties base theme. This theme should be sub-themed. It should never be published on its own.
	core = 7.x
	engine = phptemplate
	screenshot = screenshot.png
	base theme = omega

	; JAVASCRIPT

	scripts[] = 'js/acquia-base.js'