Isn't this a case for a tight little client side applet? I looked a couple of years ago for a basic, configurable WYSIWYG applet that I could just drop into a "make your own page" type of page, but didn't come up with much. (and then went out and bought a couple of java books with the intention of making one myself and they remain pretty much unopened) But what I had in mind was an applet that would give the user a WYSIWYG type editable content area, with maybe a simple toolbar with the styles I wanted to make available. It could tie into a schema or similar to define that toolbar (for full reuseability), and allow the usual keyboard shortcuts for bold, italic etc. if it was light enough, you could have multiple instances for each editable area on the page. Ideally the applet would simply write the html to a hidden field, so nothing new would be required on the backend, it's just a regular post with html content. anyhow I post something like this about every year just in case someone's come across something - it'd be ideal to present a non-IE solution for html-free, client-updatable pages, blogs etc.. Sam > > well, i still suspect the "content" area at the address above was entered > using some sort of editor like what we're discussing. i've seen *far* too > much of the sort of html it produces to not suspect the bit i pasted here. etc..