[CONTEDIT-111] Add 'Stories' App Created: 17/May/17 Updated: 22/Sep/17 Resolved: 21/Jul/17 |
|
| Status: | Closed |
| Project: | Content Editor |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.6 |
| Type: | Task | Priority: | Major |
| Reporter: | Anja von Gunten | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Epic Link: | Stories App Demo | ||||||||||||||||||||||||||||||||||||
| Sprint: | Basel 104, Basel 105 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||||||||||||||||||
| Description |
| Comments |
| Comment by Philip Mundt [ 23/May/17 ] |
|
After a short discussion with avongunten we came to the conclusion to not tackle this in Sprint 97.
|
| Comment by Mikaël Geljić [ 04/Jul/17 ] |
|
Hi there, Travel-demo owning the Stories app sounds awkward to me. The Stories app is gonna be "advertised", users are going to look for it in the product/bundles—until they realize that, in order to get it, they have to drag in our demo modules & content. This may not be an ideal setup for Magnolia NOW either. I also doubt whether the two use cases differ that much, to justify maintaining two apps (TL;DR, I'm for renaming the current app, from the content-editor reactor). As discussed briefly with Topher, the "related tours" customization is a tiny piece of it, we would tentatively address it more elegantly with decoration. It would prove the value of the stock app too (unlike the proposed setup). Here's how I see it, currently:
The travel-demo, in turn, merely bootstraps sample content into both of these stock apps (+/- customization, within the bounds of what those apps let you configure). Don't get me wrong, I do see the temptation to spawn multiple stories apps—just like we can have multiple content apps—, I just think it's a bit early to do so, without repeating all the boilerplate content-apps typically need. In particular, we aim at covering that under the umbrella of content types, hence for light-development as well. Meanwhile, I hope we can satisfy ourselves to ship the one Stories app out of the box. It has huge value already! |
| Comment by Christopher Zimmermann [ 05/Jul/17 ] |
|
Thanks Mika - that makes sense to me. |
| Comment by Rasmus Skjoldan [ 05/Jul/17 ] |
|
I'd like to have a quick meeting about this - have proposed that. Just want to quickly align on travel demo and stories app. To me, it's certainly important that the Stories app is treated as an equal to Pages and Assets and should preferably not be removed just because you dump the travel demo. But I'm not entirely sure how that works when it's an EE feature. You can enlighten me about that later, please |
| Comment by Christopher Zimmermann [ 10/Jul/17 ] |
|
To summarize a meeting with Anja, Rasmus, Michael G, Sasha, Topher on Thurs 6, July: Whether the existing articles app is renamed - or whether a brand new app is created, and how to handle the existing integration tests is for PD to determine. |
| Comment by Philip Mundt [ 11/Jul/17 ] |
|
Field labels in the screenshots are not consistent. Please specify correctly. cc avongunten. Thank you! |