Closed (fixed)
Project:
BlueTrip
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2009 at 05:44 UTC
Updated:
12 Mar 2009 at 14:10 UTC
Jump to comment: Most recent
Comments
Comment #1
vm commentedbest practice would be to duplicate a theme.
name the folder
the info.file and .info file contents to reflect name of your theme
customise until your hearts content.
This will keep your customizations safe when this theme updates/upgrades. You can then compare the changes in the new release with the "old" backedup release so that you know what you will need to change in your own customised theme.
Comment #2
Anonymous (not verified) commentedWhen first customizing a theme, it can be a bit scary to change the code, but you shouldn't. Espeially if your base theme is online, whatever you do, if it goes wrong, you can still download the original and compare.
So don't be afraid to experiment, customize the code, change it, and delete what you don't need. It is totally fine, and even recommended to edit the page template when you create your own theme.
Then, if you need to add css, just do it in a very organized way. Don't mix your style and the default one you need, and comment everything you do. Either add your css in a new separate file, or at the end of the existing css files.
Whatever you do, just try to be organized and document your own work. that's the best way to have a clean code.
Comment #3
rovoThanks for all the great suggestions. I'll go ahead and give that a try.
Comment #4
vm commented