From my own, personal experience, I guess you could categorise the website design process into two sections: the look process that doesn't make use of a wireframes, as well as the the one that does. Previously being on sides of the fence, I've an awareness of methods these two processes work and although designing with no wireframe does work, I'd ought to vote in favour of them.
Wireframing, the growth of a "visual blueprint", doesn't have to be overly complicated. At the most basic, I've seen wireframes which are simply are number of post-it notes with the user interface (UI) elements stolen them. They're then placed onto a notepad to exhibit the structural layout. Match it up to wireframes produced through design software and you may go to a better refined wireframe from the latter, but regardless of how you intend to build your structural model, it makes sense always exactly the same. Simply put, it shows yourself, the consumer or any other party where things will probably be situated on the page.
This can be a real-time saver in case you are making a website for the client. Finding comfort my era of being on "side A" of the fence, when producing a website for a client I never used to carry out any wireframing process back then. The whole process consisted of: gathering requirements, spec'ing out the website, creating the graphical UI and then building the website when the design had been agreed. The most important flaw I ran across with this process could be the risk of the consumer looking to affect the main layout quite considerably. I'd haven't any problem should they would like to tweak things here and there e.g. colours, make text larger, start being active . more images occasionally, make video somewhat bigger (the usual stuff); nonetheless it was obviously a whole lot more painful whenever they then desire to move a number of things about for the page that directly affected the "page template". Jumping up to "side B" with the fence and producing the wired layout for that site ensures that layout may be agreed beforehand in the knowledge that in the event the UI design is presented, you might then only need to update the standard stuff.
Needing to Spell against each other for Clients
Even though presenting a wireframe to a client though, I've had occasions where they'd be unwilling to sign this part off because that it looks very "blocky" and "plain". "Yes it does" can be my immediate response to this because these blocks determine where we are going to put things on your lovely page in order that whenever you revisit me afterwards once you've reviewed the graphical design, you can not then say to me why's the navigation up here and never there? Trust me, I've had clients similar to this in the past so even though producing a wireframe, there could be instances when you continue to have to spell against each other that is purely to find the layout correct first of all, then we'll use the pretty little bit with it afterwards.
An Arsenal of Design Software
There's no need to necessarily know the right path around Adobe software as a way to produce some decent wireframes. I personally use a web based tool, Cacoo, to produce mine. This online software permits you to drag and drop pre-created elements on your page. This will save considerable time along the route.?
Just like everything web related, everyone can have their very own opinion for this topic, but my own preference is to apply a wireframe each time I'm designing a web site. Whether it's to get a client or for my own, personal site, regardless of because it ensures that the UI design is increased because you're effectively working coming from a template.
When you are taking care of a project to get a client, then aiming to have Joe Bloggs sign from the wires before starting around the UI is part of this design process that I might call important making certain you maintain good budget and time management techniques on the project.