Hi Roland,
I don't know if this is helpful for you, but we have implemented 2 different
layouts that sound a bit like what you need:
www.generationblue.at
www.cosmoundnanu.at
Both layouts use a flexible "boxes" approach.
Generation Blue uses what's now called a "responsive design" - the same code
works on deskop, smartphones, tablets, etc... The content automatically adjusts
to the width of the screen. This is accomplished using a bit of javascript, but
mainly via CSS.
Cosmo and Nanu is a simpler design - the idea here was not to be adaptive for
mobile devices, but rather to allow the editor to fill a fixed width page with
different layouts composed of boxes, so that the overall effect is that of a
comic-book style look, with content in different "panels".
Each box (or panel) is a paragraph, and the editor can choose the width (full,
half, one-third, two-thirds) and whether the box should start in a new line
("clear") or appear next to the previous box ("float-left").
When the template renders the boxes, it applies appropriate style classes which
force the width. We also have a simple piece of javascript which adjusts the
boxes heights to be the same, so there are no "ugly gaps" if some of the
content is shorter than its neighboring box.
What both these sites have in common is that we don't use the STK templates. We
use the other STK features, but we wrote our own template and paragraph
definitions and scripts from scratch.
Why? STK has its own "model" of how the HTML and CSS are composed. If your
design agency can implement your design by modifying the STK theme (ideally
without changing the STK HTML at all) then you'll be faster working with STK -
all the paragraph and template definitions and scripts are done for you, and
you just need to pick out the ones you need to make your site.
However, many designs can't be implemented by just changing the STK Theme. Many
designs would require major changes to the HTML structure of the STK templates,
or redefining the paragraph nesting in ways which don't work in STK. In this
case, we have found it simpler to just "start from zero", and build our own
template scripts and definitions, specifically tailored to the design we're
trying to realize. It ends up being much less work than "fighting" with STK.
Regards from Vienna,
Richard
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]]
Im Auftrag von Roland Polzer
Gesendet: Donnerstag, 14. Juni 2012 14:04
An: Magnolia User-List
Betreff: AW: [magnolia-user] Re: Flexible column layout
Hi Ruth,
Thank you for your answer. In other CMS systems it seems to be easy for the
editor to create columns in the main area.
In Magnolia I have the "text and image" paragraph which can have tables, but
the table columns cannot contain nested paragraphs.
I would like a way for the editor two create a row with two columns (or areas)
containing paragraphs.
In the simple case with two columns I would implement a paragraph "change
column". Initially paragraphs would be rendered in the left column. Paragraphs
after "change column" would be rendered in the alternating columns.
The only reason why I need this is to align the vertical position of paragraphs.
Kind regards,
Roland
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe,
E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details, see http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
