[WEB4LIB] Learning curve: HTML or WYSIWYG

[Mcclendon, Sunny]

I agree with you. 
We have a WYSIWYG for the editors to do their content changes, but we're not committed to any one application.  (Currently, we're using HomeSite.) I suggest our editors take an HTML class before taking on pages.  The support materials I have tell them how to do simple functions in HTML AND HomeSite. They can chose which to use.  When we have workshops I do both, depending on what the user wants. 

For us, it works best to use both. WYSIWYG is easier for them to do, say, annotations. Whereas it's easier to do an anchor in HTML. A good editor will let you do both in the same application.

In my limited experience, there are always pages that can't be opened in an editor. It's nice to have that HTML to fall back on. 

Hope that helps,
Sunny


Sunny McClendon
CNN Library WebKeeper/Reference Librarian
(404) 827 2835

-----Original Message-----
From: Michelle Rempel [mailto:mrempel at peacelibrarysystem.ab.ca]
Sent: Monday, October 29, 2001 11:31 AM
To: Multiple recipients of list
Subject: [WEB4LIB] Learning curve: HTML or WYSIWYG


Morning!

I'm likely going to be doing a day session with some of the librarians in 
our region on basic web design and HTML.  I'm a purist and prefer to teach 
HTML as I think that the difficulty level is less than trying to teach a 
WYSIWYG.  Also, the librarians would be better equipped to sort out any 
HTML problems later.  Finding a software product that they would all want 
to purchase and possibly arranging licensing is a concern as well.

I've explained my point to my boss, but a more technologically savvy 
librarian is asking about WYSIWYGs.  What opinions do you have?  From a 
learning and training standpoint, what have you found to be best?  Would a 
WYSIWYG encourage librarians to create and update a website more than 
HTML?  I should mention that I've done the HTML route before and found that 
most pick up on it quickly.

Thanks!

Michelle Rempel
Peace Library System



*********************************************************************
Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
*********************************************************************