Journal #1
Robbins, J. N. (2012). Learning web design: A beginner's guide to HTML, CSS, Javascript, and web graphics. Sebastopol, CA: O'Reilly.
Summary:
Chapter one focuses on where someone would start when they get into web design. Some people do it for a career while others make it into a hobby. There's a lot that web designer has to learn. They need to be able to design based off of the idea or instructions that they have. It has to be able to run smooth and that means that the web designer has to understand several programing languages. A web designer is not expected to learn everything at once but they will eventually learn everything that they are going to need to know. New software is always coming out which sometimes replaces the old.
Chapter two focuses on how the web works. It is interesting that a simple change in the HTML can make a huge difference in the way the page looks like for users. The style of a page can drastically change bass on what you tell it to do. For me it is amazing that their are so many different commands you can give to the text that is displayed.
Chapter three focuses on concepts web designers need to know. The amount of different devices that people are using to access the internet is increasing. With the use of so many different devices there is a standard that are followed so that content is compatible.even if the screen is too small to read the text the user can zoom in on what they are looking at. The web is accessible for people with disabilities.
Q1. Why should we learn HTML?
A1. It is possible to make simple websites with HTML documents and images. You are not programing when you use HTML it is just organizing the way information is looks at on a page. It is a good idea to learn how HTML works before you start working with CSS or JavaScript.
Q2. Why do you need to run the same webpage on different devices?
A2. No two devices are the same. A computer screen is going to be larger than a cellphone screen. The way a user views and interacts with information is going to be different. Also all web browsers work differently. Some browsers do not support additional plugins that can be added. In some cases data will not be accessible to users using certain devices or browsers. That is why it is important to test what you make on a wide variety of devices to make sure it is accessible to as many users as possible.
Hey Joshua, i agree with your last answer and find the question pretty obvious, but very crucial. Seeing many different technologies that allow web capabilities means that they must be able to run on those devices. Things such as screens on phones, tablets, or even digital refrigerators need to be able to access those pages with east, and must always be double checked/ tested!
ReplyDeleteCheers!
As I started to read your summary for chapter one and you stated that a web designer had a lot to learn, my heart literally dropped. I thought to myself, I can not learn all of this in one quarter. However, as I kept reading, you stated that a web designer will learn all of the necessary information over time. This is a relief to me because I am coming in as a beginner. This allows me to soak up all of the information I can in the next eleven weeks, but not freak out if I can not learn everything.
ReplyDeleteCompatibility is definitely a concern of mine as a novice web designer. Since there are so many platforms, screen sizes, and device types available today, it is daunting to consider creating web pages that will operate smoothly, universally. Considering the extra work involved got me wondering if that is why certain software and apps are exclusive to certain platforms/operating systems. At what point does the time and cost of creating universally compatible products outweigh the benefit?
ReplyDeleteDeveloping various page formats for various devices was quite interesting, and the thought is rather daunting. I can only hope that a simpler, more convenient way to address this issue is on the horizon. Of course, by then there may be, as yet, unseen devices that that will have emerged.
ReplyDelete