[PAGES-80] Adapt pages app to Content-Connector concept Created: 05/Jul/16  Updated: 09/Feb/17  Resolved: 23/Sep/16

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: 5.5

Type: Improvement Priority: Neutral
Reporter: Espen Jervidalo Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-3943 JcrContentConnector ignores node-name... Closed
duplicate
duplicates PAGES-42 Introduce PagesContentConnector and A... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Basel 52, Basel 62
Story Points: 3

 Description   

The motivation is to further simplify the API and make the key-components JCR-agnostic.



 Comments   
Comment by Roman Kovařík [ 08/Aug/16 ]

Reopened: https://git.magnolia-cms.com/projects/MODULES/repos/pages/pull-requests/26/overview?commentId=8097

Generated at Mon Feb 12 06:15:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.