I am surprised by how few companies employ the little trick of using the WYSIWYG editor in their CMS to semantically tag rich text fields. The general idea is that you overload the WYSIWYG CSS support by using the CSS classes with semantically meaningful names.

Here is an example. Lets say you are publishing a business journal and you write a lot about companies and regulatory agencies. You might have a sentence like

Apparently, following an investigation into the hacking of several dozen customer accounts, the SEC found LPL negligent.

source

The terms “SEC” and “LPL” are italicized in compliance with your style guide. To satisfy the style guide, your reporter probably just highlights the text and clicks the italics button. But, what if your style guide changes to say that company names are bolded and your regulatory agencies are in red text? Using style classes would give you much greater flexibility than “em” and “strong” tags. Most WYSIWYG editors can be configured to have a drop down list of style classes. When a user highlights the text and selects the class, the WYSIWYG editor writes it as a span tag with that class:

<span class="classname">LPL</span>

Now what should you name your classes? Here is the trick. Rather than call them “italics” or “bold” or “red,” give them names to indicate the meaning of the text that you are styling: such as “company” and “regulator.” In addition to giving more flexibility in styling, you will be able to do some really interesting things with your content. For example:

• With a very simple XSL template you can have your rendering template put a list of mentioned companies and agencies on the page.
• You could extend the logic of your CMS to automatically create metadata about the article to help your search engine figure out that your article is about Apple computers rather than Motts Brand Apple Juice.
• You could have your rendering templates insert the stock symbol of the company or create a link to their ticker page.

The possibilities are really endless when your programming logic has access to the meaning of your content.

Using a WYSIWYG editor to do simple semantic tagging is not the only way to add meaning to your content. You can have your authors write in an XML editor. You can use a text mining engine match words against a centrally managed controlled vocabulary. However, I have found that this approach is the least expensive, most practical way to get started. They want to have their article look nice. This approach captures that intent and, with no additional effort, creates additional value that your author (at first) is less aware of. Once your content starts to have semantic tagging and your technology starts to leverage it, your authors will probably start to see the benefits and really get excited about the possibilities.

Related posts:

1. The 6 Million Dollar WYSIWYG Editor Lisa Welchman has a great post on CMS Watch Trend...
2. WYSIWYG Editors WYSIWYG editors are a key feature in most CMS products:...
3. Hippo CMS 7’s New Content Type Editor Arjé Cahn posted a short video demonstrating the Hippo CMS...
4. Good Article on Web Application Security Vulnerabilities The PHP programming language has historically gotten a bad rap...
5. Making developer docs more accessible Uploaded with plasq’s Skitch! What do developers hate more than...

This entry was posted by Seth Gottlieb on Thursday, October 2nd, 2008 at 8:44 am and is filed under Web2.0, development, tricks, usability. You can leave a response, or trackback from your own site.