- HyperText Markup Language
- where markup lang = markup tags
- diff versions 1991 (HTML) - present (HTML5)
- HTML docs described by HTML tags (keywords)
- <start/opening tag> </end/closing tag>
- where ea. tag = diff content
- <!DOCTYPE> = declaration of document type in HTML5
- all HTML docs must start w/ such a declaration
- helps display web page correctly
- <start/opening tag> element content </end/closing tag>
- <html> web document </html>
- <body> visible content/doc body </body>
- nested elements
- <h1> heading </h1>
- can go up to <h6>
- <h1>: main ---> <h6>: least important
- <p> paragraph </p>
- <a href="URL"> link </a>
- <img src="URL"> : imgs, where attributes
- src = source file
- alt = alternative text
- width and height = size
- attributes in elements
- addt'l info
- always specified in start tag
- e.g. <img src="URL">
- lang attribute
- <html lang="en-US">
- title attribute
- <p title="About this blog"></p>
- href attribute
- <a href="URL">link</a>
- style attribute
- style="property: value", where
- property and value = CSS
- <body style="background-color:blue">
- <p style="font-size:20px">
- <div> = block level element
- container for other elements, where
- <style> .cities {color: green; margin:25px;} </style>
- in body: <div class="cities">content</div>
- can be used for multiple column layout
- <span> = inline element
- container for text, where
- <style> span.blue {color: blue;} </style>
- in body: <span class="blue">Blergh</span>
3. Pratter, F. E. (2011). Chapter 2, Introduction to HTML. In Web Development with SAS by Example, 3rd ed., pp. 15-30.
- W3C = standards for HTML; XHTML pref (CSS)
- diff b/w HTML and XHTML
- HTML = SGML-based; XHTML = XML-based
- margin for error in HTML too broad
- XHTML more rigorous, precise
- XHTML also easier to maintain
- all docs encoded in XHTML must
- be coded in lowercase
- have proper tags
- nest correctly
- enclose attributes in quotes
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.
- report on CMS for 30 web-based research guides at Georgia State U.
- CMS design: MySQL & ASP
- lack of standard for lib guides, so ea. liaison w/ diff idea (no., content)
- tech and admin issues
- min. sec. w/ FrontPage implemented system
- published content quickly
- but sub-web accidentally deleted
- solution: w/ 1st web dev librarian
- +++ security
- MySQL to manage dbs, journals, special collections
- survey content guides
CMS in the library
- reduce "gatekeeper" approach
- allow more library staff w/ diverse levels of tech skills to contribute
- use ASP-generated style sheets
- common style, navigational consistency
- accommodate increasing volume and complexity of content
- flexibility in db-driven apps
- diff CMS environments
- commercial v. open source v. in-house
- keep in mind end user (GSU community)
No comments:
Post a Comment