{"id":258,"date":"2011-10-31T21:22:04","date_gmt":"2011-10-31T19:22:04","guid":{"rendered":"https:\/\/fucinaweb.com\/en\/?p=258"},"modified":"2011-10-31T21:32:52","modified_gmt":"2011-10-31T19:32:52","slug":"everything-has-its-own-name","status":"publish","type":"post","link":"https:\/\/fucinaweb.com\/en\/everything-has-its-own-name\/","title":{"rendered":"Everything has its own name"},"content":{"rendered":"

I went to the client’s office with our art director and now he is ready to show various layouts to illustrate the project.\u00a0He made some minor changes last night so we could not see them together. He opens the laptop and double-click\u00a0cool.psd.<\/em><\/p>\n

The colleague who develops the\u00a0frontend<\/em>\u00a0sent an email containing the latest corrections requested by the company that will address the integration.\u00a0Once unzipped the files, on the desktop appears the folder named\u00a0WTF.<\/em><\/p>\n

These are only two examples, but I could easily go on for hours and hours and never repeat myself.\u00a0Ok_bis_def.zip, another_one.psd, today_i_lack_ideas.png:<\/em>\u00a0I have a whole literature of meaningless and embarrassing names.<\/p>\n

Tired of spending days to rename the files and send them to different actors (if I still have time) I have developed a simple system of nomenclature which I try to apply and enforce.<\/p>\n

The advice is to start as early as the wireframing phase, to continue during the graphic design up to the development of HTML pages.\u00a0Each wireframe should properly be named before sending it to the art director, who is usually happy to keep the creativity for other tasks.<\/p>\n

I’ve tried over the years different types of classifications, but the one that ended up being more effective is the result of a compromise between the highly informative content and ease of application of the rule.<\/p>\n

A typical example of the nomenclature would be as follows:<\/p>\n