(Bug 5073) Create [% form.radio_nested %] / [% form.checkbox_nested %]

This is used on Foundation pages (different HTML structure)
(Bug 5073) Adds per-form-element error messages
(Bug 5073) Add a 1em left margin to all lists

list-style-position: inside was causing issues with the table cell being
too narrow in chrome
(Bug 5073) Create pagination template

Template meant to be included within other templates; goes into
views/components.
(Bug 5073) Separate out screenreader-friendly styling

Include for the elements you need by doing:

* @import "mixins/screenreader-friendly"
* .element-that-needs-to-be-hidden-visually-but-not-from-screenreaders {
	@extend %screenreader-friendly
  }
(Bug 5073) Initial load of pages should have no-js class

Use it to hide elements that require JS to work (class will be changed
after page has loaded)
(Bug 5073) Add LJ::send_formatted_mail / LJ::format_mail

Wrapper around LJ::send_mail, which accepts most of the same arguments.
The big difference is that you don't need to specify plaintext vs html:
just pass in a body argument, and it will use that as the plaintext
body, and then process the text with Markdown to get an HTML version
(Bug 5073) Move greeting/footer logic into LJ::format_mail

Much easier to test, because you know the full text of the email (rather
than having to guess if you need to put a newline or not).

For the record: no need for additional newlines before/after the body.

Patch includes whitespace fixes in the text of the test emails
(Bug 5073) Better detection of links in Markdown

Don't just remove any brackets; look for any brackets immediately
followed by parentheses.
(Bug 5073) Create Style Guide

/dev/style-guide, shows how each component appears, as well as
providing examples for the HTML structure.

Foundation-specific.
(Bug 5073) Add a "select-all" checkbox component

Given something with the appropriate HTML structure (see
dev/style-guide for an example), style it and initialize the JS.
(Bug 5073) Fix the position of the form error message
(Bug 5073) Use alert-box instead of panel for error msgs summary

At the top of the page
(Bug 5073) Finish converting dw-free skins

* Assign variables in Celerity / Gradation

* Tweak implementation of elements such as alert boxes, panels, tables

* Convert lynx
(Bug 5265) Convert /community/index to TT + foundation
(Bug 5265) Convert the list on /community/manage to TT + foundation

* moves the page from /community/manage to /communities/list
  The form elements for community settings at the bottom are still undone

* modifies the appearance and order of the links to be a bit less jumbled together

* converts from BML to a controller + TT

* converts to Foundation for greater consistency across the site
(Bug 5265) Split settings in /communities/list into their own columns
(Bug 5265) Convert /community/create to Foundation + TT

* now under /communities/new

* the creation process should be the same functionally, different
  visually (also differs in backend: using controller + view)

* adds $r->HTTP_SERVICE_UNAVAILABLE to DW::Request::Apache2, to emulate
  existing sysban behavior in non-BML contexts

* adds jquery.checkusername.js for general use when creating / renaming

* adds jquery.validation.js for foundation pages. Currently
  experimental. Adds error message display and handles ARIA flags

* adds htdocs/js/page folder for per-page JS. This should be fairly
  minimal, mostly initializing. Reusable modules should go into
  htdocs/js

* adds .journaltype-textbox / .$journaltype-textbox (e.g., div
  class="journaltype-textbox community-textbox") classes, to be used
  whenever we want the userhead in a textbox
(Bug 5265) Fix links to community/manage to community/create

* community/manage => communities/list

* community/create => communities/new

Redirect is in place, but no sense having an extra step.
(Bug 5265) Use DW::FormErrors in the Community controller

This also acts as an example of how to use the DW::FormErrors object
in controllers. Note that it's really all in the controller -- the
display of the errors is handled by the site skin, instead of having to
be inserted per-page