From 10f4954b4530a67d88c66ba8e397ee81487f4752 Mon Sep 17 00:00:00 2001 From: Max Kanat-Alexander Date: Tue, 20 Jul 2010 20:34:41 -0700 Subject: Bug 428313: Properly expire the browser's CSS and JS cache when there are new versions of those files. This also eliminates single-file skins and should also allow Extensions to have skins. r=glob, a=mkanat --- skins/README | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 skins/README (limited to 'skins') diff --git a/skins/README b/skins/README new file mode 100644 index 000000000..111c00f03 --- /dev/null +++ b/skins/README @@ -0,0 +1,20 @@ +There are three directories here, standard/, custom/, and contrib/. + +standard/ holds the standard stylesheets. These are used no matter +what skin the user selects. If the user selects the "Classic" skin, +then *only* the standard/ stylesheets are used. + +contrib/ holds "skins" that the user can select in their preferences. +skins are in directories, and they contain files with the same names +as the files in skins/standard/. Simply putting a new directory +into the contrib/ directory adds a new skin as an option in users' +preferences. + +custom/ allows you to locally override the standard/ and contrib/ CSS. +If you put files into the custom/ directory with the same names as the CSS +files in skins/standard/, you can override the standard/ and contrib/ +CSS. For example, if you want to override some CSS in +skins/standard/global.css, then you should create a file called "global.css" +in custom/ and put some CSS in it. The CSS you put into files in custom/ will +be used *in addition* to the CSS in skins/standard/ or the CSS in +skins/contrib/. It will apply to every skin. -- cgit v1.2.3-24-g4f1b