Initial cut at restoring the ability to publish news articles, with admin approval etc.
auto-approve news posting by administrators and show missing about pending approval
add migration to add status column to news_item
fix for WEBSITE-179 "Replace delete user with disable user"
content updates
remove printlns, change to use content table since news_item extends content
Make the individual plugin pages live.
Fix 'flash of content' problem on download page.

We use Modernizr to attach CSS classes to the <html> element for graceful
degradation of our pages. Unfortunately, Modernizr was being loaded at the
end of the page (because of the default disposition of 'defer' in Resources)
and that was resulting in the classes being added *after* page load. So you
saw the non-JS content just before Modernizr was loaded.

Very simple fix: Modernizr is now disposition 'head', so the CSS classes are
added at the beginning of page load.
Update the downloads page.

Implements WEBSITE-174. The page has been made more user-friendly by grouping
the old releases by major version. The page also works with JavaScript disabled.

For the styling, I created a dedicated less file for the page since no other
page needs it. Trying to move away from one great monolithic CSS file.
Upgrade to Resources 1.2.RC2.

RC2 throws an exception if any modules in the dependency tree are missing, so
I had to resurrect the YUI plugin. That does mean we need to use it though.
Resurrect legacy plugin home page URL.
Change 'def scaffold' to 'static scaffold'.
Fix typo in case clause.
Make plugin tags link to 'list by tag'.

The plugin pages display the tags for that plugin. These are now links to the
page that displays all plugins with the corresponding tag.
Summarise plugin description in list plugins view.

Some plugin descriptions are very long and these take up way too much space
in the list plugins page. All descriptions are now curtailed to 500 characters
max.
Add 'Admin' link to menu bar for administrators.
Fix styling of edit user page.
Enable existing users during DB migration.
Fix incorrect capitalisation in name of fancybox CSS resource.
Add LESS reloading via client-side less.js.

Server-side reloading of LESS is difficult in Grails when the @import statement
is used, so for development mode (run-app) we use client-side less.js rather
than the CSS generated from the LESS files on the server. When it comes to
generating the WAR file, we use the lesscss library for Java to compile the
LESS files to CSS, and it's the CSS files that are then referenced directly by
the pages.

This is a pretty ugly solution for a variety of reasons. To start with, we
shouldn't have to use client-side LESS, since Grails already has a reloading
mechanism that the Resources plugin hooks into. Unfortunately, there is no way
to know which LESS files need recompiling when one of them changes, because
you have to compile the top-level LESS file which ultimately imports the one
that you've changed.

On top of that, the lesscss Java library is pretty slow at compilation. During
WAR creation I have seen 6.5s and 19s. That's just not viable for automatic
reloading while you're developing. This is probably related to the library
using less.js on Rhino, but your guess is as good as mine.

Finally, I had to reorganise the LESS files so that they were no longer in
sub-directories. This was to work around an issue that client-side less.js
behaves differently with relative URLs and sub-directories compared to server-
side LESS. This GitHub pull request explains the general problem:

    https://github.com/cloudhead/less.js/pull/331

A faster LESS compiler for Java applications would go a long way to resolving
these problems. Any volunteers? :)