PHP coding before website design?

When you are coding for yourself or for a client, do you get the php coding done first then work or have someone work on the design of the site or the other way around.

Do you have a reason for your approach to a project?

I understand that not all tasks will be performed by yourself and it may be a partnership or a group effort.

Just trying to understand better the order that you will work on a project.

 

I code the php first, make an ugly but functional UI. I then wrap the design around it. This is how I've always done it.

Yeah, once I have an idea, I'll open notepad, and list all the ideas, then what I need to do for each, like so:

Digg Trade Script

User system
     Login
     Registration
     Referal System

Code (markup):

etc...

 

I always make the design first, no special reason for it really

 

Hi WeedGrinch, thanks for explaining your approach, it sounds like it works well for you.

Hi aGor, would you happen to be more of a design person anyway? or as you say no real reason, thanks.

 

Both?

I tend to build my framework, design the next site, tweak the framework, design the next site, etc. etc. I've built up a small library of solid, secure code to work with.

I suppose the answer would be 'design, because I've already finished the coding', but that might be cheating >_>

 

It's actually a good idea. I mean, i've coded 20 login system, nothing unique about each one, simply because i didnt save the others.

*Creates a folder called php library*

 

hahaha ouch.

Twenty is a bit much. I'm working on my third serious login system at this point - trying different things and learning new or alternative methods is always valuable. But there is always a point at which you have diminishing returns and you perfect a small piece. My e-mail validation system being one example, though the larger scope it fits in (e-mail account management) is still in flux.

 

i like make php first . because its easy to manage template after that.

 

I always do the design first. Only reason being that it's habit. I had my first website before I knew PHP, so I naturally had the design done first, and when I started learning PHP I incorporated into the design.

 

I write down the structure of the php scripts i use on the sites, then i make the design and after thet I implement the PHP into the site

 

I get an idea in my head and think about how I'd (in general) code each portion of the site. I then seek a design for it or attempt to make a rough design (though I'm not a designer) - this helps me visualize what I've planned and helps me come up with more ideas or a better approach to how I had already planned on coding something.

 

I write the PHP after the design, more simpe for me

 

Thanks everyone for your input on this.

 

If it is for myself, I do programming first, but when dealing with client, I show them the design first because usually my clients would know the end results.