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

Update to current

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.

Q: Should we migrate to BlueTrip?
A: Probably not as their value isn't proven.

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

CSS can be previewed in different browsers, however no interaction is possible:

Original Sahana CSS documented here: DeveloperGuidelinesCSS

Relevant Bugs:

Maximal usability ideas:

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.

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

Enhance these with dropdown menus, like in T3:

Alternative layouts

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

Q: How to {{include}} content into multiple areas? (How is it done with the JPolite app?)

Right-to-Left theme

We already have a simple:

body {
    direction: rtl;

This is currently set using the Theme.

We could look at setting this based on a lookup of the current locale.

Print View

Provide a view which allows for better Printing

  • CSS sufficient? (media=print)

Browsers don't print pages in identical ways...if this is key, need to use PDF.

Like for format=ocr.

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


Note: See TracWiki for help on using the wiki.