[MGNLRES-184] Phase out in-place templating app in favor of Resources app Created: 30/Jul/15  Updated: 19/Jul/22  Resolved: 26/Nov/15

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: None
Fix Version/s: 2.4.2

Type: Epic Priority: Major
Reporter: Andreas Weder Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: resources, resources-app, templating, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to CFGUI-5 Prepare the definitions app for inclu... Closed
relates to MGNLRES-203 First set of improvements for Resourc... Closed
relates to MGNLRES-201 Write filters to only show resource f... Closed
dependency
is depended upon by MGNLINTEMPL-83 Remove legacy in-place templating "Te... Closed
relation
is related to MGNLRES-149 Concept for supporting processing res... Closed
supersession
supersedes MGNLRES-183 Improve the Resources app for in-plac... Closed
Template:
Epic Name: Phase out in-place templating app
Acceptance criteria:
Empty
Release notes required:
Yes

 Description   

This epic collects a set of stories to improve the Resources app shipped with 5.4. They add both new features as well as rework existing ones to improve clarity and align the app with the original feature set of in-place templating. Also included here are stories and tasks describing the underlying technical changes required to achieve all of this.

The goal is to ready the Resources app to take over all in-place templating functionality. Once that is done we will migrate existing template over and remove the legacy "Templates" app, which is of no use anymore. We're also going to remove the hot-fixing functionality we've added in the initial version, as it added too much complexity at this point and is a source of confusion for customers. JCR resources become first-class citizens like resources from other origins, instead of being treated as patches or hot-fixes.

There's a revised design in the UX wiki space that describes the desired outcome in more detail.



 Comments   
Comment by Andreas Weder [ 20/Aug/15 ]

I've moved some not-yet-started stories to different follow-up issues to better partition our road to improved configuration.

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