I have read about the advantages of utlizing css formatting to replace html tables and other html formatting, but I don't have the expertise to do so myself. I'm looking for a coder to do update the pages, fix compatibility errors, and document their work so I can learn from it.
The .zip file that accompanies this bid request has two files: - [url removed, login to view] - [url removed, login to view] The first is the page that I want fully transitioned to css formatting and the second is the existing css file. [url removed, login to view] already uses some css formatting; however, I believe there is a lot of room for further css formatting. e.g.: - replacing the tables - replacing the image-driven borders with css-driven borders - etc. The final product of this project should be a rebuilt [url removed, login to view] that looks virtually identical to how it looks now, but benefits for complete css formatting. I hope that the complexity of the code and the size of the file will be decreased significantly (from [url removed, login to view]) and that utilization of css formatting will make it easier for me to manage my site (once I apply css formatting to all my other pages). I use Dreamweaver MX2004 and it currently says that [url removed, login to view] has 74 compatibility errors (testing against IE 4.0+, NN 6.0+, Mozilla [url removed, login to view]+, Safari 1.0+). The improved [url removed, login to view] should be compatible with all those and should have no Dreamweaver-reported compatiblity errors. Of course, there will have to be additions made to the [url removed, login to view] file. Please note that my site has other pages that currently use [url removed, login to view], so the existing elements of [url removed, login to view] can not be altered for this project. New elements in [url removed, login to view] must not conflict with the old ones. [url removed, login to view] is just a sample page that I will then use to make changes to a dozen or so other pages in my site. Thus, I would like for both [url removed, login to view] and [url removed, login to view] to have lots of coder comments explaining what each part does so I can learn from it and repeat it. Thank you in advance for your bid. Depending on the number of bids I receive I might not reply to each bidder. However, I often add select bidders who submit bids that I don't choose to my Favorite Bidders list, so even if you bid and don't hear back from me, you might receive a personal bid-request in the future. I prefer a lot of communication, so if you have any questions, suggestions or comments (especially if you think I am not asking for the right things to be done), please let me know. All the Best, Erik Summary: - rebuild [url removed, login to view] with full css utilization - add to [url removed, login to view] but don't alter its existing elements - put a lot of coder comments into the two pages - make sure that [url removed, login to view] is fully compatible with browers listed above (no errors reported my DW MX 2004) 1) Complete and fully-functional working 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 only ever exist 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.
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).
I use Dreamweaver MX 2004 for Mac.