If you have read my earlier posts (here and here), you may know that for two days I was working on making it possible to show a specific SharePoint restricted tag in a blog post hosted in SharePoint Blog application (in this case it was the <embed> tag that is often used for lots of things, but mostly for Flash video from YouTube).  In addition I wanted to make the process almost “transparent” in WLW (Windows Live Writer), so I took the opportunity to learn how to make a plug-in for WLW.

Well now that I had gotten it to work using a manual process, I started to think about how to achieve the same thing for other SharePoint restricted tags, such as <script> <object> <iframe>, etc (and please don’t tell me iframes are evil, I don’t want to hear it), and I had a whole idea for plug-ins for my plug-in, specialized approach, etc when I went to bed.  So this morning, my dog Xander, who felt that 6am was too long to wait to be fed (which is completely normal), woke me up and as I tried desperately to ignore him, I started thinking about this problem.  I realised that plug-ins for a plug-in was just too ridiculous to continue.  Instead why don’t I just have my plug-in allow the user to specify a list of tags that are restricted, and it will convert them over to the div framework (with attributes encoded into the “title” attribute, the original tag name encoded in class).

So this post represents my attempts / success in getting that change put into place.