[PAGES-1072] DOC: Deprecate support for magnolia-hosted SPA with templateScript (mgnl 6.2) Created: 07/Mar/23  Updated: 22/Mar/23  Resolved: 20/Mar/23

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

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by PAGES-1089 DOC: Remove support for magnolia-host... Accepted
documentation
documents PAGES-995 Deprecate support for magnolia-hosted... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-1073 Implementation Sub-task Completed Martin Drápela  
PAGES-1074 Review Sub-task Completed Oanh Thai Hoang  
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)
Epic Link: SPA Editor Backlog
Sprint: DevX 33
Story Points: 2
Team: DeveloperX
Work Started:

 Description   

The Visual SPA Editor started out using a `templateScript` property in a page template definition.

The "External SPA" feature which introduced `baseUrl` and `routeTemplate` and is now the best practice approach.

In order to get our customers on the better featured External SPA, and to reduce maintenance effort and bugs we should docu deprecate the earlier approach.

 

To docu:

Short overview of migrating from templateScript approach.

Brief explanation of benefits.

Deprecated in 6.2.30

Support will be removed in 6.3.
Will not be supported on SaaS

 


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