[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:
Relates
relates to DOCU-1567 Write new Integration Feature overview Closed
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 ]

... 20 minutes of configuration vs 4 weeks of Java dev for a custom connector ...

I fear you expect Marketing here ... hm ... which we typically try to avoid besides some exceptions.

And the docs should provide the guidance they need to perform their integration.

How far should it go?
What is the scope?
Who is the audience?

The topic can be tackled with a reduced one-pager providing some very basics or it can be a 20 pages white paper.
(which remembers me that there once was a white paper coming from marketing, but most probably outdated. I also remember that Lorraine once asked me to update that paper - but I was rejecting this since I thought Marketing should speak first with sales et al.)

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.
And at least for me it is also not clear in which direction our product - both on-premise and cloud - will go.
=>
"Custom Cloud" - as we provide it for swissRe, but I'm not sure whether this will become a common pattern. I see swapping, opposed opinions concerning this from stake holders.
=>
Easy Integration Stories (https://goo.gl/xnCUAz) - will they really make it?

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.
To define the scope in detail - we really would need to know what will happen concerning custom cloud yes or no.

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:
1. As a cloud user I don't know which ones from that long list will work in my case
2. Marketing Tags - I'm not sure if it's clear to everyone what you can achieve with it. For example I had no clue that the chat on our corporate website was done via Marketing Tags. We are missing some nice examples for terms that people may also search for (eg. chat in this case. Maybe Zak could also help here?
3. Some of the modules there are not available on cloud and don't make sense there
4. It would be nice to have some REST based integrations described with some examples with the systems you can base your integration on it. We could also look at the most common tools we, our customers and partners integrating with and list them as examples

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.
If you think your ticket is still relevant and should remain open, please add a comment and set it back to open.

Generated at Mon Feb 12 01:17:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.