[MGNLSTK-435] Paragraph for easy access to data in data module (or standard model classes for it) Created: 17/Aug/09 Updated: 25/Mar/13 Resolved: 25/Mar/13 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | paragraphs |
| 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 | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Description |
|
I was asked in a presentation/mini workshop of STK how all 'categorization' values could be displayed. So I saw the need of users, which want to use STK in a pure inplace templating mode, for easy accessing any stored data in the data module. In this use case the only need was, for being able to render all defined categorizations. I could think of a paragraph on which you choose a folder in data module, and the model class just delivers the allChildren collection. |
| Comments |
| Comment by Christian Ringele [ 21/Aug/09 ] |
|
I have attached a model class, that could be used by any paragraph as its model class within STK. The other idea what would scope the same use case would be: |
| Comment by Christian Ringele [ 25/Mar/13 ] |
|
M5 will change this by content apps, there for obsolete. |