libreccm-legacy/ccm-sci-bundle/web/themes/mandalay
jensp c1e64375dc LastModified now uses the correct auditing information (Ticket #1934).
git-svn-id: https://svn.libreccm.org/ccm/trunk@2578 8810af33-2d31-482b-a856-94f89814c4df
2014-03-21 10:12:25 +00:00
..
css Some ajustments for the admin.css. 2014-02-11 11:00:44 +00:00
fallback Synced Mandalay-Theme in ccm-sci-bundle with Mandalay Trunk. Further development of Mandalay will be done directly here. 2014-02-05 09:12:13 +00:00
fonts Update des Mandalay-Themes 2013-11-07 12:19:02 +00:00
images Aktualisierung von Mandalay auf die aktuelle Version 2013-11-25 07:39:20 +00:00
includes LastModified now uses the correct auditing information (Ticket #1934). 2014-03-21 10:12:25 +00:00
lang New content type for historic dates. 2014-03-19 15:43:38 +00:00
layout New content type for historic dates. 2014-03-19 15:43:38 +00:00
settings New content type for historic dates. 2014-03-19 15:43:38 +00:00
user Java-Script code for Piwik-Tracking updated for Piwik 2.1 2014-03-17 16:43:05 +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 Backported some changes and improvments from the Mandalay-YAML fork back the orginal mandalay. Also updated the Mandaly-YAML branch. 2014-02-19 14:17:06 +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