[MGNLSTK-436] Make inplace templating more usable Created: 17/Aug/09  Updated: 25/Mar/13  Resolved: 25/Mar/13

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: concept
Affects Version/s: 1.1.1
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Christian Ringele Assignee: Christian Ringele
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLSTK-433 Singleton paragraphs don't show 'dele... Closed
depends upon MGNLSTK-407 Make template hierarchy configurable ... Closed
depends upon MGNLSTK-435 Paragraph for easy access to data in ... Closed
depends upon MGNLSTK-422 AllowedBodyClasses in BodyClassResolv... Closed
depends upon MGNLSTK-437 Show original code of a template in t... Closed
depends upon MGNLSTK-446 More complete method collection in ST... Closed
Template:
Acceptance criteria:
Empty

 Description   

By helping customers who want to use STK in purely inplace templating mode I have seen different problems/constraints in doing so.
Their need was to build a POC of a certain site. So the main aim was to build it only in inplace templating mode without using a IDE.

I have created some Jira tasks of the problems/constraints I have seen.
For not loosing track of them in the meaning of one topic 'inplace templating' I created this task and add all relevant tasks here.



 Comments   
Comment by Christian Ringele [ 25/Mar/13 ]

M5 will change all repo accesses, also the inplace templating I assume.
This issue is obsolete.

Generated at Mon Feb 12 07:27:01 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.