The skin command is an advanced command used primarily in the site.skins section of your site to edit and manage your skins. If the user is not an admin, this command will do nothing.
To use this command, you must first define a mode (by setting either a mode parameter or simply putting your mode in #1). That mode can be copy, rename, update or delete. And each works about like you would expect. Here's a few more specifics:
For copy, you set a to and a from skin name. The from skin must exist, and the to skin must not exist or this mode will throw a warning. Assuming those conditions are met, it will create the specfied new skins directory, copy over all the available skin files, and rename the two code.skin pages (the html and css file). Any existing style.css page will be copied over as--and may need updating if it uses absolute urls.
This mode similarly require a to and a from parameter. Rather than making a copy of a skin, it renames the folder and code.skin pages.
This mode requires a skin parameter. If the local skin is found, all files and the folder will be deleted.
This mode updates the style.css file. Basically, code.skin.skinname.css is read, any skinvars in the file are evaluated (colors, image paths, etc), and a new finished style.css page is created.
Using SkinsThe idea was to make it possible to fully edit your skins dynamically right through your browser, without jeoparidizing your existing site.
To make a minor change, just go to the site.skins page, select the skin you modify (from your installed skins) and then select the option you want to modify your setting, css, or html.
To work on more major changes, consider using this basic workflow:
1) Go to site.skins and select your existing skin.
2) Copy it to a new skin name, let's say "newskin".
3) Use the site skin tools to edit the skin files.
4) Use the display tool to preview those changes.
5) When its ready, use site.auth.skins to switch skins.
For more advanced testing of a skin, you can set a directory (like "test") to use the new skin in site.auth.skins, and then create any test pages you want to explore the site layout and design.
This approach allows you to develop a new skin without disrupting your current users through the construction process.
For more information on skins, see the tutorial on the corresponding concepts page.
Server CachingNote: on some servers, the style.css is dynamically cached, making it impossible to see your changes automatically. One workaround is to edit your code.skin.skinname.html page and add a version number to the style.css link. For example, compare the two lines below:
<link rel="stylesheet" type="text/css" media="screen" href="https://www.boltwire.com/skins/piano/style.css />
<link rel="stylesheet" type="text/css" media="screen" href="https://www.boltwire.com/skins/piano/style.css?ver=1.7" />
By simply updating the html file each time you edit your css file to a new version number, you can "trick" your server into serving up a fresh copy of your style.