[TYPO3-50-general] Using Phoenix with a grid system

[Adrian Föder]

Hi Folks,

I don't know if this is the best matchin mailing list: we'll see.
Working full time on a basically-plain FLOW3 project, I fiddle a bit 
with a real Phoenix "project" (it'll be a relaunch of a club/society web 
site I'll do on a voluntary base.
Since the requirements are not a lot and the current page is on Joomla, 
state 2007, I think it's a good thing to start with. I would've done 
that in TYPO3 v4, but Christian encouraged me to try Phoenix on this; 
and since basically no "editors" will work on that page, I'm fine with it.

OK; so I chose a bought theme [1] as template, which uses a 960 grid 
system (btw: not *the* 960gs, but this approach).

Markup will look like this:

<!-- 960 Container -->
<div class="container">
	<!-- Logo -->
	<div class="four columns">
		<div id="logo"><a href="#"><img src="{f:uri.resource(....)}" alt="xyz" 
/></a></div>
	</div>

	<div class="twelve columns">
	<!-- menu ... -->
...
</div>

<div class="container">
	<div class="four columns">
	...</div>
	<div class="eight columns">
	...</div>
	<div class="four columns">
	...</div>
</div>

So as a conclusion, a .container element will basically represent a 
"row", while the .columns elements define how many columns a specific 
area will take place. The summ of all columns must be sixteen.

A special case is the fact that *not* each visual row needs a .container 
wrapper, you can also do

<.container>	
	<.sixteen.columns>...
	<.sixteen.columns>...
	<.one-third.column>...
	<.one-third.column>...
	<.one-third.column>...
</.container>

which will result in three rows, first two being full-width, third row 
being three thirds columns.


OK, what I finally wanted to ask is: what would be the best practice to 
reflect this as content elements? I could imagine a content element 
"container", which the editor adds, and inside each container element 
these column types, each, can be added. Inside each column type, we're 
on typical "content element" level, means now TExt, text w/image etc. 
can be added.

Looking at the nodes, is my assumption correct that a "container" 
element would be a Content Node, with having (different) "Columns" as 
children; each now having typical CEs as children?
How can this be reflected in the backend for manually adding? Is there 
the option of something like "recursive" sections? (what is that thing 
having a [+] icon called?)

Looking forward to your input and suggestions,

best,

-adrian


---
[1] http://vasterad.com/themes/?theme=sensation