[DOCU-1388] Overview and guidance on Integration for OnPrem and Cloud Created: 27/Mar/18 Updated: 30/Sep/19 Resolved: 30/Sep/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | cloud, outdated | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Pre-2019 mgnl-staff requests | ||||||||
| Description |
|
As integration is a key differentiator for Magnolia, developers should be able to get an understanding of their options for integrating, and discover why Magnolia is a good choice for integration. It should be as easy as possible for them to discover the best technique to solve their integration requirement. And the docs should provide the guidance they need to perform their integration. Ideally it would also help them understand the relative effort, and skill set to implement a specifc kind of integration. (20 minutes of configuration vs 4 weeks of Java dev for a custom connector) Integration on Magnolia Cloud should be specifically addressed, and is the top priority. Integration with "Integration platforms" should be specifically addressed. We already have https://documentation.magnolia-cms.com/display/DOCS56/Integration which is a good starting point. Some Ideas for Integration on Cloud: https://wiki.magnolia-cms.com/display/PMTEAM/Integration+options+for+Magnolia+Cloud
|
| Comments |
| Comment by Christoph Meier [ 29/May/18 ] |
I fear you expect Marketing here ... hm ... which we typically try to avoid besides some exceptions.
How far should it go? The topic can be tackled with a reduced one-pager providing some very basics or it can be a 20 pages white paper. Anyway. I see the importance of the topic and consider it as very interesting - but, yeah - it must be refined and the scope must be clear. |
| Comment by Christopher Zimmermann [ 29/May/18 ] |
|
Re "Ideally it would also help them understand the relative effort, and skill set to implement a specifc kind of integration. (20 minutes of configuration vs 4 weeks of Java dev for a custom connector)" - no this is not supposed to be marketing. It should give information on relative effort to perform different types of integrations. Im not sure of the size, we'd have to investigate more, it should be deeper than 1 page - something that a dev would get a real feeling of the integration basics and options available. Re "Easy Integration Stories" - the intention here is to improve the documentation of existing ingtegration possiblities - work on those stories probably won't start till end of the year. Shall I create a more detailed brief and suggestions? Or should we rather meet first to clarify intention and discuss options? |
| Comment by Christoph Meier [ 31/May/18 ] |
|
Yes, czimmermann - we can discuss it. We can start with a quick discussion. |
| Comment by Ewa Snopczynska-Sienczylo [ 05/Jun/18 ] |
|
For now we are not talking about custom cloud. We should document current integration capabilities of the cloud, so without cutomer/partner-created java modules. |
| Comment by Ewa Snopczynska-Sienczylo [ 05/Jun/18 ] |
|
Looking at the current integrations page, I see following points: |
| Comment by Julie Legendre [ 07/Feb/19 ] |
|
Agreed to keep with PO. Upcoming dev changes in CORE related to light integrations may apply to cloud (docs). |
| Comment by Julie Legendre [ 30/Sep/19 ] |
|
In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed. |