.LRN Zen Project

1. Accessible and semantic layout/design (first priority)
2. Layout for screen reader readability
3. Consistent  CSS for all packages with inheritance where possible
4. Package specific CSS only where absolutely necessary
5. Remove as many images as possible
6. Totally simplified CSS scheme
7. Consistent deprecation
8. Support for 4 font sizes without UI breakup
9. File path re-factoring so designers can easily skin a local installation and upload zip file with local styles for sharing accross installations
10. A theme page that includes as many existing adp chunks and form templates as possible.
11. Theme manager that allows a designer to upload a css file and immediately test it against the theme page.
12. One style for screen, one for print, and one for mobile

 Discussion

     0. Why not OpenACS Zen? I think this needs to apply across the toolkit for any package, not just .LRN ones, or there will forever be problems as new applications come out for OpenACS, and are later adopted for .LRN. DaveB, we are going to start with .LRN b/c it contains a limited number of packages and also because there is an accessibility push in the project. A big portion of this will also be defining best practices. CarlB

    1. I agree with Carl.  I have been working through some of this on our own generic OpenACS installs here but would love to co-ordinate with others.  Robert.

    2. I also will help out. I have several tools available and will look at what is redundant and post soon. Jon Griffin

   3. Please consider expanding the scope of the guidelines to include OpenACS and similar efforts underway at Interface / CSS Coding Guidelines. Accessibility etc. is important for the entire toolkit and long overdue. -Torben