Revision history [back]
It is possible to add custom footer, css, js, and the HTML <head> element via the settings user interface and the possibility to add top portion of the site will be included shortly (there will be other useful changes as well).
So, the easiest method to modify appearance of the site is through the "settings" interface and the admin account.
A caveat is that some names of the element selectors might still change so the customization may require some maintenance upon upgrades.
The second method is to edit the html template files directly.
If you choose the second method, keep using the "default" skin and edit its html template files, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. askbot.org is not too different from the default application, but there are substantial modifications in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.
The first template to look at is askbot/skins/default/templates/base.html, it is quite simple and you can substantially change the appearance by modifying that template in the combination with adding some custom css.
Another helpful bit when customizing the templates is installing askbot application in the "developer" mode:
python setup.py develop
That way the askbot app will stay in the local directory and the files can be accessed more easily.
It is possible to add custom footer, css, js, and the HTML <head> element via the settings user interface and the possibility to add top portion of the site will be included shortly (there will be other useful changes as well).
So, the easiest method to modify appearance of the site is through the "settings" interface and the admin account.interface.
A caveat is that some names of the element selectors might still change so the customization may require some maintenance upon upgrades.
The second method is to edit the html template files directly.
If you choose the second method, keep using the "default" skin and edit its html template files, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. askbot.org is not too different from the default application, but there are substantial modifications in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.
The first template to look at is askbot/skins/default/templates/base.html, it is quite simple and you can substantially change the appearance by modifying that template in the combination with adding some custom css.
Another helpful bit when customizing the templates is installing askbot application in the "developer" mode:
python setup.py develop
That way the askbot app will stay in the local directory and the files can be accessed more easily.
It is possible to add custom footer, css, js, and the HTML <head> element via the settings user interface and the possibility to add top portion of the site will be included shortly (there will be other useful changes as well).
So, the easiest method to modify appearance of the site is through the "settings" interface.
A caveat is that some names of the element selectors might still change so the customization may require some maintenance upon upgrades.interface.
The second method is to edit the html template files directly.
If you choose the second method, keep using the "default" skin and edit its html template files, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. askbot.org is not too different from the default application, but there are substantial modifications in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.
The first template to look at is askbot/skins/default/templates/base.html, it is quite simple and you can substantially change the appearance by modifying that template in the combination with adding some custom css.
Another helpful bit when customizing the templates is installing askbot application in the "developer" mode:
python setup.py develop
That way the askbot app will stay in the local directory and the files can be accessed more easily.
It is possible to add custom footer, css, js, and the HTML <head> element via the settings user interface and the possibility to add top portion of the site will be included shortly (there will be other useful changes as well).
So, the easiest method to modify appearance of the site is through the "settings" interface.
The second method is to edit the html template files directly.
If you choose the second method, keep using the "default" skin and edit its html template files, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. askbot.org is not too different from the default application, but there are substantial modifications in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.
The first template to look at is askbot/skins/default/templates/base.html, it is quite simple and you can substantially change the appearance by modifying that template in the combination with adding some custom css.
Another helpful bit when customizing the templates is installing askbot application in the "developer" mode:
python setup.py develop
That way the askbot app will stay in the local directory and the files can be accessed more easily.
It is possible to add custom footer, css, js, and the HTML <head> element via the settings user interface and the possibility to add top portion of the site will be included shortly (there will be other useful changes as well).
So, the easiest method to modify appearance of the site is through the "settings" interface.
The second method is to edit the html template files directly.
If you choose the second method, keep using the "default" skin and edit its html template files, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. askbot.org is not too different from the default application, but there are substantial modifications in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.
Another helpful bit when customizing the templates is installing askbot application in the "developer" mode:
python setup.py develop
That way the askbot app will stay in the local directory and the files can be accessed more easily.
It is possible All templates are now rewritten in jinja2, but it's still too early to add custom footer, css, js, and HTML say that they are frozen. In fact one thing that's going to be done soon - all links to external <head>.jselement via the settings user interface and the possibility to add top portion of the site files will be included shortly (there will moved to the bottom. Then certain pieces need to be other useful changes as well).
So, modularized so that it would be simple to change the easiest method to modify appearance of the site is through the "settings" interface. layout.
The second method best way do deal with customizing skin on the level of the template files is to edit the html template files directly.
If you choose the second method, keep using the your skin "default" skin and edit its html template files, it directly, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. askbot.org It is not too different from the default application, default, but there are substantial modifications differences in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.
Another helpful bit when customizing the templates is installing askbot application in the "developer" mode:
python setup.py develop
That way the askbot app will stay in the local directory and the files can be accessed more easily.
All templates are now rewritten in jinja2, but it's still too early to say that they are frozen. In fact one thing that's going to be done soon - all links to external .js files will be moved to the bottom. Then certain pieces need to be modularized so that it would be simple to change the layout.
The best way do deal with customizing skin on the level of the template files is to keep your skin "default" and edit it directly, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. It is not too different from the default, but there are substantial differences in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.
On the other hand, it's possible to do quite a bit of customization by changing only file /askbot/skins/default/media/style/style.css. Still git system will be very helpful here as well.
All templates are now rewritten in jinja2, but it's still too early to say that they are frozen. In fact one thing that's going to be done soon - all links to external .js files will be moved to the bottom. Then certain pieces need to be modularized so that it would be simple to change the layout.
The best way do deal with customizing skin is to keep your skin "default" and edit it directly, while maintaining a local git repository (which does not have to be publicly accessible). That's how I maintain skin for askbot.org. It is not too different from the default, but there are substantial differences in some places. When default skin changes - you'll just need to merge the modification into your local skin. This is quite simple and manageable in git if you keep up with the updates.places.
On the other hand, it's possible to do quite a bit of customization by changing only file /askbot/skins/default/media/style/style.css. Still git system will be very helpful here as well..
Merging with git is quite simple and manageable if you keep up with the updates.