When creating a website

Should you start developing the backend i.e. database first or interface?

 

First you should create content ....
If you have one then first backend i think

Regards

 

No ignore content. what i meant was. Should i design the database for the site 1st or make the html, css etc.

 

Design the database first.

 

Start by drawing up a plan tables etc and then build the frontend last

 

Thanks bcabank and Notting, that's what i wanted to know.

 

I usually build front end ... the navigation and structure of the site first. Then you will know how to build out the backend.

 

This is what I do: http://www.14thc.com/how-to-build-a-web-site.html

Design the site first, but know the requirements of the DB. The site concept is more important than either IMO.

 

backend, interface is the last step

 

The database and the frontend are orthogonal and can be developed mostly at the same time. Both must be pretty much done before the scripts can be written.

cheers,

gary

 

I completely agree with rmccarley about the site concept. This should definately come first. ie knowing your target market and how you are going to achieve a sustainable competitive edge. But the DB should be planned (along with the planning of the interface) before the interface is built.

I suppose it comes down to preference though.

 

imho, database design first for future scalability is always a big plus... but that could more for corporate systems i guess.

 

i normally try and get the design out the way

 

i really can't see how you can develop the interface without knowing the table schema of the backend... unless of course, you're talking about simply creating a layout with the graphics and all for look and feel...

 

I've been thinking about this post for a coulpe of days and I've tried both in the past. I think it pretty much depends on how well you know the subject matter.

If, for example, if you want to put up a site about vacuum cleaners and you're already a vacuum cleaner expert, then you will probably be best served to put the db up first and then let your layout and design flow from the data model. Since as an expert you probably know all of the data points that you need.

On the other hand, if you're putting up a site about vacuum cleaners and you don't know very much about them, then starting with the DB can be difficult because you might very well find yourself needing to redesign the DB every time you notice a piece of information that will need to be displayed. In this situation you will probably be better off fleshing out all of the information you want to display by creating a design before you try to build the data model.

It's always easier to build a web site based on subject matter that you are an expert in, but that's not always possible.