3 XHTML Strict Website Templates and Design

We need XHTML Templates to be designed in photoshop and built into clean and proper XHTML Strict markup. Templates will be used for merchants (retail stores, restaurants, etc) in our online mall. There are multiple categories of merchants, we eventually want templates for each category in our online mall, located at http://www.helpwwmall.com. We want to start this process with 3 templates at up to $100 each. Over time, we will increment this value to 10 templates, at up to$100 each, if the first 3 are satisfactory. If the first 3 are not satisfactory, we will continue looking for someone to meet our needs, ie. if you do not meet the following requirements, we will not use your templates, and you will not be paid for the work. The first 3 templates we desire are: - Retail Store Template - Restaurant Template - Corporate Template Please submit an example of your previous work, when replying to this post. - Requirements: - These templates are going to be modified in a WYSIWYG Editor (TinyMCE), with limited access. Any editable portion will be extracted and put into its own include file. The users will modify the include file. If there is a section which needs to list data, such as a navigation or news area, and the markup is too complicated for the user to modify, the user will insert each item separately and control the order in which they appear in the list. The template will read the list the user has defined and insert the data appropriately (this is already completed). Therefore, there are two different content types: page content and data list. Each data list item has a Title and it has Content. You don't need to worry about the Template Syntax, only the XHTML and design. Each template needs to be very clean XHTML Strict markup. Make sure you validate your markup and your CSS with [login to view URL] Class names should be used instead of inline styles and background images should be used in all places where the image isn’t allowed to be modified. In other words, if an image needs to appear in the markup, and that image is part of the layout or is such that the user shouldn’t modify it, the rules which instruct the browser to render that image should reside in the CSS file. Likewise, if an image is allowed to be modified, use an image tag so that the WYSIWYG can provide controls for the user to modify it. There should be little inline CSS or JavaScript (only use it when needed), but consolidate all of your CSS code into two files when linking an external script. JavaScript can be in multiple files. Part of the CSS will be extracted so that the editor can load it and render styles for any content page the user wants to modify. Take this into consideration while building the markup. This file will exclude body styles and other layout styles that wouldn’t apply to content areas. Submit this file along with the rest, and name it “[login to view URL]”. The other css file you may name to your choosing, something along the lines of “[login to view URL]”. Again, any content area that can be modified should have its rules defined in “[login to view URL]”. Try to group your class names with container elements. In other words, if you have links that need to use a class name, try to apply that class name to the parent element: <div id=”parent” class=”link_class”> <a href=”#”>link_class styled link</a> </div>. Do this whenever possible. Of course, individual elements can have their own classes, but avoid it when you can, as this makes the process more complex when the user tries to modify the content. No Table Layouts! Only use a table when listing tabular data. The store's name will be printed in text, in place of the logo. Try to use some CSS to style this, instead of a typical logo image. - Page Details - The navigation should be visible on every page and each template should come with the following areas defined and extracted into clean, XHTML Strict markup. 1) Home Page a. This page should have some welcome text that the user can modify. b. This page should list the 5 newest news announcements. Use a UL or a Definition List. c. For merchant templates, the home page should list bonus rewards and basic contact information with no map. Bonus rewards are: Birthday Rewards, Dollar Spent Rewards, X Purchases Reward (see live site for demo). 2) Contact Information Page a. This page should contain contact information such as, Business Name, Address, Email, Phone, and a form with a Captcha. Design the form and provide an area for the Captcha, we will implement these features. b. This page will render a google map with an icon representing the company’s location. Provide a place for the map in your design and in your markup. c. This page needs to have the company’s business hours, accepted credit cards, and other restaurant information such as whether or not they support Dine-In, Take-Out, Buffet, Breakfast, Lunch, Dinner, etc (see merchant signup form on live site). It needs to list the lunch entrée price, dinner entrée price, cuisine type, etc. 3) News / Announcements Page a. This page should list all of the news announcements the company enters. News announcements will have a title and content. The title will say whatever the user enters. Use a UL or a Definition List. 4) Product Information a. For all merchant templates, we need a page for them to list featured products. This will be a data list. You can style this page however you want, following the rules listed previously in this document. b. The product list should consist of an image, a name, a price and a description. There is no checkout as of yet, this is just a list. c. The product page should list merchant bonus rewards, such as: Birthday Rewards, Dollar Spent Rewards, X Purchases Reward (see live site for demo). d. This page needs to have the company’s business hours, accepted credit cards, and other restaurant information such as whether or not they support Dine-In, Take-Out, Buffet, Breakfast, Lunch, Dinner, etc (see merchant signup form). It needs to list the lunch entrée price, dinner entrée price, cuisine type, etc. e. For restaurants, this page will be a menu instead of a product list. Design it accordingly. 5) Basic Content Page a. This page should be named “[login to view URL]” and should contain a content area that has a slightly different layout than that of the home page. The home page should have a bit more to its design than this page. This is intended to be used for sites to create new pages. The content they create in the WYSIWYG will go into the content area of this page.