Chicken or the Egg problem
-
-
Usually both. First I start creating a cool graphic template, then I convert it in webforms, then redo all because I no longer like it... ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA]
-
getting the functionality right first seems more important than getting the looks "right" first. So I would do a web layout first and then "skin" it.
-
getting the functionality right first seems more important than getting the looks "right" first. So I would do a web layout first and then "skin" it.
ahz wrote:
getting the functionality right first seems more important than getting the looks "right" first. So I would do a web layout first and then "skin" it.
Well, you on some sites you see, that they have done it this way (and only the half). They seem not to be usable. If first make a layout, then develop a simple website and afterwards adopt it to the layout I wanted. Greetings, Ingo ------------------------------ A bug in a Microsoft Product? No! It's not a bug it's an undocumented feature!
-
I am working on a web project now and I am thinking of getting the ASP.NET code right first and then I can change the looks to whatever I want using CSS. Sort of like the CSS Zen Garden[^] approach. I am not sure how well this will work out in practice.
Member - the great cult of Firefox at CP
-
I generally sketch out the layout and fundamental elements on paper then take that into Photoshop/Fireworks to make it look nice and then out to HTML and CSS. regards, Paul Watson Ireland Feed Henry! K(arl) wrote: oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
-
I work in a concurrent process. Start out with a rough draft of the design of the site and then start doing the code. Go back and work on the design and make changes and the alter the code the match. Sometimes code dictates design and other times design dictates code. Its always a per project situation, theres really no right way to do it, but I find you cant do one before the other.
-
I have followed these steps many times: 1) Create a Photoshop file (or am given one from a designer) 2) Usually there are two files, one for the home page and another for sub-pages 3) I do the image slicing and conversion to HTML 4) I usually slice the navigation separately and create a separate PSD for it 5) Next, create a style sheet for the site 6) Flesh out the navigation logic (in DHTML, JavaScript, database driven, etc.) 7) Then I bust out common areas into separate web user controls (header, footer, navigation, etc.) 8) Create stub pages for all pages in the site 9) Complete the "Code behind" for each page (usually a data model is built before this step) 10) Add greeking text and stock photos to the pages (I'm not usually responsible for content) 11) Turn over for user acceptance testing and content authoring So basically, I wait and let the graphic design drive the programming. Hope this helps, David
-
Typically, in the old days, I would start with a blank Photoshop file and create the basic site. Many times, I would create the different pages of the site using multiple layers in Photoshop. This gave me a method to visual the majority of the site before I commited to a given look of feel. After this, I would build a template for the site. Nowadays, I will bring up DotNetNuke, create a new portal, build out the site and see just what modules if any I need to build. Then I hit Photoshop, build the "look and feel" and convert that into a skin and container files. Then I am finished and can move on to another project. There are those rare times though, that I do not use DNN, Iw ill build the site out with Photoshop and convert the exported files into a Master page for ASP.NET 2.0. Typically a site may use a couple master pages depending on site layout. Most of the time though, it is DNN. Rocky <>< Latest Post: SQL2005 Server Managemnet Studio timeouts! Blog: www.RockyMoore.com/TheCoder/[^]