A couple of years ago I started playing with OJS look&feel.
Those were hard times, full of dirty hacks and night postings to Alec.
Time goes by and just a few months ago I started our migration to OJS 2.2. As far as this OJS version included a brand new theme engine, I wanted to develop a flexible theme that hopefully could be contributed to OJS (too much good received, and to little given).
I started working on it, but (and sorry in advance if I'm missing something) I found the general layout of OJS a little overwhelmed and far from been ideal...
I didn't reflect much about this (I'm writing while I'm thinking) but let me illustrate with a couple of examples:
A good practice in CSS design is making 2-1-3 layouts to let your site be "SEO-friendly". If content comes first, google (et. al.) will be happy and if google is happy, your magazine's Editor will be happy and if your Editor is happy... you will be happy. As far as I see OJS 2.2 layout is today something as:
| | |-leftSidebar (1)
| | |-rightSidebar (3)
| |-main (2)
| | |-navbar
| | |-breadcrumb
| | |-content
Which drives me to the second point: Where is the footer in this tree?
OJS includes a "#footer", but is for it's own proposes (show debug info) and any content included in footer is added at the end of the "#content" layer.
As I said, may be I'm missing something, but if not, those are changes that could be easily archived and will make the life of CSS designers and OJS administrator easier.
Otherwise, complex or flexible themes will need a little tuning in the template layer and more CSS than usual.
I just hope it makes sense for anybody,
PD: Let me know if you prefer this post in the bugtrack as a "feature request" for OJS 2.4.