wiki:BluePrint/CSS

Version 37 (modified by Fran Boon, 13 years ago) ( diff )

ToDos

BluePrint for CSS

We have moved to a full page design to allow maximal screen real estate to be available for list views & data entry. Ours is based on:

The logo font is Brush Script.

Main outstanding task on this is to have the Modules menu show which module we're currently in.

  • The Auth menu already does this.

The Modules menu could be moved to a single dropdown - located below the Login box.

The Auth menu should be migrated to using the same style as the Modules/Options menus?

The CSS could still do with some cleaning up to remove unused styles.

We should include alternate layouts which different views can inherit from (common areas included into these to be DRY):

CSS could be parsed as a template (included as a view) & thus have commonly-changed items (Logo/Colours) stored in the database (s3_theme).

  • Would the minify script cope with this? (Could amend to have the editable file use keywords which are replaced by the braced variables in both debug/min)

Maximal usability ideas:

Replace the current menus with Breadcrumb-style Chevrons, e.g.:

Enhance these with dropdown menus, like in T3:

Relevant Bugs:

CSS can be previewed in different Internet Explorer version, however no interaction is possible:

Original Sahana CSS documented here: DeveloperGuidelinesCSS

Right-to-Left theme

Ideally this should be as simple as:

body {
    direction: rtl;
}

Print View

Provide a view which allows for better Printing

  • CSS sufficient? (media=print)

Mobile View

Provide a cut-down version for use on low-screensize, low-bandwidth devices, such as Mobiles

Use the RESTlike CRUD controller's ?format=plain

Icons in Menus?


BluePrints

Note: See TracWiki for help on using the wiki.