From my personal experience, I guess you could categorise the website design process into two sections: the design process that doesn't use a mockup tools, and also the one which does. Being on both sides of this fence, We've a comprehension of precisely how both these processes work and even though designing with no wireframe does work, I would have to vote to be replaced by them.
Wireframing, the growth of a "visual blueprint", must not be overly complicated. At most beginner's, I have come across wireframes which can be simply are number of post-it notes with the user interface (UI) elements stolen them. These are generally then placed onto a notepad to exhibit the structural layout. Match it up to wireframes produced through design software and you will view a better refined wireframe from the latter, but regardless how you intend to make your structural model, it makes sense always the same. Simply put, it shows yourself, your client or another party where things will likely be found on the page.
This may be a realtime saver in case you are creating a website for any client. Going back to my days of due to being on "side A" with the fence, when making a website for any client I never used to accomplish any wireframing process in the past. The complete process contained: gathering requirements, spec'ing out the website, creating the graphical UI and after that building the site once the design have been agreed. The major flaw I ran across on this process will be the possibility of the client looking to affect the main layout quite considerably. I'd don't have any problem when they just want to tweak things occasionally e.g. colours, make text larger, atart exercising . more images in some places, make the video a lttle bit bigger (the standard stuff); however it was a ton more painful should they then wish to move a number of things about for the page that directly affected the "page template". Jumping up to "side B" from the fence and producing the wired layout for the site ensures that layout may be agreed beforehand knowing when the UI design is presented, you could possibly then only have to update the usual stuff.
The need to Spell out for Clients
Even if presenting a wireframe to a client though, I've had occasions where they'd be hesitant to sign this part off on the grounds which it looks very "blocky" and "plain". "Yes it does" would be my immediate solution to this as these blocks determine where we will put things on the lovely page to ensure that when you get back to me later on when you've reviewed the graphical design, you cannot then notify me exactly why is the navigation up here and not there? Believe me, I've had clients like this during the past so even if to become a wireframe, there might be when you will still need to spell out that this is only to get the layout correct to start with, then we'll apply the pretty little into it afterwards.
A collection of Design Software
You don't have to necessarily know on your path around Adobe software to be able to produce some decent wireframes. I prefer a web-based tool, Cacoo, to generate mine. This online software enables you to drag and drop pre-created elements to your page. This could save time and effort along the way.?
Like with everything web related, everyone may have their unique opinion about this topic, but my own, personal preference is to use a wireframe each and every time I'm designing a website. Whether it is for a client and my personal site, it does not matter mainly because it implies that the UI design is hasten because you're effectively working from a template.
When you're working on a job for a client, then planning to have Joe Bloggs sign over wires before you begin about the UI is a part of this design procedure that I'd personally call fundamental to making sure that you maintain good budget and time management over a project.