[DOCU-1141] New structure of modules' description (cloud as not limitation) Created: 07/Sep/17 Updated: 07/Feb/19 Resolved: 07/Feb/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Ewa Snopczynska-Sienczylo | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | cloud | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Epic Link: | Adapt core documentation to cater for a Cloud user audience. |
| Description |
|
We need a clear way to present what works on cloud and what are possible additional capabilities for on-premise customers. Right now in the Documentation we talk about all modules included in the cloud bundle with links to CORE (where there is a description of all capabilities which will not always work on cloud but person who is reading that does not know that. On main Cloud documentation we just list "Known limitations". So you need to then read first full description, understand it and then come back to the limitations to understand that not everything will work on cloud This is also important as we refer in the contract to Documentation where there is a description of the services, platform and the software (Magnolia instances) and now there might be some misunderstanding.
|
| Comments |
| Comment by Julie Legendre [ 03/Apr/18 ] |
|
In general: change the order, start with Usage, Configuration and things that makes sense for both cloud and on-premise and add Installation at the end with comment that it's only for on-premise |
| Comment by Christoph Meier [ 13/Apr/18 ] |
|
See epic DOCU-1398 |
| Comment by Julie Legendre [ 07/Feb/19 ] |
|
Agreed to close with PO |