Details
-
Story
-
Resolution: Fixed
-
Neutral
-
None
-
None
Description
An article *consists of an outline (aka the required fields), a story and of an optional footer (form fields again)*. The story is the actual body of the article. Whereas the outline is published as soon as possible, the story is written later on and published in a second step.
The *article story* is written in a "free-flow" manner. It *consists of several content blocks* (e.g. simple rich text, images, video embeds, tweet references), which *can be added, edited and re-arranged* freely. A story is similar to our existing pages with areas and components, but focuses on content only, leaving out any type of layout and visual attributes.
Goals
We've integrated the previous POC in the product codebase (see DEV-388).
The goal now is to build on top of that and to:
- Refine the code from the original POC, make sure it adheres to your standards and integrates well into the product code base.
- We should be able to access the article editor UI, so that we can discuss our approach amongst ourselves and with customers.
- Add tests where necessary.
Please do NOT refine any of the existing, already implemented features, unless necessary. We'll add and refine actual features using separate stories.
Journalist F: hourly | V: high
Checklists
Attachments
Issue Links
- depends upon
-
CONTEDIT-1 Cleanup and ready POC for putting it into the product
-
- Closed
-
-
CONTEDIT-2 Provide internal bundle that contains article editor so it can be easily reviewed
-
- Closed
-
- mentioned in
-
Page Loading...