At this point, I only use this for simple articles/news/blog entries that I want posted.  If I want something more, I create my own CMS outside of WWF.  The reason being that making too many MODs to Borg's scripts makes it hard to upgrade WWF.

 

For example, you will notice that I do not use forum_posts.asp for articles but have created article_posts.asp instead.  Then in forum_posts.asp I determine whether or not the post is in forum format or article/news/blog format, and redirect to article_posts.asp if article/news/blog and use forum_posts.asp if a forum post.  This way it cuts down on the number of files I need to update every time Borg comes out with a new version.  If I didn't have to worry about upgrading WWF, I would have implemented it a different way.

 

Although I am playing with the idea of creating alternate "list" pages for articles and blogs that would order the information how I want, and then having a different table hold additional information about a post.  The goal being to touch Borg's code and database structure as little as possible, while adding as much functionality as possible.  Not always an easy task.

 

The article that you see on that page is actually the first post in a forum thread!

 

Basically I created article_posts.asp by modifying forum_posts.asp so that the first post looks different than the replies.  I then set up WWF so that for non-forum categories (articles and blogs) use article_posts.asp instead of forum_posts.asp.

 

I'm going to do more tweaking, but this small demonstration shows how easy it is to implement it.

 

This is really a  good news!