Child pages
  • Front-end Discussion -- Design, Architecture, CSS, Web standards & more
Skip to end of metadata
Go to start of metadata


WIKI Sections: HOME - MEETINGS - PROFESSIONAL DEV/NETWORKING - FRONT END DISCUSSION - BACK END DISCUSSION - MULTIMEDIA DISCUSSION - CONTENT DEVELOPMENT - PROJECT PLANNING & TO DOs - MEMBER'S PAGES

An area to post design, layout ideas, architecture, etc.

Design & Architecture

Identity

NCAR and its Labs and Divisions are a family of related content and tools. A visitor to an NCAR website should be able to tell that we "go together" by our visual design, structure and organization. There is a continuum of design possibilities to acheive this, from strictly templating every aspect of all these websites so that they look almost identical, to adopting only certain key common elements (such as a common main navigation) while allowing lab websites to otherwise have different layouts.

Questions to consider -

  • How much commonality does it take to create a visual "family"?
  • Which approach do you prefer? Very templated, such as the nasa.gov websites? Or, very loose identity systems such as in most university system websites (I'll find an example)?
  • Pros/Cons of each?
  • What would it take in web technologies if we did want to adhere to the same layout/design templates?
  • AND, what should be the design similarities/differences between the NCAR websites, and UCAR's?

CSS & Web Standards

Kris gave a presentation at the March 16 meeting on the relationship between Web Standards and CSS layout techniques.  The presentation is available on the CSS and Web Standards page

Javascript, AJAX Methods & Client-side Interactive Scripting 

Text

  • No labels