- Before I even begin to build a website for a client, I engage in a deep conversation around two simple questions: Who is coming here and what are they looking for? I design the entire site around the answers to those two questions.
- Anyone coming to a business website is looking for information. With the answers to those two questions in mind, I build for the purpose of delivering that information to those people with as few clicks as possible (preferably none).
- Every time you add a page you add work for the visitor. One more barrier between them and what they want. One more thing they have to look for. One more thing they have to click. One more opportunity for them to just give up and leave. Therefore, make it as few pages as is possible and sensible.
- An example of the above that I often give to clients during our initial conversation is restaurant websites. Almost every restaurant website could be two pages. Home page: Hours, location, number to call for a reservation or further info. Page two: Menu (In HTML, not PDF, with prices!). Thats it. I can’t think of a single restaurant website that I’ve seen that needs more than that. Yet, almost every restaurant website I visit is way more complex than it needs to be.
- These days, almost everyone is coming to your site from a mobile device. This is especially true if your visitors are from outside of the United States. Build with that in mind (not only mobile friendly/responsive but especially choice of font types and sizes). Test everything — every page, every link, etc. — on a smartphone. Make it look good there.
- Most businesses should hire a copywriter and editor long before hiring a web designer/builder. In fact, most should worry far less about the design of the website. People are coming for information, not how pretty it is. Focus on the words first.
Ho trovato molto stimolante questo post di Patrick Rhone. Mi chiedo quanti ‘web- designer/developer’ riflettano attivamente su questi aspetti prima di mettere mano alla tastiera.