[PAGES-416] DOC: Indicate when page templating features are not supported with SPA Editor Created: 25/Mar/21  Updated: 23/Aug/22

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

Type: Improvement Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by PAGES-1153 Component Inheritance with Visual SPA... 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)
Epic Link: SPA Editor Backlog
Team: AuthorX

 Description   

When a feature is not compatible with SPA Editor this should be indicated. Otherwise developers will try to use the feature and will not succeed and will be confused about what they are doing wrong. Also it is important to know upfront what is supported in order to plan a project appropriately.

AC

In documentation, anytime a page templating  feature  is not supported in page editor, this is indicated.

 

Including (but lets research if there are more):

 

 


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