[PixelBit]

Should i design and get the layout sorted or code the functionality first? Or does it matter? Which will be easier for me in the long run?

EDIT: I've made a site map and planned out all the page relationships and such.

This post has been edited by PixelBit: 14 September 2011 - 07:57 AM

[sas1ni69]

Hey there This is quite a personal opinion. There's no right or wrong here. Maybe you should code the basic layout and then to into the functionality. When you're satisfied, go over the design and improve it. Good luck!

[noscript]

Hey
Personally I create the basic layout and give it basic styling with css,
I use heaps of clashing colors to show the different elements in the page,
and then make some quick adjustments, then its straight to coding.

I noticed this at tech, everyone else was very focused on their projects styling first,
then they added the functionality, I personally work the opposite make it work then make it look pretty.

I don't think it really matters just whatever feels right for you and planning out your project always makes it easier.

Good luck

[Hqtitan]

I usually start out with setting up the basic layout with borders around the elements so that I know where they're at. Then I get all of my content and functionality put in, and then work on the rest of the styling.

[KingCuddles]

I always get the basic layout and functionality done first - get it working in which ever browsers I choose to support - then get the client to ok the functionality. Then I make it pretty .

[Infinite loop]

I Agree with the previous post a rough layout and style is good. I like to create a style sheet just so I know all the elements are hook correctly mostly just clashing colors and borders everywhere at this point. Once it works I make it look acceptable before I pass it to the marketing department to review and improve.

The Important Question is are you sure you can make it work before you spend time making it look good.

If not make sure you can make it functional before spending to much time on how it looks. Trust me it sucks being stuck with a beautiful disaster and smaller things can be almost as annoying. For example like setting up a nice page style with a drop down list in mind then finding out you have to use a textbox for some reason instead.

[Lemur]

Neither. Content is king. Unless you know what and why you can't ever hope to get to the how. Implementation and design should never precede preliminary research and analysis.

[Shane Hudson]

Lemur, on 04 October 2011 - 08:52 PM, said:

Neither. Content is king. Unless you know what and why you can't ever hope to get to the how. Implementation and design should never precede preliminary research and analysis.

This is true. However I think we need to clear up the word design. It does not just mean graphically. Design is about taking an analysis (could be a 50 page report or it could be a meeting with your client or just thinking the idea over in your head) and figuring out the best way to make it work.

• Who is using this website?
  
• How much content will there be?
  
• Should each page be different?
  
• What kind of layout will the user be expecting?
  
• What colours make sense for the purpose of the website?
  
• Will the website require a CMS?
  
• Which CMS would fit the purpose and functionality of the website?

The list is endless.

Design should be done before implementation. That is not to say you design the look of the website before you design how the backend will work or how the pages will link together. Get all of that sorted, design the website (on paper or on design software) THEN start making it.

When I am making custom CMSes I start with the backend, AFTER I have designed it. The website will generally look terrible or not even be able to see it for the first 75% of the work.

This post has been edited by Shane Hudson: 05 October 2011 - 05:16 AM

[Duckington]

I find the best way is to:

- Create a very simple css/html layout
- Then work on the key functionality
- Check with the client that it's functioning how they expected
- Then complete work on functionality
- Then do the actual design
Obviously with various client meetings throughout to discuss it all.

Of course it's up to you how you want to work.