libreccm-legacy/ccm-sci-bundle/web/themes/mandalay
jensp db34c28bde Backport Mandalay r420
git-svn-id: https://svn.libreccm.org/ccm/trunk@2346 8810af33-2d31-482b-a856-94f89814c4df
2013-10-10 13:49:00 +00:00
..
css Neueste Version von Mandalay mit weiteren Verbesserungen im ContentCenter 2013-10-10 06:51:36 +00:00
images Neue Version von Mandalay 2013-08-05 05:49:30 +00:00
includes Neueste Version von Mandalay mit weiteren Verbesserungen im ContentCenter 2013-10-10 08:29:13 +00:00
lang Neueste Version von Mandalay mit weiteren Verbesserungen im ContentCenter 2013-10-10 06:51:36 +00:00
layout Neueste Version von Mandalay mit weiteren Verbesserungen im ContentCenter 2013-08-16 18:55:13 +00:00
settings Verschiedene Verbesserungen beim Anlegen neuer ContentSections und dem Zusammenspiel zwischen Sections und Kategorien. 2013-09-21 12:44:25 +00:00
user Backport Mandalay r420 2013-10-10 13:49:00 +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 Neue Version von Mandalay 2013-08-05 05:49:30 +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