This is actually pretty easy, so long as I remember that the Username is one I created. It is tied to the location of the web log in the FTP account.

The FTP host will automatically have the log-in from Windows Live Writer rooted at the wingnut blog location on the server because that is what the rules are for that Username. That is why the image folder appears to be at the root. It is the root for that account on FTP, not the root of the FTP host.

The URL is where the pictures are actually carried, relative to where the orcmid.com web site is imaged on the server. The names and folder structure within that folder will be generated by Windows Live Writer. These materials are not intended for deep linking, as you will learn if you use that URL to be nosy.

One challenge with this structure is keeping the images/ subdirectory backed-up. The structure that LiveWriter uses is ungainly and not something that is useful for me to mirror on my web-development site or attempt to preserve in VSS. Instead, I collect all of the image/ material into a single Zip file and I back that up in VSS and keep an image on my hosted-site image and the hosted-site itself. The versions I keep backed up on my local web-development machine will also be backed up on the Windows Home Server that supports my SOHO LAN.

I have no idea if the same or different structure will work with the blog engine I migrate to. How this one migrates will provide the worked case for migrating the images associated with the other nfoCentrale blogs.

[Update 2010-04-29T04:54Z OK, I didn’t catch that the width on the cell was also set. It should all be floating now, with it getting tricky when the browser page width is so narrow that the image itself is squeezed. That’s good enough for now. Update 2010-04-29T04:48Z I put the image and the text with it in a single-celled table so that the additional blog item material below would not flow up alongside the image if viewed in a wide browser window. What I need to remember when I do that is that Live Writer gives the table a fixed with (800 pixels, it seems). I don’t want that. The table should be the appropriate width for how the page is being viewed and that will be just fine. This update remedies that be taking the fixed width out of the <table> element.]