Web Design


Web Design07 Dec 2007 04:14 pm

Here is the rest of the list.

1. Watch your load speeds. As a lot of people are on dial up, load speeds are an issue. No one wants to wait along time to have a page load. More and more are moving to faster connection speeds, but still a large percentage of people are still on slower speeds. While adding images or even thinking about video, remember load speeds.

2. Do not play music on your home page automatically. This has been mentioned by many books and design sites, yet still designers do it. For one most find it annoying when it starts, and two it can alienate people from your site because in various likes in music. I you must have music for example, a band site, give the user an option to turn it off, or have volume controls.

3. Easy to use navigation. This one is pretty important. Users want to know where they are and how to easily get to where they want to get. Make the site map of your site easy to read, and make the structure easy to follow. Also the navigation bar should be easy to read and consistent throughout your site or application.

4. Colors of text vs. background should be pleasing. There are always those sites that use red text over bright blue or something similar. Then you try to read the first line of text and go cross-eyed. Black texts on a white background is preferred, but if you need to use different colors, make sure the text is easily read, and does not strain the eyes.

5. Content. Write content for your site that is appropriate. Do not try to combine 3 businesses into one site as users will get confused as to what they are looking at. For example, if your site is about skiing in Aspen, do not try to run an online poker page from the same site. Domains and hosting is cheap enough to separate your business ventures.

6. Spelling goes a long way. Make sure you run your content through a spell-checker. I find even large corporate sites have very easy to fix spelling errors. Simple spelling errors put off users. If you can not spell right, it shows that a user cannot trust you with a product or service either.

Web Design31 Oct 2007 02:54 pm

I am making a list of mistakes in web design. I know, there has been tons of these lists on other sites. But this list is different, it also takes into account newer technologies that have been used over the last few years. So here we go:

1. Write for web not print. In the text of your sites make short easy to read paragraphs. You are, most of the time, writing to explain a product or service, not write a novel. If the first thing a user comes up against is a wall of text, more than likely they will leave.

2. Write articles on the web on one page. This is a common complaint I have heard lately from people. I have never done it but have seen many people split articles into many pages for no real reason. Make pages contain information people are looking for without looking for a next button. They would rather continue scrolling than click to 5 different pages for the same article.

3.With the big hype of AJAX, don’t overdo it. Make sure you have a purpose for using it. Google maps have a valid reason for updating maps, but to go to a site filled with cheesy dropdowns and auto completes for no known reason is bad design.

4. Do not overuse animations such as Flash. These technologies serve specific purposes. Flash is great for interactive elements in a site such as video or animation, but search engines do not know what content is in a .swf file so cannot index it. Plus people do not like splash screens, they want the website.

5. Do not use popups on your site. With the huge push on internet security, users mostly view popups as spyware or annoying ads. If you must use popups, make your user aware by spelling it out on your site that you use them. This will make them more aware that you use them and that they should expect content from your site to be displayed using them.

6. When linking, do not use the target of _blank. Most users are still using non-tabbed browsers. Users can find this obtrusive and feel like your site is opening windows for them.

That is just a few tips on design, I’ll give you six more in a few days. Stay tuned.

Web Design& Web Development22 Jun 2007 12:52 pm

Like most other software developers and web designers we have trouble with some clients. I really feel the problem to this is a client does not understand the work and effort that goes into a site or software package. If a client saw what was involved in the Software Development Life Cycle and designing a functional database or design they may think about things a little differently. 

Clients should think of software or a site like a house (Read this for a good laugh). Once a foundation is down, any drastic changes are costly. With a house, if you decide to add a room half way through, you have to get plans re-approved for loads and building codes, drastic changed need done, and the extra labor in building the extra piece. The same is true with development. If you have a database and software halfway through being built, and a client requests a change in structure, there can be many effects in database integrity, other pages or forms affected, and the extra work to build.

This shows that even small changes to software can affect many aspects. Without fail, this also pushes out deadlines and increases costs as a lot of work needs to be done to make the so called “easy change”.   Please keep these in mind when working with a developer or designer. They will be happy, it will cost you less, and the chance of the project getting done on time will increase.

Web Design& Web Development26 Apr 2007 09:53 am

After looking over the videos and information on the Adobe site the other day, a few things popped uot at me as great features in the new Dreamweaver CS3. Just to list my favorites here: 

1. Spry ajax - This looks very cool. Instead of extensive hand coding JavaScript for very simple ajax functionality, this allows you to create almost a node/child-node ajax function with just selecting an XML file and setting the data source of a field. This looks easy to do and quick. I can already think of a few things I am going to try it out on. 

2. Pre-Built CSS Layouts - Dreamweaver CS3 comes with an array of CSS templates. Not completed templates with text or anything, just CSS shells to start with. This should save a lot of time when starting pages. 

3. WYSIWYG and W3C? Dreamweaver 8 use the Internet Explorer 6 plug-in for its design view, this was not the most standards compliant and created sloppy/bloated HTML. Now it is based on standards set by W3C. This should make browser compatibility much easier to deal with. 

4. Integration with Photoshop - When Adobe acquired Macromedia; this was the first thing that popped into my head. I love Photoshop far better than Fireworks for image editing. More filters, better tools, just a better product. Fireworks has its uses for buttons and such, but to have Dreamweaver integrated with both will be very nice. 

There it is, some of the things I am looking forward to when I get a copy of Dreamweaver CS3. I hope to get it at the beginning of May. Then I will make sure and post a review for everyone to see if it has lived up to the hype.   

Web Design& Web Development10 Apr 2007 03:24 pm

After Adobe bought Macromedia there were a few questions out there. A few I had (as well of a few other designers and developers), were:  

1. What would Adobe do with Fireworks? 

2. How would future versions of Dreamweaver work with other image editors, especially Photoshop? 

3. Would Adobe try to keep GoLive as a web editing tool? More importantly would they try to re-vamp Dreamweaver to keep the name and go for more of the GoLive interface? Or get rid of GoLive altogether?  (more…)

SEO& Web Design28 Feb 2007 05:40 pm

Just found the Yahoo Live Badge. I don’t have too much to say about this except, who in their right mind would put something like this on a public professional site. It looks cheap, and I don’t think visitors to your site need to know how many back links you have. Wonder how many developer hours were used in building and testing a worthless tool like this?