Hey,
im willing to build ( not myself) a website.
now my question is, what comes first?
the web design or the coding?
Thanks
I think you would build the design first then code the design.
First go for the design and let the code after
If you're making it from scratch, code the basics, then design it.
(Jun 22, 2013 08:44 AM)`Ninja Wrote: If you're making it from scratch, code the basics, then design it.
I strongly disagree, you design the mockup in photoshop first. Then you cut out the images that make up the design in small sizes because you can code them to repeat anyway. THEN you start coding the design.
Although I usually do this:
- Make mockup in photoshop
- Code the site and create the images as I go
Always, you must design the website first, create the outlines, make a proper structure, and when you have the final image of your website, you can easily slice it out and code the front end of your website. This is how it's done.
Then later if you want you can convert this into a wordpress or a tumblr theme. Or can be used for a custom script.
(Jun 22, 2013 08:46 AM)ObscureCoder Wrote: I strongly disagree, you design the mockup in photoshop first. Then you cut out the images that make up the design in small sizes because you can code them to repeat anyway. THEN you start coding the design.
Although I usually do this:
- Make mockup in photoshop
- Code the site and create the images as I go
Yes to a part, you do a mockup/draw something AFK to have your idea on a paper then you start working on it (coding) and designing after each object ..
im willing to hire a web designer,
but also willing to hire a web coder.
should they be the same person?
or would it be okay if they would be diffrent persons?
p.s
what is this "mock up"?
(Jun 22, 2013 08:59 AM)Vaxxor Wrote: im willing to hire a web designer,
but also willing to hire a web coder.
should they be the same person?
or would it be okay if they would be diffrent persons?
p.s
what is this "mock up"?
Its upto you if you hire the same guy or different ones.
A mockup is the image made in Photoshop that shows how the website will finally look when coded.
(Jun 22, 2013 08:59 AM)Vaxxor Wrote: im willing to hire a web designer,
but also willing to hire a web coder.
should they be the same person?
or would it be okay if they would be diffrent persons?
p.s
what is this "mock up"?
Easier and better if it's the same person, a webdev or at least working together.
A mockup is a basic idea design to make at first, like putting your idea on paper to be able to take it from there, much like a basic building scheme or what to call it.
thanks guys!
that was really helpful!
How I work: I call websites, or anything a "Project".
First, I have a notebook. This is the initial blank sheet of where I write/draw what' the project goals are. A list of what I need to do/accomplished.
Then in the notebook, I draw up a wire frame for ideas what the website could look like.
Once I like the sketched wireframe, I'll go in Photoshop and make up another wire frame, and find a good color scheme that the website would look good with.
Then I design the elements, create a mockup of the website. Unless it's an important client, I don't try to make the mockup/design result 100% complete, I can do that with code.
Once I'm done with designing the website and the client likes the design, I'll go ahead and start the development process, which is cropping out the necessary images and getting my tools ready. Then I start the coding.
That's pretty much it. I use code pre-processors and such to help with the development, I'll compile everything then set it up for the client.
Advice to you: Get a notebook/sketchpad. Drawing wireframes and planning before the designing parts helps A LOT. I found this out 2 years ago and I've been doing so much better.
Pay a person to do it all, alot easier if they know what the design is.
First come up with some ideas.
The design is first and should be the most important thing, because almost everything is possible with the coding if you're skilled enough
The design is best to do first, kind of hard to code the backend without even seeing the frontend.
|