There is a tutorial of an older version here:
Scott McCulloch News Articles Module V00.04.09 Review
(6 videos - 30 mins)

Yep saw those, thanks, that got me started... without those tutorials I think I would have tossed ventrian NA out the window already.. Now I find myself trying to understand what the consequences are if I use one instance of the ventrian article module (see www.cubeconsulting.nl/artikelbeheer.aspx) versus a number of instances with related articles (which I had before). Newsslider can only point to one instance at the time, so if I want to use related articles I think I better use one big page with all articles resulting in a potential clutter of articles if somebody is smart enough to just type www.cube../artikelbeheer.aspx.

Now that I am bugging you anyway, can you tell me please, how can I enter tags in the page details..? There is a tags dropdown list, but I can't seem to find where to enter the actual tags I should choose from.. Thanks Lee!

On DNN Creative we have setup multiple Ventrian NA modules on different pages, each displaying a different category, ie:
http://www.dnncreative.com/Tutorial...fault.aspx

For tags, go to Admin / Taxonomy

We are covering those tags along with Taxonomy and Folksonomy in the July issue of DNN Creative

Hi, thanks for the reply. Will add additional NA modules, too, then. I started out doing that but did not grasp the meaning of picking different instances in newsslider, causing unexpected windows to open up when clicking on [read more].
I will return to this approach, maybe I will still hang on to one master page holding all articles and using the other instances to filter on a category (someone else suggested this). I think that way I can relate all articles. Many thanks so far! Aad

Hi Lee, sometime ago I posted these remarks: In a similar quest to understand the dnn universe, in Ventrian NA I was struggling with the [hassumary] tokens which made my [details] content disappear. Apparently the summary is not empty when using the br entermode in the fckeditor, it leaves one br tag. The [hassumary] is then valid, and the [details] token which is between [hasnosummary] token is not displayed. Took me a while and a lot of sedatives before I found that one out..

I am still fighting to get rid of this excess BR tag, do you have a solution to this? I searched all over the net, found people with similar problems, but no solutions.. It is a big headache in Ventrian as the body of an article is not seen as empty and therefore read more links are shown when there is no body text in effect..

Many thanks Aad

The easiest way to do that is to edit using the Basic Text Box. 

Hi Joe, sometimes the easiest answers turn out to be too easy.. I tried your suggestion, but I still get the empty BR tag - even in basix text box - when I leave the body text empty in ventrian NA.. This seems Firefox related, in other browsers I manage to get the body text to remain empty, but then ventrian won't save the article.. Seems like there's some bug there, too..

I'll try to look at this in News Articles.  It works this way with Text/HTML modules.

There are configuration options for the FCK editor.   There are some threads in the forum that discuss how to customize the default behavior.  There is also a list of tutorials.

Your other option is to switch to the Telerik editor if you are using a current version of DotNetNuke.

Hi Joe, thanks for those comments. You are absolutely right, it really does empty out the content in the HTML module, no extra BR tag.. It really must be something in ventrian then.. I guess it is in Scott's hands now (pun intended..)

I guess I have found a solution to the BR tag issue in empty body text ventrian articles. I added a custom field to the Ventrian NA template and the dnnUI Newsslider interface with name Readmorelink, type of dropdownlist with values link and none. Then I put the read more link between an expression token like this:

[EXPRESSION:Readmorelink:=:link] a class="readon right" href="[LINK]" target="[LINKTARGET]">[lees verder] a [/EXPRESSION:Readmorelink:=:link]

Now only if the value of 'link' is selected when creating a new article a link is shown to more content, otherwise it is not.. I agree it is not the prettiest solution, but it seems to work now...