[MGNLFE-185] DOCS: Indicate which features are not available on headless Created: 29/Mar/22  Updated: 31/Oct/23  Resolved: 25/May/22

Status: Closed
Project: Magnolia Frontend Helpers
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
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 MGNLFE-684 DOC: Move all Headless vs FreeMarker ... Closed
Relates
relates to MGNLFE-160 DOCS: Review and overhaul SPA editor ... Selected
relates to MGNLFE-184 DOCS: Indicate which templating featu... Closed
relates to MGNLFE-684 DOC: Move all Headless vs FreeMarker ... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLFE-200 Confirm the relevance for headless of... Sub-task Completed Martin Drápela  
MGNLFE-202 Mark SPA/headless-friendly modules - ... Sub-task Closed Martin Drápela  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Epic Link: Headless Phase 2
Sprint: DevX 10
Story Points: 1
Team: DeveloperX

 Description   

As a business user, decision maker, or developer I want to kknow which Magnolia features can and caannot be used in aa headless context.

Every feature that cannot be used on headless, or that haas a reduced functionality - should have an indication on its documentation.

Additionally there should be a central location where someone can go to see which features are not available on headless

Docs to change

Available

Requires implementaion in SPA project.

Pages App

Personalization 

Versions

Live Copy

Commerce connector pack 

Marketing Tags - Probably: Authoring can be used, speciaal implementation is required in frontend project

Marketing automation connector pack - Probably: Authoring can be used, speciaal implementation is required in frontend project

 

Not Available

Diff / Compare Versions -Not available on SPA / headless. 

ABn Testing - Not available on SPA / headless

Form module -  Not available on SPA / headless

PUR module -  Not available on SPA / headless

Component Inheritance -  Not available on SPA / headless

Component autogeneration -  Not available on SPA / headless

Model class / JSModels -  Not available on SPA / headless

MTK -  Not available on SPA / headless

 

Needs research:

Campaign Manager - Pretty sure it is available now. Check with JanS or Bartosz

Content Translation Support module ?

Multisite

Privacy module

 

 



 Comments   
Comment by Bartosz Staryga [ 23/Oct/23 ]

Maybe all the places where we talk headless vs freemarker etc could point to: https://docs.magnolia-cms.com/product-docs/6.2/Developing/Templating/Freemarker-vs-headless.html and we would keep most up to date state there?

Comment by Christopher Zimmermann [ 23/Oct/23 ]

Sounds good bstaryga , could you create a new ticket for this?

Comment by Bartosz Staryga [ 25/Oct/23 ]

I tried my best: https://jira.magnolia-cms.com/browse/MGNLFE-684

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