[MTE-58] Workshop: Review existing MTE components Created: 14/Oct/15 Updated: 17/Oct/16 Resolved: 11/Dec/15 |
|
| Status: | Closed |
| Project: | Magnolia Templating Essentials |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 0.8 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Christopher Zimmermann |
| Resolution: | Done | Votes: | 0 |
| Labels: | workshop | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 3h | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| 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: | |||||||||||||
| Epic Link: | Light Development 1.0 | ||||||||||||
| Sprint: | Basel 22 | ||||||||||||
| Story Points: | 5 | ||||||||||||
| Description |
|
Results of the workshop: Workshop Goals: A 1/2 day workshop including people who have had experience working with the components, or have extensive project or STK experience. As preparation, participants should spend ±1/2 day to re-familiarize themselves with MTE components and create a branch with two components rewritten to the standard they would propose. Ideally textImage and internalTeaser. Workshop has three parts: Also consider proposal to move MTE templates to new module: Based on the workshop - implement the recommended chages. Some possible changes / coding guide topics:
( Note: How to include css, js, or other resources in MTE for components considered in another workshop: Workshop goals:
|
| Comments |
| Comment by Tomáš Gregovský [ 08/Dec/15 ] |
|
Lets just put my comment before tmr meeting, to save some time For example. to have just components, without at least one page with availability for them is no-go for me. (I don't want to define page template and set availability to all MTE components just to see what they are doing). Then this topic for me continue with many follow-up questions:
These are much more follow up questions which I already went true and is really simply to struggle in question of complexity. And I am worried about to make something universal for everybody is almost impossible these days. I will just repeat myself, but in case of usability for developers I would much more like to see "basic modules" for today's most used html frameworks (3-5 of them) instead of trying to provide one universal thing for everybody. Any of them can by later extended with "addons module" for more specific components like carousel, social share, etc... (or they can by just downloadable in yaml+ftl zip). And in case any new framework will come in future no matter how crazy he will be we will don't have to look how to extend our universal MTE to support it, but will just provide new basic for it.... |
| Comment by Christopher Zimmermann [ 08/Dec/15 ] |
|
Thanks Tomas. Part of this workshop is not just to refine the existing components - but to create a good convention for how to build components - like a coding guide/style guide that could be reused on other template kits. Yes we will include page templates. See https://jira.magnolia-cms.com/browse/MTE-49 Regarding css classnames - what about creating a new templateDefinition which is the same as the existing link - but sets a css class parameter, (or using extends when that becomes available)? OK - this does not cover the wrapping div case. Maybe we should add a new parameter - that when present it adds a wrapping div to the component html. |
| Comment by Richard Gange [ 09/Dec/15 ] |
|
Just want to point out I did open this ticket about groovy model support some time ago: Groovy models work just fine when configured in JCR. It's the YAML based config that's the issue. I have a patch for it. I'm not proud of the patch however |