Convert Existing HTML Blog Page into XML/RSS Page

I am very new to blogging and have created a static HTML blog page on my website that matches the site "look & feel". (see link below) [login to view URL] This project is aimed at "converting" (or replacing) the existing static HTML blog front page on my website in favor of a "standard" blog front page (XML?) that can be handled by blog search engines like Technorati and various RSS feeds so I can syndicate my content. I'd prefer an RSS 2.0 feed type as opposed to Atom. (with a functional "Subscribe" button on the blog front page) I want the blog entirely on my website - not on Blogger or other 3rd party services so that I am not at their mercy regarding content, "look and feel", access or "corporate policy". Basically I'd like something like a main page "template" that I can "drop" my content into so I'm not struggling with creating XML blog pages every time I want to post a new article. I can "switch" the new blog main page with the older one, archiving the older article and putting a new link to it on the new main page. This may sound a bit "clunky" but it gets the job done. If you can suggest a better way, I'll listen but reserve the right to make the final call on how we do it. I don't want to depend on any server-side features and services because I change host providers every now and then and learned the hard way to do everything on my local system and FTP to the server. My content is mainly text, JPEG graphics and links to other web pages. I also want to link to older PDF & HTML articles I have on the site, saving older blog articles and providing links to them from the main blog page as I continue to generate new articles. See "Deliverables" section for additional project information and requirements. ## Deliverables (1) Complete and fully-functional working code and/or program(s) in executable form as well as complete source code of all work done. (2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): (a) For web sites or other server-side deliverables intended to permanently exist only in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment or provided to the Buyer with all the necessary information and instructions allowing the Buyer to install and run. (b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. (3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). (4) Deliverables must conform to the intent expressed by the Buyer in the "Description" "Deliverables" and "Platform" sections. (5) Deliverables to be sent by Seller to Buyer via download and/or by CD as agreed between Buyer and Seller and shall include all elements specified in "Description", "Deliverables" and "Platform" sections as well as any other information needed to adequately document and complete the project. (6.) Additional Project Requirements and Information: I'm pretty savvy on technical issues but find that the technical details of actually implementing a blog on my website unnecessarily complicated to the point of impossibility. I do not code HTML directly, though I do have the ability to edit it substantially as the need arises. I normally use Dreamweaver MX to set up the basic page and edit the HTML "bloopers" that Dreamweaver is famous for. I have no ability to edit or write XML documents. I tried "upgrading" to Dreamweaver 8 with horrific results and went back to Dreamweaver MX because I don't have time for steep learning curves, discovering new bugs and all the typical endless industry upgrade games. I may try Dreamweaver 8 again someday when I have time to waste on all the upgrade issues, but that time is not now. I have looked at blogging platforms like Wordpress, Type Pad, Blogsmith and Movable Type but all of them have some sort of deal-killer issue or other that negates all their advantages. I finally came to the conclusion that the best approach is something I can use and maintain on my own local system which is entirely uploadable to my website host using FTP. I am looking for a coder I can work with who has patience and will take the time to work with me through various issues that come up in this project. That person needs to be able to write and comprehend standard English in extended email communications as needed. If you normally write in terminally short "Twitter-ese" posts, this is probably not the project for you. Email is the preferred communication medium. Phone communication may be necessary from time to time but only as an adjunct to email. The Seller must be able to engage in relevant communication with Buyer as needed to maintain progress on the project and to keep Buyer appraised of progress. Nonresponse to communication queries or inappropriate communication for an extended period of time shall be cause for termination of the project with the Seller. This isn't rocket science and ought to be a comparatively short and easy project. I do need the option of "going back to the well" - meaning that if there are additional "tweaks" or changes needed after the initial project is completed, I need to be able to get those done without all the hassle of a brand-new project. Additional work would be negotiated for and payment agreed upon in each case after completion of the project. Any changes would ideally be done by the same person who did the initial work during this inevitable "clean-up" phase of the project for the sake of saving time and promoting cost-effectiveness. The existance of any "clean-up" work does not imply that the project deliverables can be deficient. The initial project deliverables must be complete and fully functional and meet provisions according to the "Description", "Deliverables" and "Platform" sections. The time frame of the initial project is flexible with a maximum period not to exceed three months. This does not imply that the project will take 3 months. The work required is very minimal but the Seller may wish to work on the project "as time permits", for example, in order to hold down costs. Notwithstanding this time flexibility, the deliverables will be provided to Buyer within a 3 month time frame, unless otherwise agreed in writing by Buyer and Seller. ## Platform The deliverable (new blog main page as noted in the "Description" and "Deliverables" sections above) must be compatible with IE 6 browser and later and Firefox 1.5 browser and later. Compatibility with Safari and Chrome are desirable but not required. The deliverable must be compatible with the Dreamweaver MX editor if at all possible and if that is not possible, must be editable in some fashion on the Buyer's local PC with some other editor and uploadable to Buyers server host via an FTP program agreed to by Buyer before project is commenced. Buyer's local PC operating system (OS) is Windows 2000 Professional. All deliverables must be capable of being edited and uploaded via FTP to Buyer's website using that OS.