Design or develop first?

[Wolf2]

I was wondering if I should go about designing my site first before implementing any back end capabilities.
I like to keep things organized and plan ahead so it would seem to make sense to create the static site first but i am somewhat unsure if I were to design first and end up redesigning to fit everything I plan on adding later, in terms of dynamic content.
Any tips on this would be great thanks.

[midlandi]

Depends on the method of your design I would say, mostly you should be able to plan that all you want to add can be integrated into the design you have.

[iPhone Fan]

You should have an idia of your site in your mind. Then you choose how to start to realize you idea.

[SeoKungFu]

Actually and ideally, the process should be :
- gather requirements and analyze them
- plan / schedule your timing estimates
- develop
- test / bugfix
- implement in production
This is not my own invention, it's briefly how normally, and professionally, it goes.
And well, design and development come after the gathering of requirements, of course.
It's much more efficient to do it that way, rather than changing the course of action somewhere on the run...

[a4hire]

I would agree that you should have some idea of what functions will be available at the site first. This will help to guide your design process.

[Lolito]

Actually and ideally, the process should be :
- gather requirements and analyze them
- plan / schedule your timing estimates
- develop
- test / bugfix
- implement in production
This is not my own invention, it's briefly how normally, and professionally, it goes.
And well, design and development come after the gathering of requirements, of course.
It's much more efficient to do it that way, rather than changing the course of action somewhere on the run...

I agree, this is called System Development Life Cycle. We assume you gathered all information and you analyze them. Of course we should design first before developing a prototype or design a database first before developing a prototype. In my own term I will call it "Blue Print" because we base the design before develop a system or prototype.

[joomladev]

Hi,

Actually you should go for design first and then mock up which will give you a complete idea of how your site will look a like and than you can start from backend as this is normal procedure we follow.

Thanks

[goldyweb]

Things go side by side... Put a first plan on.. then go on developing it..