Do not use
text-align:justify for reading text. Justified text looks terrible with huge gaps between words.
Do not use
text-transform:uppercase for reading text. Uppercased text harder to read than not uppercased.
Do not use
font-family:serif for reading text. Serif font is harder to read than Sans-serif.
Do not use small
font-size for reading text. Small font is hard to read.
Make every article as short as posible. The less the article is - the more people will read it. Articles should be short and informative because people does not like long and not informative articles because short and informative articles better then long and not informative ones because long articles could be more shorter and not informative articles could be more informative and also people does not like long sentances which could be splitted into shorter ones.
Read content before you post it into web. Gogoel does not saerch perfeclty contetn with mistakse.
Do not mix content and ads. Always Coca-Cola. Label ads as "ads".
What is interesting for you could not be interested for others. Last week was very hot in my town.
Delete old and not needed information - do not leave garbage in the web. Download Windows 2000, it's fast and secure.
All navigation elements should be recognized without hovering mouse over them.
All links should be underlined and non-links shouldn't be underline. Links should be with different color and link's color shouldn't be used somewhere else. User should understand where is the link and where is not without hovering the mouse over it. Dashed underline means that the link is interactive and after click on it user will see something without reloading the page. For interactive elements span can be used instead of link.
Write text for people and not for Google. People don't like when they searched information about ferrari and they came to page, which was written to trap the visitors from Google and to sell them ferrari.
Interactivity and not animation. Animation does not help to read content.
Do not play sound on pages. Most users already listen to their music in their players.
Do not fool your users. Users like the truth.
Users rarely scroll homepage. But they scroll other pages.
If you did something then try to test it by yourself and you will see the list of first bugs.
Main principles of everything (in this sequence):
- visual design
Main principles in coding (in this sequence):
- DRY (don't repeat yourself)
- KISS (keep it simple, stupid)
- loose coupling
- remove not needed
- less code - better (less errors, easier support, cleaner API)
- recognizible UI elements (inputs looks like inputs and so on)
- unchangable navigation (position, order and look of the navigation is same on every page)
It is better to have the color of the visited links different than the non-visited links. User actually believes on/requires Recognition rather than recall : one of the Human Computer Interaction principle.
The theory of visual hierarchy is the idea that the most important element is the most prominent.
Good thing is the balance between minimalism, usability and functionality.
90% of users does not change default settings. So product should work out of box with default configurations.
Only 1% of users create something (create content, write comments, send feedbacks etc).
Decisions not Options (c) WordPress
Perfect options chooser for user:
- ( ) awesome
- (*) extremely awesome
Do not use minified version of scripts and styles, because it does not worth it. You will lose few kilobytes with not minified files only with first page load, but you will save much time on developing.
Abstraction captures only those details about an object that are relevant to the current perspective.
Composition is better that inheritance.
The Zen of Python
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!