Favicons

     Favicons are small square graphics, ranging from 17 x 17 px to 28 x 28 px in preferred size, that give a graphical representation of the site the user is visiting. The favicon appear in the address bar on the left. The main reason websites use favicons is to improve their user's experience. Favicons, by giving a graphical representation of their site, make it easy for the user to recognize the site they're on while they might be switching tabs or scrolling through a list of bookmarks. A favicon adds to a website's uniqueness by making it stand out and different from other sites through use of graphics.
     To create a favicon you need a favicon generator, a software where you can design your favicon. Sites may be owned by businesses that have logos to represent themselves but when it comes to favicons simply converting the image file for the logo into a .ico (file format that favicons use) may not be optimal. Favicons have a limited size, biggest size being 28 x 28 px, and regular image files of logos far exceed the max size of favicons, so the logo will be very blurry. This is why a favicon should be designed from scratch; first on grid paper and then being transferred to a software that provides a grid and color options. Once the favicon is saved as an .ico it is inserted into the code of a website through the <link> tag and will appear in the address bar if done properly.

Comments

Post a Comment

Popular posts from this blog

Favorite Teacher Project Reflection

Image
     The second project for DD this year was about creating a website in appreciation of your favorite teacher. This project was a lot like the our first project except it revolved around a teacher and not movies, otherwise, it required all the same skills we learned in the first project. Just like in the first project, the beginning steps were not in the computer, rather, they were on paper. After deciding which teacher to make the site about (Ms. Sakhno), I begun by creating wireframes both of the website itself and how the folders for the project would be organized. My website wireframe consisted of 4 pages all with relative links that took the user to all the other pages from any single page. There was a home page, which explained the purpose of the site and why the teacher I chose was my favorite, a biography page, which described the teacher's life up until now, a subject page, which discussed the subject the teacher taught, a trivia page, which displayed an infographic abo
Read more

Lab 20 Reflection

Image
     Lab 20 incorporated many of the things we learned from Lab 18, with the functionality holding many similarities. In Lab 20 we were to create a webpage that compares 2 numbers, x and y. The user is supposed to be able to see if x is greater than y, y is greater than x, x and y are equal, etc. The interface is similar to Lab 18; there is an area to input two values, there is an area with many buttons that lead to a specific outcome, and there is an area to view what the outcome is. Unlike Lab 18, the buttons don't perform an arithmetic operation on the 2 values but check if a certain comparison between the 2 values is true or false. The result area, instead of displaying the result of an arithmetic operation done on 2 numbers, displays if a certain comparison between 2 values is true or false, essentially displaying the result of clicking the now comparison buttons.      I started Lab 20 just like I started Lab 19, by duplicating the code for Lab 18. There was not much to chan
Read more