From my personal experience, I reckon that you might categorise the website design process into two sections: the style process that doesn't utilize a prototyping tool, and also the the one which does. Having been on sides with this fence, We've an understanding of methods both these processes work and although designing without a wireframe works, I'd personally have to vote towards them.
Wireframing, the roll-out of a "visual blueprint", doesn't have to be overly complicated. At the most basic, I have come across wireframes which are are simply series of post-it notes using the graphical user interface (UI) elements stolen them. These are then placed onto a notepad to indicate the structural layout. Match it up to wireframes produced through design software and you might view a a little more refined wireframe from the latter, but no matter how you intend to you could make your structural model, it makes sense always the identical. Simply put, it shows yourself, the consumer or some other party where things will likely be located on the page.
This may be a real-time saver in case you are producing a website to get a client. Rediscovering the reassurance of my events of located on "side A" with the fence, when making a website to get a client Irrrve never utilized to perform any wireframing process in the past. The complete process was comprised of: gathering requirements, spec'ing out your website, allowing the graphical UI then building the site in the event the design was agreed. The most important flaw I ran across in this process would be the potential for the customer attempting to affect the main layout quite considerably. I'd haven't any problem whenever they simply want to tweak things occasionally e.g. colours, make text larger, start being active . more images here and there, result in the video a little bigger (the standard stuff); nonetheless it was a whole lot more painful when they then wish to move numerous things about about the page that directly affected the "page template". Jumping onto "side B" in the fence and producing the wired layout to the site ensures that layout can be agreed beforehand in the knowledge that once the UI design is presented, you might then only have to update the standard stuff.
The need to Spell against each other for Clients
Regardless if presenting a wireframe to a client though, I have had occasions where they would be hesitant to sign this part off on the basis that it looks very "blocky" and "plain". "Yes it does" would be my immediate answer to this as these blocks will determine where we're going to put things on your lovely page to ensure that whenever you return to me afterwards once you have reviewed the graphical design, you can not then inform me exactly why is the navigation up here and never over there? Trust me, I have had clients like this previously so even if creating a wireframe, there might be instances when you'll still have to spell it out that this is purely to get the layout correct for starters, then we'll make use of the pretty little for it afterwards.
A collection of Design Software
There's no need to necessarily know your path around Adobe software so that you can produce some decent wireframes. I take advantage of an internet tool, Cacoo, to produce mine. This online software enables you to drag and drop pre-created elements onto your page. This may save considerable time during the process.?
Like with everything web related, everyone can have their unique opinion with this topic, but my very own preference is to use a wireframe whenever I'm designing a web site. Be it for a client and for my own, personal site, it does not matter mainly because it signifies that the UI design is increased because you're effectively working from a template.
If you are taking care of a job for any client, then aiming to have Joe Bloggs sign over wires prior to starting around the UI is a part of this design method that I might call fundamental to ensuring that you maintain good budget and time management techniques on the project.