[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: PNG File stories_outline_collapsed.png     PNG File stories_outline_embed_video.png     PNG File stories_outline_expanded.png     PNG File stories_outline_image.png     PNG File stories_outline_related.png     PNG File stories_outline_video.png     PNG File stories_outline_with_content.png    
Issue Links:
Relates
relates to CONTEDIT-132 Stories-app close confirmation dialog... Closed
relates to CONTEDIT-137 Add additional actions to stories app... Closed
dependency
depends upon CONTEDIT-127 Implement visual design for MultiValu... Closed
depends upon CONTEDIT-128 Default state of CollapsibleComposite... Closed
depends upon MGNLUI-4254 Add story app icon to icon font Closed
depends upon MGNLUI-4266 Add new story app icon to icon font Closed
is depended upon by MGNLDEMO-221 Stories app demo Closed
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   

'Stories App' will be the 'stock' instance of the content editor, similar to the role the Pages app plays. It will be present in the EE bundles even when the travel demo is not installed.

The travel demo will install some sample content and make some minor modifications to the app. These modifications are not to be performed in the scope of this ticket.

App:

  • Stories

Workspace:

  • stories

Action bar:

  • Add story
  • Edit story
  • Rename story
  • Delete story
    As well as all of the typical content app actions:
  • Rename
  • Move
  • Duplicate
  • Export
  • Publishing
  • Versioning

Definition of outline:

General

The outline of the Stories app has 4 collapsable sections. The sections are collapsed per default (when opening a new story):

The fields within the outline are specified as the following:

Following image shows the outline with sample content:

Lead visual

The section Lead Visual has three options that can be selected via radio:
The fields caption and credits are the same for all three of them.

1. Image

2. Video

3. Embed video

Related content

A story links to other stories and other tours that can be selected with a multivalue field. In the context of this ticket, only provide the link to other stories. (The links to other tours will be implemented in another ticket.)



 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.

  1. Instead of renaming the article-editor we should create a new app stories-app
    • It is bound to the travel-demo and therefore (the outline) will differ to current articles-app
  2. We keep articles-editor for UI testing purposes (until we have recieved proper contents from marketing and know how to embed it in the demo)
  3. We need to decide where the new app (stories-app) will be "hosted"!
    • In the content-editor project
      • with optional dependency to the travel-demo (and optional installs)
      • with separated contents and pages (templates) in the travel-demo
    • In the travel-demo project <- Decided to do this option. Make it a submodule in travel demo EE project.
  4. Having a separate app for Stories is a very good test-bed for the content editor.
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 Stories app brings you a JCR workspace (currently "articles"), semi-structured node-types, and the content-editor, just like...
  • THE Pages app brings you a JCR workspace (website), templating-based node-types, and the page-editor.

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:
We decided that the Stories app is shipped as a stock app, independent of the travel demo as suggested by Mika above. The ticket description has been updated to match the conclusions.

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!

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