DOCS: Indicate which templating features are available with SPA and Freemarker (MGNLFE-184)

[MGNLFE-199] Confirm the SPA-relevance of some Magnolia properties Created: 18/May/22  Updated: 20/May/22  Resolved: 20/May/22

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

Type: Sub-task Priority: Neutral
Reporter: Martin Drápela Assignee: Robert Šiška
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Date of First Response:
Sprint: DevX 10
Team: DeveloperX

 Description   

As mentioned in the parent ticket, please confirm the following:



 Comments   
Comment by Robert Šiška [ 20/May/22 ]

Area definiton

  • createAreaNode - Not relevant in SPA. Area nodes are created only after a component is added into the area.
  • fragmentDefinition - Not relevant in SPA. Rendering (and therefore caching of rendered content) is handled by SPA itself.
  • type - Relevant in SPA. Works the same way as in Freemarker rendering.

Component definition

  • deletable, moveable, writable - Works the same way in SPA. Note: it's {}writable{} not {}writeable{}.
  • personalizable - Works the same way in SPA.
  • fragmentDefinition - Not relevant in SPA. See above.
Generated at Mon Feb 12 05:45:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.