1) W3schools HTML Tutorial: http://www.w3schools.com/HTML/
This information provided a very useful tutorial and quiz in terms of setting up ones own website. I found the examples to be helpful in decipering the various approaches one can take in setting up a website. Hopefully, we will have a chance to do this in the near future.
2) HTML Cheatsheet http://www.webmonkey.com/reference/HTML_Cheatsheet/
When it comes to setting up a website, these tags should be helpful. I think they will have more meaning once I apply them to what I am doing at that particular point. I am wondering if professional web designers rely on these tags, or is it simply for amateurs?
3) W3 School Cascading Style Sheet Tutorial: http://www.w3schools.com/css/
Wow, I did not know that one can lay out many webpages at once. I wonder if one wants to make changes to a webpage, whether it would be dormant, or will the original be the default page prior to the revisions?
4) Goans, D., Leach, G., & Vogel, T. M. (2006). Beyond HTML: Developing and re-imagining library web guides in a content management system. Library Hi Tech, 24(1), 29-53.
I did not understand why some libraries want to limit staff from contributing to the website. Supposedly this is to limit the "gatekeeper" effect. Perhaps libraries do not want staff that is not tech savy for this venture? Or, is it out of lack trust toward the staff? Either way, it is kind of scary.
Adam Brody
I agree, I do not understand why everyone can't work together to create a website. If the website is for multiple departments, then why would they not want those departments to be a part of the development team? I wonder if it is a lack of trust issue...? If they allowed the different departments and staff to work with them in the creation of the website, then it would go up that much quicker. There might be some lag-time to smooth out some ruffled feathers between departments but the time between "talk" and "live" would be faster and the end result would be better.
ReplyDeleteI also enjoyed the tutorial. HTML is very complicated... there are numerous books about it! So tutorials like this are very helpful in understanding complicated concepts like this.
ReplyDeleteI think I might be able to answer your questions. The objective of any cheat-sheet, or at least from my personal experiences, is to serve as quick reminders to those better acquainted with the field. They could always forget certain details and such sources as those can help them refresh their memory in an instant. As for the CSS, as long as the web-creators have alternatives available that will allow them to simplify their work and save more on resources, they will definitely plan on incorporating the changes, and I am sure they will keep the original versions handy as a back-up in case the plan fails. And for your concerns about the CMS article, the problem is rooted upon fear of change. Because the staff is dealing with a field in which they have no familiarity, they tend to believe what they do not know is simply going to hurt them down the road. That is why CMS was invented in the first place to help establish a connection, thus allowing the collaborative efforts to be more successful and prosperous so as to benefit both the staff and patrons.
ReplyDeleteI did not think the library wanted to limit staff contributions, but to rather devise a method to better organize what is contributed. I think having a large amount of librarians contributing guides in their own methods really just hinders the research of patrons because there is so much they have to weed through. There use of a content management system has undoubtedly benefited their patrons that utilize the library website.
ReplyDeleteI agree with Gemma in that I don't think they are trying to limit the staff's knowledge of HTML. I thought that CMS systems allowed for an easier and more uniform way of presenting information on a libraries website. Although it does allow librarians to be less knowledgeable about HTML, the staff has to be familiar with how to use the content management systems so they aren't using staff that isn't "tech savvy."
ReplyDeleteI asked the same question about the HTML cheatsheet, about whether professionals rely on them. It seems like a lot to remember, but I wonder if it can be learned much like a language can. Probably if you used it quite often. But I know I find a sheet like this quite useful.
ReplyDeleteKristen Huth
I also found the tutorials helpful. I'm pretty sure that we will get the opportunity in our next assignment to author our own webpage. I'm looking forward to actually putting into practice what we learned from this week's readings too!
ReplyDeleteAdam, thanks for always having a clear and concise posting on the readings. I am so new at all this stuff I am thankful for the 'cheat sheet', too.
ReplyDelete