libreccm-legacy/ccm-sci-bundle/web/themes/mandalay
jensp 697835822b - Fix für SciDepartmentProjectsTabO
- Integriertes Mandalay-Theme auf aktuellen Stand gebracht


git-svn-id: https://svn.libreccm.org/ccm/trunk@1675 8810af33-2d31-482b-a856-94f89814c4df
2012-05-21 14:05:39 +00:00
..
css Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
images Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
includes Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
lang Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
layout Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
settings Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
user - Fix für SciDepartmentProjectsTabO 2012-05-21 14:05:39 +00:00
_skeleton_.xsl Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
license Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
liesmich Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
readme Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00
start.xsl Anpassung ccm-sci-bundle mit Mandalay theme als default, aplaws generic deaktiviert. 2012-05-18 00:14:07 +00:00

readme

Mandalay
========

This will be a complete new theme for RedHatCMS /
Byline / Aplaws+ build up from scratch.

Design goals are to build a modular box-layout-based theme
integrating all functions from the cms which will be styled
by changing css files and xml-based settings.


Some hints for this theme:
--------------------------

* Each content type have exactly one xsl file in the types directory, which will do all the processing
  * This file will include templates for all view (detailed, listed, ...)
* shared functions like Processing of image attachments will be located in seperate files in the include directory
* templates will be defined with name and match clause, where aprop
* css file go in the css sub folder structur
  * for each media type, there will be a folder on first level
    * for each content type there will be al folder on second level
    * also, there will be a folder for global css settings in second level
    * in these folder on second level there are 4 css files: basic.css, enhanced.css, ie-hacks.css and admin.css
      * basic.css uses css styles, which will work in all css capable browsers
      * enhanced.css uses css styles, which will work with modern browsers (Firefox, Konqueror,...)
      * ie-hacks.css uses special css styles, which will correct the flaws of MSIE
      * admin.css uses css styles, which will be needed by admin ui
* setting for personalization are located in the settings directory
* localized static text are read from the xml-files in the lang folder