[STORE-4] use STK for the pages Created: 10/Mar/10  Updated: 11/Mar/10

Status: Open
Project: Magnolia Store (server-side)
Component/s: server
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Boris Kraft Assignee: Magnolia International
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

We should eat our own dog-food. STK article provides a structure that can in similar fashion be used for a detail page. The header would contain the structured part, and the content could then be unstructured.

The benefit in my eyes would be we use what we believe in, and could use RSS feed generation and fancy teaser etc.



 Comments   
Comment by Magnolia International [ 10/Mar/10 ]

This is true but - on the other hand - shouldn't the "fancy" stuff left to www.magnolia-cms.com or documentation? I'd be more in favor of the "store" to kist contain the info necessary for the client to work (i.e what modules are available for it, what to update, etc), and link back to documentation or other site for more info.

This same information could be reused by www.m or documentation.m, via rss or other mechanism.

(eventually, the communication between the "client" in admininterface and the server store will be a little more evolved than an iframe and pages)

BUT - it is true that STK provides a part of the infrastructure for this too.

Comment by Boris Kraft [ 11/Mar/10 ]

Down the road I envision this to be more and more like the iTunes store, not just a list of stuff, but really a store front with different sections. In any case I see little reason why we shouldn't use what we communicate as best practice. If we use STK for the web interface, it will be straightforward for anybody to work on this.

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