130907 vehicle display app

I need a cms/product manager built specifically to display large ticket units such as motorcycles, tractors, atv's, etc. The project is effectively a product catalog for items that won't go through an online sale process (no shopping cart). I want something similar to the sDealer software found at [login to view URL] (download the free trial version before bidding please), but simpler and not geared specifically to automobiles. I expect the front-end display to be template wrapable (header/footer) and all unit display to be css as much as possible. W3 compliance is desirable. Requirements: 1. 7 specified content type fields (price, engine, drivetrain, transmission, make, model, year). Make and model will be dropdowns with data entry capability (if a make or model doesn't exist in the database a user can enter it without leaving the screen...think WordPress categories on a posting page). Year, make, model should all be used in the front-end display templates meta tags for title. 2. WYSIWYG field for additional details on the unit. 3. the ability to add fields and labels dynamically. At least a dozen additional fields are necessary. If a field isn't used, it should not display on the front-end (this is true of the pre-established 7 as well). 4. at least 4 pages of WYSIWYG managed content to be used for home, about us, specials, contact us. The possibility of one-click addition of pages would be great. Page editing should include title, description, and keyword fields to be used page meta tags. 5. Minimum 5 image per-listing upload capability with lightbox display on the unit display template. 6. The ability to delete listings with "Are you sure?" verification. 7. Customer contact form - the "contact us" page should have a customer contact form requesting name/phone/email/comments. It can also be used as the "request info on this unit" form if we pass unit information to the form from unit display pages. 8. Financing application form should have name of vehicle passed to it via query string. Admin should be able to configure TO/FROM/CC/BCC/Subject One key criteria is that if the field isn't filled in the admin, it doesn't display on the front-end. The main functional problem I had with sDealer is that it expected you to be selling individual unique units. That's fine for automobiles but not for motorcycles/tractors. Most of these dealers just want people to know what they have or can get, it's not about tracking exact inventory. I might put a TYPE of motorcycle in and post pictures of all of the available colors. No design necessary, just give me header and footer files to work with and I'll wrap design and navigation around the functional display areas of the site. DISPLAY CODE MUST BE W3C COMPLIANT CSS and xhtml. The admin design is up to you, though the cleaner the better. Take inspiration from the Wordpress admin interface. No clutter, easy to identify links, and context specific help info. Admin - The site will be managed by non-technical personnel within a dealership. As such, it is important that the backend be as easy to navigate and understand as possible. All steps should be taken to consider the secretary, parts counter guy, or mechanic that might end up managing the site. Web apps are not going to be the core competency of the content managers. The ability to have multiple admins is preferable.