A brief introduction to the files that control the the appearance of the output.
Template authors vary as to how much information they provide towards editing the component files. All, or nearly all, templates will provide these basic files and you can do a lot of customisation without touching any others.
It's best to change only one value at a time, test it thoroughly and then move on to the next. Remember that almost all the values in these files are global to the template, so my advice would have to be to check everything, to ensure that you're not adversely affecting something you don't intend to.
style.ini
This is read by the initialisation file parser to extract the baseline colour values for a template. The colours are defined as three character hexadecimal codes.
- _existing_ is the colour for internal links that are referenced in the index. In other words, they lead to wiki pages that already exist. By default, the same value is used for inline links and for any table listings.
design.css
Defines the basic components of a template, such as forms, buttons, lines, etc.
- Headlines are set as percentages of the default font. Typically, H1 is set at 150% and the rest as smaller values, in 10% decrements, down to 100%. If you are never likely to use H4 and H5, these can be set at 100%, allowing you to give bigger gaps to H2 and H3.
print.css
Specifies what a printed version of the form will look like.
media.css
Controls the appearance of the Media Manager sub-system that is used to upload and assign images, etc to entries.
rtl.css
Provides special formatting for those languages (Arabic, Hebrew, etc.) that are read from right to left, rather than from left to right (English, French, German, etc.).
