Westminster New

[Danielle]

That's exactly what I'm getting at :) The average person wouldn't really think like that, so they'd be confused when they changed the footer in the admin. Having the footer area in the admin leads you to believe no coding is required to edit the footer. I didn't mean you should put in specific info to cover every possibility, just that it might be good to indicate that other coding may still be required after editing the footer in the admin. In any case, it was just a suggestion :) Thanks again for your quick help with this, I really appreciate it!

Even though there is an admin interface for the footer menu, it effects the output of the code so yes, it is a "code" change.

Thanks,

Anne

[DivaVocals]

That's exactly what I'm getting at :) The average person wouldn't really think like that, so they'd be confused when they changed the footer in the admin. Having the footer area in the admin leads you to believe no coding is required to edit the footer. I didn't mean you should put in specific info to cover every possibility, just that it might be good to indicate that other coding may still be required after editing the footer in the admin. In any case, it was just a suggestion :) Thanks again for your quick help with this, I really appreciate it!

I agree with Anne.. It isn't necessary for this to be in the readme.. It's a given that if you move things from one column to another that a CSS change will be needed.. It' pretty much a given that most ANYTHING you do to move things from their original positions onany part of the template might require a similar change..

I don't think this needs to be in the readme. It would be impossible to add instructions for all of the various template modifications people can make. It is a given that if you are going to modify the template you might need to make changes to the css.