Posted by Jim Michaels on 10/10/28 11:39

"windandwaves" <winandwaves@coldmail.com> wrote in message
news:hyAxf.14336$vH5.770216@news.xtra.co.nz...
> Steve wrote:
>> On Thu, 12 Jan 2006 11:18:46 +1300, windandwaves wrote:
>>
>>> Hi Folk
>>>
>>> I would like some feedback on my e-commerce development:
>>>
>>> www.antlervelvet.co.nz/test/index.php
>>>
>>> I am particularly interested in the actual e-commerce application
>>> (e.g. navigation, ease of use, etc...). I am trying to turn it into
>>> my first open source project and I want to post it on phpclasses
>>> when it is ready.
>>>
>>> TIA
>>>
>>> - Nicolaas
>>
>> 1. I'd say that the shopping logic is the wrong way round: let the
>> punter build up an order, then log in to an account at the end to
>> process it. I also don't think the page with all the buy now entries
>> on it works - too long. I would have tried further, but I'm not
>> adding my details to a site I'll never use (:
>
> I have taken up part of the ideas (no need to activate account). May
> implement more.
>
>> 2. Upgrade to at least xhtml.
>
> why? what is wrong with html strict?

because I hear XML and xhtml can somehow work together with all these new
technologies coming out, whereas HTML is left out in the cold. MySQL can
now export XML, and companies transfer data as XML or they keep their
product base in XML. (and because of that, they expect an e-commerce
solution knows how to do DB data mapping). I am not suggesting that you go
XML though - I don't know how much extra work that would be.

>
>> 3. Prettify your html: it'll make it easier to see obvious mistakes (
>> 2 favicons? ). Get rid of this session id that you're passing all
>> over the place - it's not necessary. Use of (more) session variables
>> will make it much cleaner. Standardise on the position of your login
>> box.
>
> I have:
> <link rel="icon" href="http://www.antlervelvet.co.nz/i/favicon.ico"
> type="image/ico">
> <link rel="SHORTCUT ICON"
> href="http://www.antlervelvet.co.nz/i/favicon.ico">
>
> I have two, because the first works on some browsers and other works on
> other browsers.
>
>
>> 4. Visit http://validator.w3.org and
>> http://jigsaw.w3.org/css-validator
>
> Done, all my pages validate now.
>
>>
>> 5. You could do with a proof reader. I picked up on a number of 'word
>> ,next' grammar errors, and I'm not too sure whether the language is
>> English or American. Always a problem for those of us here in godzone
>> (:
>
>
> What do you mean with 'word, next' grammar errors
>
> The American / English one is a funny one. True. Not sure what to say
> about that.
>
> Thank you
>
>> HTH,
>>
>> Steve
>
>

[Back to original message]