Damaris RM

Using GAS, you can inventory, index and manage client records. With our web based software, clients can access and view the inventoried documents, request pick-up or delivery, accurately monitor document movements, and enforce role based security, all without leaving their office. By storing data off-site, clients ensure they have secure back-up documentation in the event of business disruptions or compromised internal record keeping, thereby minimizing the potential impact of business disruptions.

GAS processes electronic documents. It offers a fast and reliable documents retrieval tool. GAS archives and indexes all the documents outgoing from your IT packages. It guarantees data integrity. Thanks to safe electronic storage, it provides legal documents copy. GAS accelerates the decision making process for your customers by giving access to all their commercial legal documents.

For backwards compatibility, if this section is missing, the full length of the short description will be used, and Markdown parsed.

A few notes about the sections above:

• “Contributors” is a comma separated list of wordpress.org usernames
• “Tags” is a comma separated list of tags that apply to the plugin
• “Requires at least” is the lowest version that the plugin will work on
• “Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on higher versions… this is just the highest one you’ve verified.

• Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for stable.

  Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that’ll be used for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.

  If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where you put the stable version, in order to eliminate any doubt.

A brief Markdown Example

Ordered list:

1. Some feature
2. Another feature
3. Something else about the plugin

Unordered list:

• something
• something else
• third thing

Here’s a link to WordPress and one to Markdown’s Syntax Documentation. Titles are optional, naturally.

Markdown uses email style notation for blockquotes and I’ve been told:

Asterisks for emphasis. Double it up for strong.