[MGNLDEMO-100] Responsive columns component Created: 14/Sep/15 Updated: 15/Apr/16 Resolved: 27/Oct/15 |
|
| Status: | Closed |
| Project: | Magnolia Demo Projects |
| Component/s: | None |
| Affects Version/s: | 0.7 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 2.25h | ||
| 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: | Travel Demo | ||||||||||||||||||||
| Sprint: | Basel 16 | ||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||
| Description |
WhyA columns component will allow pages of the demo to have unique and customizable layouts. It will allow evaluators to see how they can easily create layouts. It will show evaluators how they can integrate a css layout framework such as Twitter Bootstrap. Component details
The component should work similarly to the row component of Tomas' Twitter bootstrap template set on the Forge. The dialog for a row contains a "Layout" selector with the following options:
Based on the selection - between one and four columns are displayed, which are areas where a user can add components. The area should have all MTE components available. The four areas should be created only once upon component creation - so that after a user enters components into the areas the user can still change the layout and the components will remain intact. I recommend using the bootstrap col-sm- classes for all layouts except those with a col width of 3 where I would use col-md- classes. The component html should output a row css class at the top level - but not a bootstrap container class as it will be used in the context of the demo where container classes are already specified. Usage in demoThis component should be available in the main area of home and standard pages. (magnolia-travel-demo home.yaml & standard.yaml).
NoteThanks to improvement proposed in |
| Comments |
| Comment by Philip Mundt [ 17/Sep/15 ] |
|
As far as I'm concerned, I like the proposition. It's the simplest way to get a couple of column variants without adding too many areas (vs. the row AND column approach).
I think this is the only thing that will be difficult to achieve. |
| Comment by Tomáš Gregovský [ 17/Sep/15 ] |
|
All these I already went thru. In latest twitter-bootstrap module (1.3 works only with 5.3.x) you are working only with rows (first is autogenerated to every page) and via dialog you may choose layout for that row. All columns are handled automatically (even if you later decide to completely change that layout). If you can give it a try (version 1.3) that will be maybe best. I spend few months thinking about this solution BTW In next few days I want to migrate it to 5.4 |