HTML5/CSS3 Upgrade to DNS Portfolio

The URL: Front-End: [login to view URL] Back-End: [login to view URL] Login:xxxxxxx Password:xxxxxxx FTP: Will be provided Pre-amble: This is test bed for updating my DNS Portfolio Domain Sales Script. I am updating to a bootstrap responsive theme. And at the same time updating code to be HTML5/CSS3 compliant. The biggest part of this compliance is removing all the tables from both the front-end (1 page) and back-end (7 pages) and taking all formatting out of the pages and placed at the bottom of the respective [login to view URL] files (1 for front-end and 1 for back-end), but probably you can just copy the back-end [login to view URL] over the front-end [login to view URL] (ie use the same data in each file. If slight difference to each file just include all in 1 file). To Do: Front-End (1) The menu hightlight in the [login to view URL] file is the same color as the background in portfolio.php. So you need to change the color of the menu highlight so that the highlight is displayed. on both [login to view URL] and [login to view URL] (2) The number of domains in a category is colored black. This needs to be changed to white. (3) Remove all tables and page formatting to bottom of the front-end [login to view URL] Pages involved: [login to view URL] (4) Tidy up the formatting of code in portfolio.php. Ensure HTML5/CSS3 compliant code. Back-End (1) Remove all tables and page formatting to bottom of the back-end theme.css. Pages involved: [login to view URL], [login to view URL]; [login to view URL], [login to view URL]; [login to view URL], [login to view URL]; [login to view URL] (2) Tidy up the formatting of code in all files above. Ensure HTML5/CSS3 compliant code. Make Offer (1) Complete the integration of the Make Offer Page. Mostly just formatting work. [login to view URL] Job Finish Apart from not seeing any tables or formatting in the above pages, the job will not be considered finished until the follow tests are performed without errors or warnings (1) The WC3 Validator at [login to view URL] for [login to view URL], and, [login to view URL] (2) The HTML Validator at [login to view URL] for Front-End [login to view URL], and, [login to view URL], and, [login to view URL] for Back-End [login to view URL], [login to view URL]; [login to view URL], [login to view URL]; [login to view URL], [login to view URL]; [login to view URL] To Note (1) The Back-End pages face the same problems as encountered in the Front-End. (2) The system uses templates. So you won't find, for example, [login to view URL], under the root, (ie [login to view URL]) but you will find it under the template (ie [login to view URL]) and similarly for the Back-End [login to view URL] (ie [login to view URL]