Friday, October 10, 2008

Reading notes- week 8

Reading notes week 8:
-HTML Tutorial:
In this tutorial, it starts by simply explaining what HTML means (Hyper Text Markup language) From here it has you do a simple exercise in Notepad, in which you write in HTML language, save the document, then open this same document in your internet browser. By doing this I learned the very very basics of how a webpage is made. I found this activity to be simple, yet it gave me an understanding of something I never knew how to do before, it also made me wonder how much more complex WebPages are made.
-HTML Cheat Sheet:
This article was a collection of HTML “Cheats”, or commonly used html markups that allow you to do many things with your webpage, including change colors, make links, change the size or style of the text, and make menus. This site answered a few questions I had from the previous article, by giving me the shortcuts to make slightly more complicated web-pages.
-CSS Tutorial:
CSS stands for Cascading Style Sheets. Styles are how an HTML page is displayed, and multiple styles can cascade into one. I was honestly not totally sure what all this meant at the end of the page, except that using this can save time and allow you to make multiple pages at once in the same style. I am still a little confused as to how to really use this and what it really means.
-Beyond HTML: Goans, Leach and Vogel
This article starts by explaining that the Georgia State University library had used a Front-Page web site to make library subject guides. There were very few guidelines, and there were 15 people working on this project. Because of the diversity of the people involved, and the lack of structure, the WebPages ended up looking very different, and being very hard to use from one to the next. There needed to be a way that course materials, including books, databases, journals and websites could be accessed. They thought that they should use a CMS, or content management system, instead of allowing those making the pages to simply use their own html. Some libraries use CMS to make updating the pages easier, while others use it to control a situation like Georgia State had: with too many differences from contributors. CMS systems have to be created, whether through open source or purchased software, or by having someone in the library create it. In the end, the transfer to CMS was smooth, and helped to organize the library.

2 comments:

RAlessandria said...

I was happy to see you were also a bit unclear on the CSS topic and how it's used. I got the idea from the tutuorial that it was almost the same as HTML, but more like add on's, basically, just different "commands" one could use.

Jenelle said...

From all the blogs and blog comments I am reading, I think everyone seems a little confused on the CSS. I thought it was an "addition" to HTML, but now I'm not sure if I am just confusing myself even more (and now probably you too). Hopefully class will clear up all the confusion with HTML and CSS.