Web Site Building

Verb

Can anyone help me please?

I came up with a concept some time ago for an interactive website. But although I did allot of web design in university I'm way behind with the times now. I have been advised that the site I have in mind needs to be a php built database.

At this stage of planning I'm interested in understanding the legal sides of building a website and storing user’s information as well as how to write (if necessary) Disclaimers’ or T/C’s. All of this I know nothing about.

Also, how would I go about finding someone / some company to build the site? Obviously cost is the main issue at this early stage. Someone has already told me that the best way to start is to look to someone just starting out in this business for themselves and come up with a deal that benefits them as much as me in getting it done cheaper. But also I know nothing on doing this. Any advice would be great.

steve1980

When you say interactive, what exactly will be interactive? That one word can mean so many things in the website world.

Verb

I mean. There will be 2 types of accounts. The first is someone with items to be reviewed (This will be multiple people with many items). The second will be someone who logs in has an account and can search through all the items, select and review (they can do this more than once on the same item) and a record will be kept on their account. They will be able to search through the site and their own accounts through a variety of filters. Please excuse my slight vagueness.

paddyrg

Find similar applications on the internet and work out how you can reuse something that already exists. From your vague description though it sounds like you could take advantage of a Drupal base with a few tweaks - and that'll be at least £10k cheaper than starting from scratch.

For your business questions, why not head over the Small Biz forum?

BTW - junior programmers/straight from uni are generally a terrible investement for getting a decent site. Often they can cut poor-to-reasonable code, but have no real-world architecture experience - and that is where the big savings are. For instance I've seen (many, many times) junior developers get all excited about doing the fun/cool bits, and wanting to develop from scratch, but many years in IT at a senior level really proved to me that the smart money looks to someone with a senior architectural overview who will then manage the developers!