Well, if you put everything that I want to see in a Getting Started
guide, it'll end up being a book! :) (which may not be a bad idea by
the way).
I would (humbly) suggest some information on how the different pieces
fit together from an architecture perspective, and then maybe dive
deeper into your thought process about the more complex areas. More
than the code itself, its how and why you, as a much more experienced
developer, built it that way that makes it more interesting. Of
course, this could very well be a series of blog posts (or a book/
ebook that I wouldn't mind paying for) instead of in the wiki.
I'm not really building a store/ecommerce application (at the moment),
but the same concepts/architecture/methodology would apply to most
real-world (read "non-demo") apps, and I would love to understand the
inner workings and learn from it.
Thanks!