Originally Posted by cuda2k
Can a Wiki let you put in a serial number of a frame and return to you a number of possible identifications of that frame based on the format of the serial number? Can a Wiki have a multi-part fully customizable, wizard style search engine with reference images and dynamic page generation based on the information already given. Can a Wiki automatically re-size uploaded images to reduce bandwidth costs. I could go on with this but I won't.
Sure why not? No matter what you want to call it it's still an ad hoc search. What I'm suggesting is that you look for a CMS type project and spend time on the custom parts you want instead of on the plumbing. For example the registration. Registering users for forms authentication is in virtually ever CMS system available. Take a look at Dot net nuke.
Originally Posted by cuda2k
Its your opinion that you disagree with my over all motives here. But I'm sure many others will be more than happy to wait a little longer for me to build exactly what I am envisioning instead of throwing a pre-packaged up on a site and letting everyone go at it.
My point is your first production version will not be the last version because you will only notice problems in production. First versions never last long. There is always something to refine. That refinement can be very difficult when it's in production.
Creating a CMS from scratch is nontrivial. If you really want to learn your better off learning how a well built existing system works and use that knowledge the next time. This will cut down on your learning curve and work.
I'm the same way; I learn best by doing. I'm only relaying this to you from experience.
You have a good idea, but you may need a more professional approach.
Anyways, good luck either way...