Revision history [back]
I'll give a second answer - suppose you have successfully deployed from github - how to edit skins now?
One method is to have a separate skin directory and change the skin setting in the /settings url (as in the document that you've mentioned).
This way the files that you've copied are "yours" completely, which actually brings the following problem: if any of the template tags/variables change - you'll have to replicate those changes in your custom skin. This may not be a lot of fun. Also I plan to rewrite skins in Jinja2 some time down the road for extra speed - so default skin is an area of future changes.
An alternative (but it requires use and some understanding of the git system) is that you just edit anything in askbot/skins/default tree, commit that stuff into your repository, then merge in any updates. This way it will be possible to "upgrade" your custom skin in the future.
I'll give a second answer - suppose you have successfully deployed from github - how to edit skins now?
One method is to have a separate skin directory and change the skin setting in the /settings url (as in the document that you've mentioned).
This way the files that you've copied are "yours" completely, which actually brings the following problem: if any one of those files in the template tags/variables change default skin changes in an important way - you'll have to replicate those changes in your custom skin. This may not be a lot of fun. Also I plan to rewrite skins in fun.Jinja2 some time down the road for extra speed - so default skin is an area of future changes.
An alternative (but it requires use and some understanding of the git system) is that you just edit anything in askbot/skins/default tree, commit that stuff into your repository, then merge in any updates. This way it will be possible to "upgrade" your custom skin in the future.
I'll give a second answer - suppose you have successfully deployed from github - how to edit skins now?github.
One method is to have a separate skin directory and change the skin setting in the /settings url (as in the document that you've mentioned).
This way the files that you've copied are "yours" completely, which actually brings the following problem: if one of those files in the default skin changes in an important way - you'll have to replicate those changes in your custom skin. This may not be a lot of fun.
An alternative (but it requires use and some understanding of the git system) is that you just edit anything in askbot/skins/default tree, commit that stuff into your repository, then merge in any updates. This way it will be possible to "upgrade" your custom skin in the future.