update to author_list and added if_article_keywords & plugin_credits

Been kicking around an idea for a portable, down loadable resource directory for a bit, thought I would toss it up for comments.
The general idea works like a chain letter, whether this migrates freestyle or as part of a more structured forum thread or topic is part of the question – perhaps both. The version 1 directory that I have for download as part of this post contains a directory called “resources” , at present, it contains a directory called “ras” – my development prefix. Inside this directory is a directory called “author_list” which contains my ras_author_list Ver 4.2.0 and some support and code example files. Inside my own directory (ras) I set things up as I wish. To add to the resource directory itself each plugin author (or tutorial author – whatever) would create a directory using their development prefix (if you don’t currently have a prefix I would recommend creating and registering one – the details can be found on Textbook for how to do that) and place within that directory what they wish.
The sticky part comes with structuring version numbers as the download zip file version is bumped for each addition.
A lot of choices to pick from there, from formal forum threads to google-code projects. Just free styling it would get ugly quick I think.

Thoughts?

To any and all concerned, I have a friend pedaling a bicycle 80 miles for a very good cause. Thank yourself for the good things in your life and participate.

It would be fun to Catch a Blaze Here

The drawbacks of some conditional approaches to article and article content display keep bringing me back to an old idea whose potential rattles around with me some; that idea would be article status alteration from withing an article form.
The tag for accomplishing this is in the sidebar as ras_set_article_status, the help file at present reads as follows:

Tag ras_set_article_status sets the current article to whatever status is set in the status attribute, which actively alters an article’s Status. It accepts a status attribute which lists article status as follows.

These tags are intended to be used in an article form. When used in an article form this tag alters an article’s status on an exit condition basis (an article displayed as Live when the tag is called will display, if it’s status is changed to Pending on that pass it will not display on the next pass.)

Used singly as an article form tag it feels very clumsy, but what can be accomplished with article form “form” and “status” attribute settings when organized with sections, conditional tags, and category usage is extensive.
Adjusting article status allows integration of posting time based conditionals (or any other article based conditional check) to automate display control, with pagination methods that are an inherent design characteristic of Textpattern. This if nothing else has me looking at it again and again.
The potential is greater than it seems at first.

The archive in the side bar named 4.0.6 plugins.zip contains a set of plugins that will run with TXP 4.0.6. Very little changed with any of them except some minor updates to adapt to changes in the tagbuilder functions used in some of the older plugins.
This set of plugins represent what I feel worthy of survival and general use with TXP 4.0.6.

Included are:

ras_plugin_credits_v4.0.6.1.txt
ras_page_of_v4.0.6.1.txt
ras_if_dates_v4.0.6.1.txt
ras_if_article_keywords_v4.0.6.1.txt
ras_if_article_image_v4.0.6.1.txt

These have been tested fairly well at this point, but any feedback is always welcome.