Create Use Case Documentation
(DOCU-176)
|
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Suzanne Deprez | Assignee: | Antti Hietala |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: |
| Description |
|
Create a use case that will provide information and documentation needed in order to deploy a site to production. This information is divided among several resources (see Deployment+to+production). This use case will provide a starting point that can direct the user to all of the helpful documentation and provide a cohesive description. A skeleton of this use case is provided at Deployment+to+production. |
| Comments |
| Comment by Antti Hietala [ 01/Sep/11 ] |
|
How is this task related to DOCU-89 How to do a project with Magnolia? Avoid overlap. Also, make sure you clearly state the best practice. While there may be many options for doing a particular task, identify the recommended way. For example, while you can run Derby in production (and there are sites that do), it is not our recommendation. |