Hello!

[oddjosh]

Hello! I have just officially joined this group. I am pretty sure I
want to base an e-commerce solution on this code. I love how clean
the code is and the fact it's built on ASPNETMVC. I will need to do
extensive additions to this in order to fit my clients needs, so I
thought I would join this group and perhaps contribute some of my
work.

Here are a few concerns/questions I have about the latest build:

1. Is there any reason the Model layer of the application is not in a
separate project? I love how clean the code is currently, but I
think one could take SoC a little further by placing the Model layer
in another asembly. Thoughts? Perhaps there's a reason it isn't?

2. Category SEO/navigation. I would rather the URL for a category be
something like: "http:///Category/X". This should be an easy
addition, perhaps someone else has already done this?


Thoughts anyone?

[Mike Hadlow]

Hi Oddjosh,

Thanks for checking out Suteki Shop, and for the kind words!

In answer to your questions:

1. My general philosophy with project organisation is not to confuse
logical & physical separation. I physically seperate things that I
might want to deploy seperately, so the Suteki.Common project is
broken out because it contains stuff that I reuse in my commercial MVC
Framework projects, the intention was (and still is, if I get the
time) to create a fully featured starter kit somewhat like Sharp
Architecture based on this code. The only change that is probably
worth making now is to separate out the deployable elements (views,
config, js, css and images) from the compiled code. But of course you
are free to take the code and do what you like with it. If it makes
sense for your project it should be trivial to separate out the model
layer.

2. It would be simple to change the routing to do what you want. In
fact it sounds like a good idea. We already to this with products so
it would make sense for categories to behave in the same way. Add an
enhancement request to the issues list or better still, submit a
patch.

I'm looking forward to seeing what you come up with.

Cheers!
Mike