[ALOY-255] Assess/Improve Alloy Documentation
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Resolved |
| Resolution | Fixed |
| Resolution Date | 2012-09-28T03:17:16.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | 2012 Sprint 20, Release 3.0.0 |
| Components | Documentation |
| Labels | n/a |
| Reporter | Tony Lukasavage |
| Assignee | Unknown |
| Created | 2012-09-12T10:57:32.000+0000 |
| Updated | 2018-03-07T22:25:33.000+0000 |
Description
Let's assess the current state of Alloy's documentation:
* Do we have good coverage from the docs provided by the docs team?
* If not, where do we need improvement?
* Should the quick start be updated with more samples? Perhaps separate tabs sections for high level Alloy concepts like view/controller creation, using models, etc...
* Do we need to consider wiki/training docs?
Any work resulting from this ticket will be put into a ticket of its own.
Arthur has stated that Alloy docs on the wiki and other elements wil be made available for 3.0.0