[MTE-71] Simple MTK template demo Created: 11/Dec/15  Updated: 25/Mar/22

Status: Open
Project: Magnolia Templating Essentials
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Christopher Zimmermann
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Story Points: 8

 Description   

There should be a demo for MTK which demonstrate typical use cases for each page and component template included in the kit.
A pages exists for each component to demonstrate alternative usages. For example a video subpage should show at least these permutations: asset+ fullwidth, asset+fixedwidth, embed+fullwidth, embed+fixedwidth, plus versions which include captions and not, etc.

Consider that this demo could eventually used for integration tests.



 Comments   
Comment by Christopher Zimmermann [ 13/Apr/16 ]

Please include me in review.

Comment by Antti Hietala [ 03/Feb/17 ]

Closing:

  • Building another demo to show the same components we already showcase in the travel demo seems to provide little value. This ticket basically requests a showcase similar to the old demo-features site.
  • A developer who sees a Text & Image component in the travel demo will understand that the component is close enough to what they want. They understand that the component can be reused and customized. Showing the component in various widths and contexts should not be required – a developer should assume that that's how components work, and that assumption is correct.
  • Let's add documentation to encourage component reuse and restyling. Document one example of a component in different permutations as suggested in the ticket description.
Comment by Christopher Zimmermann [ 16/Feb/17 ]

This will be very helpful for newcomers to Magnolia. Travel demo has a different purpose and does not offer clear overview of MTK. I have a draft version produced. For me the main outstanding question is how it should be delivered - I'm leaning towards another node at the root of the website tree.

Comment by Jan Haderka [ 17/Feb/17 ]

git repo link of your draft?

More detailed description of the functions/components it's demoing? (BTW IMO showing output of different ootb available functions has more value than showing components)

Any research data on showing how many clients use MTK components vs. developing their own w/ more-less same functionality?

how it should be delivered - I'm leaning towards another node at the root of the website tree.

If it should be delivered, than definitively separate module w/ it's own independent page structure. Keep in mind that that for CE you can't have multiple sites, so ppl would need to choose to either install this or travel demo, while if installed on ee, it should come up w/ own site definition too.

Comment by Christopher Zimmermann [ 20/Mar/17 ]

Agree that it should be own module. (Light module). An evaluator can have both travel demo and mtk demo installed and browse pages on author. (Even if they are not both actual sites.)
There's no data on how many clients use MTK components.

Comment by Christopher Zimmermann [ 20/Mar/17 ]

Proposed mtk demo: https://git.magnolia-cms.com/users/czimmermann/repos/mtk-demo.
See README for some details.

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