This page hosts the detailed specification for the ​Blueprint for the CSS Cleanup & Fixes.

The main sahana.css needs cleaning up & updating.

Is it better to try & consolidate all css files into a single stylesheet?

• GOOD: Browsers default to only downloading 2 files at a time, so many files is very slow on high latency links
• BAD: Harder for maintenance during development
• Solution?: Provide a script to Productionise the environment (Use compressed JS files & combine all CSS into 1 big one)

There are several components which aren't currently relevant & so should be removed:

• /static/styles/sahana_old.css

There was a recent change to S2 CSS which hasn't yet been ported here:

I've been working on rebranding Sahana for a deployment and in doing so have been working on the default template. A question popped up that I wanted to ask the dev team:

Why has the layout been chosen such that the Footer is contained in the Wrapper as below?

  |---- Neutralizing Styles
  |---- Basic Page Formatting Styles
  +---- Container
     |---- Header
     +---- Wrapper
        |---- Menu Wrapper ( Module Menu, Main Menu, Login Form, OpenId Login, Breadcrumbs )
        |---- Content ( Home, Result, Module specific styles )
        |---- Footer  
  |---- Form Layout Styles
  |---- Popup Menu Styles
  |---- Message Display Styles


It would make more sense to me that it should be laid out like this:

  |---- Neutralizing Styles
  |---- Basic Page Formatting Styles
  +---- Container
     |---- Header
     +---- Wrapper
        |---- Menu Wrapper ( Module Menu, Main Menu, Login Form, OpenId Login, Breadcrumbs )
        |---- Content ( Home, Result, Module specific styles )
     |---- Footer  
  |---- Form Layout Styles
  |---- Popup Menu Styles
  |---- Message Display Styles

This revised layout would open up the footer to a lot more layout possibilities as well as follow a better design approach whereas a footer is not really part of a content box.

Greg

---

BluePrints