post #21 of 21
The biggest part of the problem (as mentioned previously) comes from handling any appreciable volume with static pages like you're working with. The second one is the security issues. As I initially understood things (incorrectly, apparently rolleyes.gif) I thought you were just trying to have a small 'pick it' site where friends and personally networked clients could configure their custom build - and have the configuration emailed to you - with no payment processing, etc.. being done on the site itself. That seemed to be what you were indicating with your comments regarding the direction.

If you're not storing any personal information (other than briefly passing email address, phone number, and order details to a script) anywhere on the site - which you won't be able to with a static site regardless - you don't have to worry as much about security. The worst thing that can happen is you might get someone using a script to bombard you with bogus orders - but since you'd be handling payment processing offline - that's only a logistical nightmare - not a legal/financial one. Although depending on how secured the web server itself is, and that of your processor, you could be open to a man-in-the-middle attack to hijack your users' data as it travels between the two servers.

It would definitely be a good idea to have an experienced developer build your site - but if you can't afford to get a good one - you really need to consider giving up some of the 'bling' in favor of using something that's already built and proven. There are lots of sites that use amazon, yahoo, etc.. to handle all of the backend processing (so you aren't storing any personal or financial information on your site - other than an order number and some basic contact information). I already posted some prebuilt cart systems in my first couple posts - but since ZenCart is the one used by default for goDaddy hosting - I'd initially suggest spending a few days going through their documentation and tutorial videos as well as seeing if you can find some unbiased reviews of shops that have/are using it for their front end.

The one advantage you have by doing your static site at least, is that if you do hire a developer - you can much more easily communicate to them what you are hoping to have your customers see when they access your site - that should save time/money over having some scribbles on napkins. biggrin.gif Like any construction project (online or physical) get past references and contact them as well as getting a couple of competing quotes (at least 3 total if possible). It's often helpful to have some stages in mind when subbing out a project of this nature... i.e. don't worry too much about having FPS/PSU calculators and flashy animations - or at least get those quoted separately. If you go with a reputable developer, they will work with you do design something you can afford now, but write it in such a way that you can easily add features/functionality down the road without having to start all over again.

And always, always, always bid the project or phase of the project at a flat rate for completion - never agree to paying a simple hourly rate. A decent shop will quote this way automatically. However, on the other end - be prepared to pay dearly if you have changes after the job has started. I almost never have projects that work out that way - and as a result it's usually the client that ends up paying dearly for a mid-project change - but it's the easiest way to keep your development costs low and your developer happy!
Edited by DiGiCiDAL - 5/23/13 at 6:11am