|
Web Design Student |
||||
|
Learning response User Knowledge Design Knowledge Project Development Knowledge Tutoring Knowledge Overall I really enjoyed this class. I learned a lot and now that I have a taste of web design - I want to learn more. Hands On Training Tutorial Responses |
|||
Client Case Development |
In browsing through a wide variety of Election-based web-sites, I found that many of them were layed out with a very strong emphasis on information rather than entertainment. Most of them had a great organization to the layout with multiple little sections describing a larger article they linked to - much like a newspaper. Considering this I also found that a lot of them were reading sites rather than browsing sites. You could browse to find something to read, but in the end you would be reading. I also found that a lot of the information was static rather than dynamic. But I feel that all these decisions are best for maintaining a professional appearance. Some of the sites I looked at include: Facebook: Hillary - http://millikin.facebook.com/person.php?id=2290827757 Site with great profiles on all the candidates: New York Times Election Guide Mitt Romney Official Site: Barack Obama's Official Site: Hillary Clinton Official Site: Best of Rudy Giuliani, MIke Huckabee, Mitt Romney, polls; news, in real time Giuliani's Official Site: |
|||
Chapter 10 |
missing |
|||
Chapter 8 |
In this Chapter we learned how to: I learned a lot of things from this chapter that I didn't already know so this will be very beneficial to me as I continue to create web pages in this class. |
|||
Web Design |
Nicole Falletti's Bookmarks Page Organization: Navigation: The only suggestion I have is possible adding a bit of space between categories so that they separate out a little more. Putting links back to the top might be nice, but certainly aren't necessary since the length of the page is fairly short. http://students.millikin.edu/~nfaletti/AdoptingPetLinks.html |
|||
resume critique |
Good Resume I really liked this sample resume. It's very simple, crisp, and organized. The person's name is right at the top where it's easily noticeable with all her contact information at the top. It's also good to see that her name isn't so large so as to overpower the the rest of the text on the page. Each section is separated using a gray background behind the header, and the header text is a larger bold serif font. The text below each section uses a san-serif and is smaller. It's also nice that the background has a little color to it because it keeps it from being bland and dull. Bad Resume The first thing I noticed when I viewed the page is that there is no indication whose resume we are viewing. I kind of like the idea of listing highlights and then dividing the page up into sections. I always have had a rough time fitting everything I wanted to onto a single page so this layout would allow you to include a lot more information. Each section is fairly well-organized, but a potential employer might not be interested in reading all that is written there. He should probably try using more lists rather than lengthy paragraphs. He's consistent with his font use but it would be nice if there was a little more separation between headers and subheads/body text. So the changes he needs to make are: Clearly make his name visible on every page, better organization, shift from paragraphs to lists, more concise, and develop a text hierarchy. |
|||
Chapter 7 |
Chapter 7: Typography This was a quick and easy chapter but very beneficial. |
|||
Chapter 6 |
This chapter is all about Cascading Style Sheets (CSS) and works a lot with coding. I was really excited about that because I was really hoping to learn a bit more about how to use code. At the beginning it shows you how to go into your page properties and set up the defaults for the page so that you can specify things like the color of the background/font, the font type, the size of the font, how links will appear, the margins for the page, etc... All of those things can be set and changed by clicking on the page properties button in the property inspector window. The next section showed me that I can export my CSS style sheet and it will create it's own page of code that I can then link to any other page in order to maintain consistency between pages. There is also a nice little diagram on page 125 that explains what everything in the styles panel represents and does. After learning how to export a style sheet, we learn how to create our own CSS rules all by using the styles panel. The first window to pop up requests that you tell the program what you are wanting to be effected, like all paragraphs (p) or a header (h1). Once this information has been entered, you then move on to specify how you want it to be effected. You can specify the font type, color, size and margins; the background color; the way text is aligned in a block;how the words are spaced; the type of border you want; etc. If you know what you're doing, this method seems really easy and would make laying out your own unique style sheet fairly simple. I also saw how you can select a rule within the style panel and add properties to it or change pre-existing properties all within the style panel. The fourth section seemed a bit more complex. It seems to me that the ID selectors allow you to be very specific to a particular area. This section had us create individual rules for each cell of the table in the page's layout. We ctrl clicked on the little tags below our design window and chose to set ID. I had no problem doing what the book asked, but I would like to understand a little better about what exactly I was doing in this section. The same applies to sections 5 and 6 involving the classes and pseudo-classes. I had no problem doing them, but if you asked my why I was doing it I wouldn't be able to give you an answer. So far - I've found this chapter to be the most educational though. |
|||
A Favorite Website: |
Web Address: Site About: I like both of these sites because they are interactive. The jkrowling site is more animated I think in that objects actually move and link to other pages where they are more interactive/animated things. I like the vikmuniz site because the main page is interactive. The linked pages aren't so much - but the artwork is awesome! "Site Analysis" I found this website while browsing the other night and found it to be rather unique and very interesting. The introductory page is has a nice orientation. The animation is engaging showing people various people and locations and the type of house that suits them. This set up peaks a viewers interest and encourages them to continue to the rest of the site. The one downside to the main page is that I found a bit of difficulty finding the little arrow that allows a person to proceed into the site. (It’s at the bottom right hand side of the page.) Once you get past the intro page the site is set up very well and is user-friendly. You can learn about Frank Lloyd Wright and architecture, browse through a gallery, or design a house based on a client of your choice’s needs. Once you select a client, little boxes pop up providing advice and facts on how a real architect would proceed. You are allowed to make decisions regarding the shape of a house, height of the walls, and interior layout of the building. Advice boxes continue to appear as you progress through the steps of construction. If you change your mind about a decision there are several ways to back up and change your decision. Overall I found the site to be easy to navigate through and clear indications for where to go next. One of things I love about this site is that it is designed to be a learning device. The site is constantly providing facts and information teaching the person about architects, Frank Lloyd Wright, and how to create a building that fits a client’s needs. The layout was appealing and maintained the same format throughout. Overall, I found this website to be fantastic with regards to its orientation, navigation, and content quality. |
|||
Chapter 5 |
This chapter covered a lot of new information. Some of it included: I found this section to answer a lot of my questions about how files actually get linked together. I have a feeling I may need to refer back to this chapter later to refresh my memory. |
|||
Chapter 4 |
This chapter was quick and easy. Several of the ideas were already performed in Chapter 3 so it was a nice refresher for placing images into a document. The chapter also covered: I also learned from Prof. Brooks that I need to make sure my Dreamweaver page is set for standard mode and not layout. When my document was in layout mode I couldn't insert images into my file. Standard mode gives me more flexibility to create my web page. |
|||
Chapter 3 |
This chapter was very quick and easy to go through. You showed us a lot of the things we needed to do in this Exercise yesterday. I found the reading on site root and document relative links interesting. Document relative link is basically a file - the computer just finds the file with the same name. Although you already showed us, it was good to go over myself how to load a folder into the files panel. From there you can do everything from opening a page or file to pulling a file into an already open page. |
|||
Chapters 1 & 2 |
1. Is CSS coding placed at the beginning of a coded document (before the html, xhtml, or xml begins)? |
|||
|
© 2007 Randy Brooks, Millikin University • Last Updated December 15, 2007 |
||||