How the BleedingEdge categories work

BleedingEdge categories are quite different than the Normal-type categories. You don't have to visit your site's backend to publish and unpublish releases and items. It all happens automatically whenever you upload or delete files on your server. Here is the breakdown of how that works.

As all ARS categories, BleedingEdge categories are linked with a Files Directory. Unlike Normal-type categories, BE categories continuously monitor that directory for changes. Whenever you create a new subdirectory, a new ARS Release is created. The Version of the ARS Release is the directory's name and its Maturity is always set to "Alpha".

It also makes it easier for managing development / nightly releases for software. If you upload a plain text file named CHANGELOG (all caps, no extension), ARS will read it, compare it with the previous release's CHANGELOG, colorize the result and use that as the ARS Release's description.

• Lines starting with # (hash) indicate bug fixes

• Lines starting with + (plus) indicate added features

• Lines starting with - (dash) indicate removed features

• Lines starting with ~ (tilde) indicate miscellaneous changes

• All other lines are comments and/or notes

If you're not interested in colorizing, changelogs and stuff like that, just keep in mind that if you upload a plain text file named CHANGELOG it will be used as your ARS Release's description.

Finally, for each file you upload an item be created and published. If you have set up Automatic Item Descriptions for the category they will, of course, be used for naming the item. ARS Releases and ARS Items created this way will inherit the access (view) level settings of the BE category.

Let's sum it up, OK?

• Creating directories creates releases

• A text file named CHANGELOG will be used to produce your release's description

• Uploading files creates items

• Access (view) levels are inherited from the category to the release, to the items

• Deleting a directory unpublishes the release

• Deleting a file unpublishes the item

• You don't need to login to your back-end to manage the releases and items, but if you want to, you can.