I’m now using John Papa’s Footer WLW (1.1 CTP) and Scott’s Profanity Checker Plugins…

JohnPapa.net - DZone PlugIn for Windows Live Writer

“I had a good response to my DotNetKicks plugin for Windows Live Writer. One of the requests that came along was to write a Live Writer plugin for DZone, too. DZone is another one of the aggregating sites … they state on their site “fresh links for developers”.

…

If you just want to use this plugin, simply download the dll and drop it in your Live Writer plugin folder.I only added a single option: the style of the link. The style can either be tall or wide.

This is Tall   and this is Wide

…”

CodeProject - Windows Live Writer PlugIn for DotNetKicks

“Windows Live Writer PlugIn for DotNetKicks. Generates a KickIt image and link to embed in a post.

…”

InsertableContentSource - New Writer Plugins Using The New SDK

“…

This plugin was something I discussed with the Writer team as a good example of the PublishNotificationHook base class for checking the contents of a post and cancelling the publish if certain criteria are met. So this allows you to configure what words would cancel a blog post from being published, and just to make sure they can’t easily be changed (say by a child), you have to password protect them

…”

This is until I can get moving on my own plugins… ;)

The coolest things about these plugins? Their authors have released the source for them. Kudo's to them!

Remember, these require the new Windows Live Writer CTP…

 

Note to self:
Make a suggestion for a future improvement that lets the user turn on/off these kind of footer plugins per post, at post edit time. For example, if I'm writing a personal post, it seems silly to have the DNK's and DZone gadgets on it. Know what I mean? I'm thinking some way to opt-in or opt-out per post. (unless I'm confused as to how they work... this is my first post with these installed).

I wonder if you could hork in something to make this work? Say a ContentSource that you add to a post that creates design time only content? Then the Footer Plugin checks the post (since it can access the body) to see if that special data is there. And if so, THEN it adds the footer. So two plugins, one ContentSource and one HeaderFooter...

Or an opt-out ContentSource where if it exists the FooterPlugin deletes it (or hides it) and also doesn't add the footer stuff.

I think that would work... wouldn't it? That would give the user a design/edit time view and the coolness of the new Plugins.

Well it's an idea anyway...

 

Related Past Post XRef:
And you thought Windows Live Writer Development had stalled... NOPE! A new WLW CTP is now available, with some cool new features and plugin goodness