Implementing the new wgo theme for Plone.

[Carsten Senger <senger rehfisch de>]

Hi all,

here is the proposal for theming wgo. I've seen the work that Vinicius did
the last weeks. Looks pretty nice. I've listed some potentially missing
webdesign elements under tasks -> webdesign. To get some volonteers there
someone with a better overview over the design status and the needs of the
content team has to rework that part.

I'm overwhelmed by work atm, but I will set up the infrastructure for the
deliverance part, clean up the old wgo.theme package and start to work on
the theme implementation.

Help with it is very welcome. You don't have to know anything about Plone
to work on it. You need to know svn (or git?) and an understanding of html
and css. Deliverance uses CSS selectors (or XPath selectors, they can be
copied out of firebug) and is written into an xml file, but with very few
and simple commands.

..Carsten


== Theming ==

wgo will be themed with
[[http://deliverance.openplans.org/index.html|deliverance]].

 ''Deliverance is a tool to theme HTML, applying a consistent style to
applications and static files regardless of how they are implemented, and
separating site-wide styling from application-level templating.''

It works like a proxy that inserts parts of the ''content'' into an
''template'' with a simple rules language. It makes the theming of plone
faster and allows to use the templates developed by Vinicius and Andreas
including their semantics. It also reduces the size of the delivered pages.

Deliverance can run in it's own process as a proxy or as part of a
[[http://de.wikipedia.org/wiki/Web_Server_Gateway_Interface|WSGI]]
pipeline.

The rules are written in a xml format. The selection of elements is done
with CSS or XPath selectors. A simple rule that inserts the main content
from a plone site into vinicius' and Andreas' gnome.org-templates is:

{{{
<replace content="children:#content' theme='children:#content' />
}}}

The children of the content element with the {{{id}}} "content" replace the
childeren of the theme element with the {{{id}}} "content" (coincidental
the same {{{id}}}).

The current theme template looks like:

{{{
 ...
 <div id="container" class="container_12">
    <div id="content" class="grid_9">
       <p>
       </p>
    </div>
 ...
}}}

the plone content like:

{{{

  <div id="content">
     <h1 class="documentFirstHeading">
     ...
  </div>
}}}

the result will be

{{{
 ...
 <div id="container" class="container_12">
    <div id="content" class="grid_9">

       <h1 class="documentFirstHeading">
       ...

    </div>
 ...
}}}


=== Tasks ===

==== Webdesign ====

* polish the theme templates
* identify missing parts. These could be e.g.
  * Forms: contact, advanced search, search results (if so based on some
  kind of plone markup)
  * press/media section (listing, press releases, supporting media?)
  * sitemap (based on the plone markup)
  * call to action boxes (like
[GnomeWeb/TwoPointTwentyseven/Content/Products#head-86ecf265ff44b46d85222a58b99cbba063f7d586])
  * preformated/code boxes
  * Friends of GNOME (decide if/how to integrate it and restyle it)

* develop the css for the missing parts
* specify the elements that should be used by the editors (blockquotes,
inline quotes, headings, intro text, pre formated, etc. and write styles
for them.
* create additional images
* continually test design and adapt some of the styles to the markup
that plone produces (e.g. navigation)
* help writing the rules

====  Programmers ====

* Add deliverance to the buildout
* create deliverance rules for the design
* adjust components that can't be themed with deliverance alone
(afaics done in the current wgo.theme package)
* write documentation for setting up a sandbox
and deploying on socket.gnome.org

==== Sysadmins ====

* Update socket