[MGNLFE-61] Support for user-defined area templates Created: 21/Jul/20  Updated: 21/Oct/21  Resolved: 08/Sep/20

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: Template Annotations
Affects Version/s: 1.0.4
Fix Version/s: 1.0.6

Type: Improvement Priority: Major
Reporter: Adrien Manzoni Assignee: Robert Šiška
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d
Original Estimate: Not Specified

Issue Links:
Cloners
clones MGNLFE-58 Allow using dialog at area level Closed
Problem/Incident
causes MGNLFE-76 DOC: User can define area templates Closed
causality
is causing MGNLFE-137 1.1.0 not working with latest Angular Closed
is causing PAGES-352 Provide endpoint for template annotat... Closed
dependency
is depended upon by MGNLFE-60 Release 1.0.5 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)
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: SPA Editor
Sprint: HL & LD 10, HL & LD 11
Story Points: 3

 Description   

Many customers use the area as a single fixed component. The template definition framework allows you to assign a dialog to an area.

Allow users to create their own area scripts with as little overhead as possible.


Generated at Mon Feb 12 05:43:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.