Color overload

CMS Ametys offers a range of functions based on a color palette. All these palettes can be overloaded by project, and some by graphic charter.

  1. Format XML of a color palette:
  2. Color palette overload
  3. Different uses for pallets
    1. Labels for CMS
    2. Project category
    3. Site configuration
    4. Link directory
    5. Project labels
    6. Task module section

 

Format XML of a color palette:

All color palettes are available in the following format XML :     

<colors default="4" css-class="sitescolors">
    <color id="1">
        <main>#FF66FF</main>
        <text>#FFFFFF</text>
    </color>
    <color id="2">
        <main>#CC33CC</main>
        <text>#FFFFFF</text>
    </color>
  ...
    <color id="28">
        <main>#000000</main>
        <text>#FFFFFF</text>
    </color>
</colors>
  • Beacon colors: The root tag
    • Attribute default: The default color that will be proposed in the palette.
    • Attribute css-class : The CSS class used to render the color in the palette tool. It is therefore used with a xsl file that generates a CSS with the list of palette colors. (Often to be ignored on the graphics integration side).
    • Beacon color: You need to add a color tag for each color you want in the palette.
      • Attribute id: This is the color's unique identifier. It's what's stored most of the time, and provides the information associated with the color. 
      • main tag : The hexadecimal code of the main color
      • text tag : Hexadecimal code for text color

Color palette overload

By default, Ametys offers a palette of colors. But they're all overloadable.

  • Overload per project
    • Find the name of the XML file associated with the palette you wish to override(filename.xml)
    • Redefine this file XML in {AmetysHome}/WEB-INF/param/fileName.xml
  • Overloading by graphic chart (not all palettes can be overloaded by graphic chart)
    • Find the name of the XML file associated with the palette you wish to override(filename.xml)
    • Redefine this file XML in {skin }/conf/file-name .xml

Different uses for pallets

For tags, it is possible to retrieve color from tags via a helper XSL tagColor.

Labels for CMS

  • Name of file to override: tag-colors.xml
  • Overload on skin side: no

Project category

  • Name of file to override: project-category-colors.xml
  • Overload on skin side: no

Site configuration

  • Name of file to be overwritten: site-colors.xml
  • Overload on skin side: no

Link directory

  • Name of file to override: linkdirectory-colors.xml
  • Overload on skin side: yes

Project labels

  • Name of file to override: project-tags-colors.xml
  • Overload on skin side: yes

Task module section

  • Name of file to override: tasks-list-colors.xml
  • Overload on skin side: yes             
Back to top

Setup and integration manual