Where can documentation be found?

The project's home page includes a link to some "partial and incomplete" documentation.

Marked #401768: Utilization as duplicate of this issue.

While the project's home page currently just contains a single image, the "partial and incomplete" documentation doesn't appear to exist any more.

Is there any documentation? Even just notes or definitions?

Documentation is in progress and will be provided as a README.txt in forthcoming releases. As you can see there isn't much at all at the moment.

If anyone would like to accelerate the documentation - the best thing to do is write something down and attach to this issue.

This documentation is under development : it is yet partial and incomplete

STORM stands for SpeedTech Organizer and Resource Manager.

It is a project management application built upon Drupal CMS platform.
Currently it requires Drupal version 6.

It is composed by a series of modules that need as prerequisite only a Drupal 6 base installation.
It doesn't require any additional external module to work, but it can be extended by them.

The main goal of STORM is to provide a basic frameworks and some standard elements upon which is possible
to build a custom project management applications in Drupal.

In fact, every component in STORM, except Attributes, is a node, so, for example, the CCK module can be used to add additional fields to the various content types if necessary and with Views module (support yet to implement) is possible to build customized views.
It is also possible to use the Drupal's core module Taxonomy to tag the contents, the Upload module to attach files and Comment module to permit comments on every content.

At now STORM provides the following features :

• Attributes : to manage the different list of values used in STORM, like : tasks status, countries, currencies and so on
• Organizations : the companies or individual stakeholders of your projects
• Projects : your projects. Every project can have multiple tasks hierarchically nested to build a WBS
• Tasks : the parts that compose a project
• Tickets : every ticket can be associated with an organization, project and task
• Timetrackings : where you can register your activities on an organization, project, task or ticket
• Expenses : where you can register the expenses of a specific project of or of your own activity
• People : organizations contacts
• Permission control : a fine grained permission control permits to share the data with other users and organizations
• Reporting : a simple and themeable support for reporting (with optional multilingual support)
• Notes : a note can be associated to an organization, project and task
• Knowledge base : to collect your tips, tricks and important pieces of knowledge

Attribute component permits to create list of values.
Every list is identified by a domain, like : country, currency, project status and so on.
Every attribute has a key and a value. The key is used internally in the code, the value instead is the label showed to the users.

This permits to build dynamic list of values to use in several contexts and give the STORM's users the freedom to completely customize the lists. It is possible to build custom lists for project, task, ticket status accordingly with company workflow and rules.

It is also possible to build group of values to use on filter forms, or to group the values in an hierarchical structure.

Organization permits to store the data regarding the customers and the providers.

Also the organization that own the STORM installation should be listed here.
This permits to organize in STORM also its own internal projects and to use the Person component to build an internal contact list and to organize the "internal" projects.

Changing priority as per #435504: TODO BEFORE STORM 1.22

There is now a handbook page about the Storm module at http://drupal.org/node/437426 (currently edittable by all as are all handbook pages)

The README.txt has also been updated and substantially extended today - currently is almost identical to the handbook page.

Therefore I'm calling this fixed. Its not perfect, but I think that there is no longer a "lack of documentation" as previously has been said. If you want more documentation - please contribute it!

I would also like at somepoint to provide some sample use cases so that a new user who doesn't want the full thing can simply say "I want a ticket management system - these are the modules that I need to activate and Storm will do that", or similarly for an invoice system etc. The best way for this is for some people to provide their own as an example.

This link is dead. He's removed all mention of STORM from his site. Not a good sign.

@aaronghawkins,

This issue is closed - meaning that the contents are considered solved.

Although some of the external links above no longer lead to documentation (but can only be editted by the users that made the comments or site webmasters), there are clear links from the project page and from other comments in the above issues. There is also a README.txt file in the download. These are all easily found.

Therefore, perhaps the comment about what "sign" this gives about the project is a little unnecessary.