Here's what I always do.

+ Do a rebuild, just in case.
+ Download the relevant HTML-files locally to my PC.
+ Edit the CSS-file(s) in place.
+ Fine-tune until I like the results.
+ Upload the changed CSS-file(s).
+ Do a rebuild.
+ Voila!

I have extracted all the CSS-stuff from the index files and put them in a separate file called "Blogger.css" so that I have all the style-dependant stuff localized.

Is this what you were asking?

By the way, I use TopStyle Pro which is a fantastic CSS-editor that allows you to make changes on the fly and see how that effects your site's appearance.

Hope this helps.

Thanks everyone for your comments.

I really would love to be able to create and test this via Moveable Type within the system, since I have content already there. I just want to be able to see the same content in more than one template without disturbing my present setup (for me and for the viewer).

Ben (or anybody else), is there an "official" way of doing this (I've perused the documentation but have come up empty-handed) --official meaning something I can use within the system.

Brenmae's suggestion *is* within the MT system, and would enable you to view your current content while leaving your current setup in place.

Just copy what is already in your current Main Index template into a new index template, which you can create on your current blog's List Templates screen. Give it another name, like test.html.

Then modify the new template however you want.

When you're done, rebuild your index files and then view the test.html file with your browser, and you'll see your current content.

Granted, this is only going to be helpful for your main & master archive indexes, and your stylesheet, not your archives, or comments, etc., (because unfortunately, you can only have one template for each of those). But you'll at least get an idea if the change is something you want to go with "across the board" before changing those other files.

I honestly don't know of a more "official" way to do what you want, *unless* you want to export your entries from your current blog, and import them into a second, "test" blog where you can make all the template changes you want without fear of mucking up your primary blog layout.

You're welcome!

I'm totally fascinated with skinning sites too, unfortunately, I don't have PHP with my host! boohooo!

I did this once in the past, but I'm not going to make any promises...

I changed the extension of the files in the blog config from html to something else.  Assuming you keep backups of the current templates (which I actually copied into a blog), everything's ok.

You'll have to change the CSS file you used, though, since that's loaded for every page load. You can work with new stuff as much as you want, and your old stuff should remain untouched.  e.g. the html files won't change, but all the new stuff will be in the htm or h or whatever files.

Keep in mind, though, that you won't get back to your current system until you change the extension back AND rebuild.  Then, of course, go delete the files you no longer need.

Evans

I want to redesign my site but I'd like a good strategy for designing a new template and testing it without disrupting my present site.

I'd like to be able to see my present content in the new template and play with the design.

Any tips on the best way to do this without harming what I have now?

maybe you could do this by creating a new "Main Index" template but naming the file other than "index.html" or saving it to temporary directory. you could also create a new stylesheet. i think this can also be done to create archives.

Ever since I added the feature of skins (from http://domesticat.net s tutorial), its been easy to test out new designs.  I upload my propsective design as a new header and footer (header2.php and footer2.php) and then type in http://www.love-productions.com/hopelessromantics/?newskin=2 - this skins my site automatically with the new design.

Of course, I did a lot of beforehand work to make my site skinnable, but if you are planning on changing designs frequently, it might be worth looking into

kristine

Girlie, thanks! Your extra information helped illuminate Brenmae's suggestion. Your final statement about exporting and then importing into a newly setup blog is also a possibility.

Kadyellebee, I bookmarked your skin link as I would love to get into PHP. Thanks.

Oh, Girlie, I'd be sad without php on my site!  Its such a useful tool!  So if you change servers any time soon, make sure you have that option in the future!!!



kristine

Another thing you can do is create a /test directory and then change your paths in blog config to output your site to that directory, and then switch it back when you're ready.

Brenna